- VS .NET browsing problem
- Posted by Bajamani on October 19th, 2005
1. Using VS .NET IDE. and building from build environment.
2. .bsc file is generated. no problem there.
3. Specified browser info in Project|Properties|C/C++|Browse
Information|Browser File.
i am able to browse my structs but not DDK stuff. any other setting
that is to be done in VS IDE?
more...i am able to browse in VS 6.
anyone? Mark?
- Posted by Gary G. Little on October 21st, 2005
You need to set the browse flag, BROWSER_INFO=TRUE, in your sources file.
Setting the IDE browse switches in the project is useless since BUILD and
sources have nothing to do with the IDE, other than using the IDE as a
launching platform.
--
Gary G. Little
"Bajamani" <bajamani@hotmail.com> wrote in message
news:1129705297.943859.37270@g14g2000cwa.googlegro ups.com...
- Posted by David J. Craig on October 21st, 2005
Follow the instructions on the DDKBUILD web site and the browser will work.
It is hollistech.com where it is located. Make sure you delete any .bsc
file you have and find the one created by the build process.
"Gary G. Little" <glittle@mn.rr.com> wrote in message
news:_HZ5f.16071$1A1.6837@tornado.rdc-kc.rr.com...
- Posted by Mark Roddy on October 21st, 2005
Also note that bscmake.exe is NOT included in the ddk distribution and
that there is an ongoing issue with what exactly the compiler generates
for .sbr files vs what exactly some version or other of bscmake expects,
and what visual studio expects, so be careful about mix and matching
ddks and bscmakes and visual studios. Ugh. Couldn't they just include
bscmake in the ddk?
Also note that the Vista WDK beta (MSDN release build 5112) refuses to
run bscmake and thinks that BROWSER_INFO is a bad thing to put into your
sources file. The former is a bug while the latter is a feature that
ought to be a bug.
The new ddk bscmake features first show up in the 3790sp1 DDK but are
not totally broken in that ddk. There is a new command line flag for
setenv (bscmake) that if not set disallows (silently) bsc file
generation and that is also present but broken in the WDK beta ddk. The
WDK can be patched to fix things up so that it works.
Support for the setenv bscmake command line argument was wedged into
version 3.11.31 of ddkbuild.
David J. Craig wrote:
--
=====================
Mark Roddy DDK MVP
Windows 2003/XP/2000 Consulting
Hollis Technology Solutions 603-321-1032
www.hollistech.com
- Posted by Ray Trent on October 21st, 2005
Mark Roddy wrote:
Yeah, agreed (build 5231 seems to have the same behavior). Anyone from
MS listening (who's in the appropriate team, that is)?
Funny you should mention this, I've been cranking through the various
bat files and documentation lately trying to get this to work with no
luck as of yet (just haven't put in enough time on it yet, I guess)...
Could you provide instructions on how to hack the WDK so that it will
generate a browser file with DDKBUILD?
--
Ray
- Posted by Mark Roddy on October 25th, 2005
Ray Trent wrote:
works around this problem, appears to be perpetually scheduled for 'next
week'. I was about to bite the bullet and declare it 'good enough for
gummint work' when lo and behold a new version of the WDK appears and I
am back to square one. Oh well...
--
=====================
Mark Roddy DDK MVP
Windows 2003/XP/2000 Consulting
Hollis Technology Solutions 603-321-1032
www.hollistech.com
