I transmit my project on WDK 6000.
The problem: I can’t build browser information.
I plaid with SOURCES keys BROWSERFILE, BROWSER_INFO,
USER_ENV_BROWSER_INFO, went through Internet and Documentation.
It is seen such as these options are not working form 6000 version. 
How to build Browser Information for driver with WDK 6000?
Thanks for Help,
Michael.
set BROWSER_INFO=1
You have to set the environment variable before calling “setenv.bat”
Christiaan
----- Original Message -----
From: “Grabelkovsky, Michael” <michael.grabelkovsky>
To: “Windows System Software Devs Interest List”
Sent: Thursday, May 03, 2007 5:27 PM
Subject: [ntdev] How to build Browser Information for driver with WDK 6000?
>I transmit my project on WDK 6000.
> The problem: I can’t build browser information.
>
> I plaid with SOURCES keys BROWSERFILE, BROWSER_INFO,
> USER_ENV_BROWSER_INFO, went through Internet and Documentation.
> It is seen such as these options are not working form 6000 version.
>
> How to build Browser Information for driver with WDK 6000?
>
> Thanks for Help,
> Michael.
>
> —
> Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
></michael.grabelkovsky>
Search NTDEV for WDK BROWSER_INFO and your first hit will be …
http://www.osronline.com/showThread.cfm?link=103307
… 
“Grabelkovsky, Michael” <michael.grabelkovsky> wrote in message
news:xxxxx@ntdev…
I transmit my project on WDK 6000.
The problem: I can’t build browser information.
I plaid with SOURCES keys BROWSERFILE, BROWSER_INFO,
USER_ENV_BROWSER_INFO, went through Internet and Documentation.
It is seen such as these options are not working form 6000 version.
How to build Browser Information for driver with WDK 6000?
Thanks for Help,
Michael.</michael.grabelkovsky>
set BROWSER_INFO=1 in the environment (not in SOURCES)
call setenv.bat with “bscmake” parameter (like setenv x:\winddk\6000 chk WLH bscmake)
make sure bscmake.exe is available for build. This is the hardest step because for some strange reasons bscmake tool isn’t included in the WDK installation. You can use the latest version from VS8 installation; VS7.1 should work as well. The problem are CRT DLLs; if you simply copy bscmake.exe to the directory with WDK compiler, it may not work because is linked against different DLL versions (I encountered this problem in the past). In this case you can add the directory with bscmake.exe to the PATH but make sure it is after WDK paths. Or copy it with appropriate runtime to the separate directory and this directory to the PATH.
With WDK 6000 bscmake.exe 8.00.50727.42 from VS 8.0 works for me (msvcr80.dll version in the bin\x86 directory is 8.00.50727.198). I simply copied it there.
Saying this I’d really like to know reason why such a basic tool isn’t included in the WDK. The argument you need VS to use BSC database is moot because MS provides a DLL which allows to access BSC info and some programmers editors use it.
Best regards,
Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]
From: xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com] on behalf of Grabelkovsky, Michael[SMTP:Michael.Grabelkovsky@ca.com]
Reply To: Windows System Software Devs Interest List
Sent: Thursday, May 03, 2007 5:27 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] How to build Browser Information for driver with WDK 6000?I transmit my project on WDK 6000.
The problem: I can’t build browser information.I plaid with SOURCES keys BROWSERFILE, BROWSER_INFO,
USER_ENV_BROWSER_INFO, went through Internet and Documentation.
It is seen such as these options are not working form 6000 version.How to build Browser Information for driver with WDK 6000?
Thanks for Help,
Michael.
Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
I raised this issue years ago when the DDK team did such a great job
with getting the toolset (well almost the toolset) into the DDK. The
answer was something about how this one utility would ruin the VS
revenue stream, or something to that effect. It seems that if we all had
bscmake in the DDK none of us would ever buy VS. Who knew? I’ve never
heard a good explanation for why it was held out.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Michal Vodicka
Sent: Thursday, May 03, 2007 12:14 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] How to build Browser Information for driver with
WDK 6000?
set BROWSER_INFO=1 in the environment (not in SOURCES)
call setenv.bat with “bscmake” parameter (like setenv x:\winddk\6000
chk WLH bscmake)
make sure bscmake.exe is available for build. This is the hardest
step because for some strange reasons bscmake tool isn’t included in the
WDK installation. You can use the latest version from VS8 installation;
VS7.1 should work as well. The problem are CRT DLLs; if you simply copy
bscmake.exe to the directory with WDK compiler, it may not work because
is linked against different DLL versions (I encountered this problem in
the past). In this case you can add the directory with bscmake.exe to
the PATH but make sure it is after WDK paths. Or copy it with
appropriate runtime to the separate directory and this directory to the
PATH.
With WDK 6000 bscmake.exe 8.00.50727.42 from VS 8.0 works for me
(msvcr80.dll version in the bin\x86 directory is 8.00.50727.198). I
simply copied it there.
Saying this I’d really like to know reason why such a basic tool isn’t
included in the WDK. The argument you need VS to use BSC database is
moot because MS provides a DLL which allows to access BSC info and some
programmers editors use it.
Best regards,
Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]
From:
xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com
] on behalf of Grabelkovsky, Michael[SMTP:Michael.Grabelkovsky@ca.com]
Reply To: Windows System Software Devs Interest List
Sent: Thursday, May 03, 2007 5:27 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] How to build Browser Information for driver with
WDK 6000?I transmit my project on WDK 6000.
The problem: I can’t build browser information.I plaid with SOURCES keys BROWSERFILE, BROWSER_INFO,
USER_ENV_BROWSER_INFO, went through Internet and Documentation.
It is seen such as these options are not working form 6000 version.
How to build Browser Information for driver with WDK 6000?
Thanks for Help,
Michael.
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
I hope once somebody responsible for WDK distribution realizes it is silly to not include this tool and will add it. I guess whole point to add compiler to the WDK was to make 3rd party drivers more stable and reliable. BSC info allows better orientation in the code, especially when based on WDK samples, which in turn leads to better productivity and code quality. I can hardly imagine to work without it and return to searching or how one examines code without a browser.
The answer you got is something I’d expect in a Dilbert strip…
Best regards,
Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]
From: xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com] on behalf of Roddy, Mark[SMTP:xxxxx@stratus.com]
Reply To: Windows System Software Devs Interest List
Sent: Thursday, May 03, 2007 8:52 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] How to build Browser Information for driver with WDK 6000?I raised this issue years ago when the DDK team did such a great job
with getting the toolset (well almost the toolset) into the DDK. The
answer was something about how this one utility would ruin the VS
revenue stream, or something to that effect. It seems that if we all had
bscmake in the DDK none of us would ever buy VS. Who knew? I’ve never
heard a good explanation for why it was held out.-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Michal Vodicka
Sent: Thursday, May 03, 2007 12:14 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] How to build Browser Information for driver with
WDK 6000?
set BROWSER_INFO=1 in the environment (not in SOURCES)
call setenv.bat with “bscmake” parameter (like setenv x:\winddk\6000
chk WLH bscmake)make sure bscmake.exe is available for build. This is the hardest
step because for some strange reasons bscmake tool isn’t included in the
WDK installation. You can use the latest version from VS8 installation;
VS7.1 should work as well. The problem are CRT DLLs; if you simply copy
bscmake.exe to the directory with WDK compiler, it may not work because
is linked against different DLL versions (I encountered this problem in
the past). In this case you can add the directory with bscmake.exe to
the PATH but make sure it is after WDK paths. Or copy it with
appropriate runtime to the separate directory and this directory to the
PATH.With WDK 6000 bscmake.exe 8.00.50727.42 from VS 8.0 works for me
(msvcr80.dll version in the bin\x86 directory is 8.00.50727.198). I
simply copied it there.Saying this I’d really like to know reason why such a basic tool isn’t
included in the WDK. The argument you need VS to use BSC database is
moot because MS provides a DLL which allows to access BSC info and some
programmers editors use it.Best regards,
Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]> ----------
> From:
xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com
] on behalf of Grabelkovsky, Michael[SMTP:Michael.Grabelkovsky@ca.com]
> Reply To: Windows System Software Devs Interest List
> Sent: Thursday, May 03, 2007 5:27 PM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] How to build Browser Information for driver with
WDK 6000?
>
> I transmit my project on WDK 6000.
> The problem: I can’t build browser information.
>
> I plaid with SOURCES keys BROWSERFILE, BROWSER_INFO,
> USER_ENV_BROWSER_INFO, went through Internet and Documentation.
> It is seen such as these options are not working form 6000 version.>
> How to build Browser Information for driver with WDK 6000?
>
> Thanks for Help,
> Michael.
> >
> —
> Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
>
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
I haven’t been following this thread very closely, so this is just an
offhand suggestion for an alternative to paying whatever it costs these
days for Visual Studio ($1000???). If you’re stuck and unwilling to pay
or at least pay immediately, you might want download a trial of
SlickEdit. I’ve used it for maybe four years (and CodeWright for six
more before that, which SlickEdit largely emulates), and, considering
only editing capabilities, I find it incomparably more enjoyable than
VS. To be clear, it offers nothing other than a very complete editor
package, at least compared to Windows editors (I’ve never used vi, for
example, and I don’t want to start the thread debating this); in
particular, it doesn’t have a debugger, Code Wizards, et. c. Salient to
this thread, it offers its own tag/symbol/reference management (in
addition to be able to use BSC files (allegedly, at least)). Although
SlickEdit’s CodeSense/auto-completion/member lookup facilities can go
haywire periodically (just rebuild the tag file), it has two very nice
features. The first is that you don’t need to build anything before
browsing works, and the second is that this (depending on what you are
doing) can speed up build times for impatient people like me. It offers
keyboard emulations for everything common, so the learning curve is
remarkably shallow. It has a ton of features, runs on Windows, OS X,
and a number of UNICIES, and is fully functional and free for thirty
days.
I just went to the website to get a download link, and, unfortunately,
the price seems to have doubled. It’s now $284.00, which, if you like
it, doesn’t even chart. However, if one of the limited versions of VS
(express?) will work, then the price may not be attractive.
Just something to consider.
http://www.slickedit.com/content/view/409/239/
mm
>> xxxxx@upek.com 2007-05-03 17:59 >>>
I hope once somebody responsible for WDK distribution realizes it is
silly to not include this tool and will add it. I guess whole point to
add compiler to the WDK was to make 3rd party drivers more stable and
reliable. BSC info allows better orientation in the code, especially
when based on WDK samples, which in turn leads to better productivity
and code quality. I can hardly imagine to work without it and return to
searching or how one examines code without a browser.
The answer you got is something I’d expect in a Dilbert strip…
Best regards,
Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]
From:
xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com]
on behalf of Roddy, Mark[SMTP:xxxxx@stratus.com]
Reply To: Windows System Software Devs Interest List
Sent: Thursday, May 03, 2007 8:52 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] How to build Browser Information for driver
with WDK 6000?I raised this issue years ago when the DDK team did such a great job
with getting the toolset (well almost the toolset) into the DDK. The
answer was something about how this one utility would ruin the VS
revenue stream, or something to that effect. It seems that if we all
had
bscmake in the DDK none of us would ever buy VS. Who knew? I’ve
never
heard a good explanation for why it was held out.-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Michal
Vodicka
Sent: Thursday, May 03, 2007 12:14 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] How to build Browser Information for driver
with
WDK 6000?
set BROWSER_INFO=1 in the environment (not in SOURCES)
call setenv.bat with “bscmake” parameter (like setenv
x:\winddk\6000
chk WLH bscmake)make sure bscmake.exe is available for build. This is the hardest
step because for some strange reasons bscmake tool isn’t included in
the
WDK installation. You can use the latest version from VS8
installation;
VS7.1 should work as well. The problem are CRT DLLs; if you simply
copy
bscmake.exe to the directory with WDK compiler, it may not work
because
is linked against different DLL versions (I encountered this problem
in
the past). In this case you can add the directory with bscmake.exe
to
the PATH but make sure it is after WDK paths. Or copy it with
appropriate runtime to the separate directory and this directory to
the
PATH.With WDK 6000 bscmake.exe 8.00.50727.42 from VS 8.0 works for me
(msvcr80.dll version in the bin\x86 directory is 8.00.50727.198). I
simply copied it there.Saying this I’d really like to know reason why such a basic tool
isn’t
included in the WDK. The argument you need VS to use BSC database is
moot because MS provides a DLL which allows to access BSC info and
some
programmers editors use it.Best regards,
Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]> ----------
> From:
xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com
] on behalf of Grabelkovsky,
Michael[SMTP:Michael.Grabelkovsky@ca.com]
> Reply To: Windows System Software Devs Interest List
> Sent: Thursday, May 03, 2007 5:27 PM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] How to build Browser Information for driver
with
WDK 6000?
>
> I transmit my project on WDK 6000.
> The problem: I can’t build browser information.
>
> I plaid with SOURCES keys BROWSERFILE, BROWSER_INFO,
> USER_ENV_BROWSER_INFO, went through Internet and Documentation.
> It is seen such as these options are not working form 6000 version.
>
> How to build Browser Information for driver with WDK 6000?
>
> Thanks for Help,
> Michael.
> >
> —
> Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
>
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Having used VSE for nearly 10 years, I completely agree…although I
wish I didn’t upgrade to the latest version
(v11). Compare to v9, v11 is a dog and completely unresponsive when
pushing tags or trying to do "intellisense"ish type matching (so much to
the point that I had to turn it off, while in previous versions I could
leave it on). If you can get pre v11 version, I would do that 
D
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Martin O’Brien
Sent: Thursday, May 03, 2007 3:38 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] How to build Browser Information for driver with
WDK 6000?
I haven’t been following this thread very closely, so this is just an
offhand suggestion for an alternative to paying whatever it costs these
days for Visual Studio ($1000???). If you’re stuck and unwilling to pay
or at least pay immediately, you might want download a trial of
SlickEdit. I’ve used it for maybe four years (and CodeWright for six
more before that, which SlickEdit largely emulates), and, considering
only editing capabilities, I find it incomparably more enjoyable than
VS. To be clear, it offers nothing other than a very complete editor
package, at least compared to Windows editors (I’ve never used vi, for
example, and I don’t want to start the thread debating this); in
particular, it doesn’t have a debugger, Code Wizards, et. c. Salient to
this thread, it offers its own tag/symbol/reference management (in
addition to be able to use BSC files (allegedly, at least)). Although
SlickEdit’s CodeSense/auto-completion/member lookup facilities can go
haywire periodically (just rebuild the tag file), it has two very nice
features. The first is that you don’t need to build anything before
browsing works, and the second is that this (depending on what you are
doing) can speed up build times for impatient people like me. It offers
keyboard emulations for everything common, so the learning curve is
remarkably shallow. It has a ton of features, runs on Windows, OS X,
and a number of UNICIES, and is fully functional and free for thirty
days.
I just went to the website to get a download link, and, unfortunately,
the price seems to have doubled. It’s now $284.00, which, if you like
it, doesn’t even chart. However, if one of the limited versions of VS
(express?) will work, then the price may not be attractive.
Just something to consider.
http://www.slickedit.com/content/view/409/239/
mm
>> xxxxx@upek.com 2007-05-03 17:59 >>>
I hope once somebody responsible for WDK distribution realizes it is
silly to not include this tool and will add it. I guess whole point to
add compiler to the WDK was to make 3rd party drivers more stable and
reliable. BSC info allows better orientation in the code, especially
when based on WDK samples, which in turn leads to better productivity
and code quality. I can hardly imagine to work without it and return to
searching or how one examines code without a browser.
The answer you got is something I’d expect in a Dilbert strip…
Best regards,
Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]
From:
xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com
]
on behalf of Roddy, Mark[SMTP:xxxxx@stratus.com]
Reply To: Windows System Software Devs Interest List
Sent: Thursday, May 03, 2007 8:52 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] How to build Browser Information for driver
with WDK 6000?I raised this issue years ago when the DDK team did such a great job
with getting the toolset (well almost the toolset) into the DDK. The
answer was something about how this one utility would ruin the VS
revenue stream, or something to that effect. It seems that if we all
had
bscmake in the DDK none of us would ever buy VS. Who knew? I’ve
never
heard a good explanation for why it was held out.-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Michal
Vodicka
Sent: Thursday, May 03, 2007 12:14 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] How to build Browser Information for driver
with
WDK 6000?
set BROWSER_INFO=1 in the environment (not in SOURCES)
call setenv.bat with “bscmake” parameter (like setenv
x:\winddk\6000
chk WLH bscmake)make sure bscmake.exe is available for build. This is the hardest
step because for some strange reasons bscmake tool isn’t included in
the
WDK installation. You can use the latest version from VS8
installation;
VS7.1 should work as well. The problem are CRT DLLs; if you simply
copy
bscmake.exe to the directory with WDK compiler, it may not work
because
is linked against different DLL versions (I encountered this problem
in
the past). In this case you can add the directory with bscmake.exe
to
the PATH but make sure it is after WDK paths. Or copy it with
appropriate runtime to the separate directory and this directory to
the
PATH.With WDK 6000 bscmake.exe 8.00.50727.42 from VS 8.0 works for me
(msvcr80.dll version in the bin\x86 directory is 8.00.50727.198). I
simply copied it there.Saying this I’d really like to know reason why such a basic tool
isn’t
included in the WDK. The argument you need VS to use BSC database is
moot because MS provides a DLL which allows to access BSC info and
some
programmers editors use it.Best regards,
Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]> ----------
> From:
xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com
] on behalf of Grabelkovsky,
Michael[SMTP:Michael.Grabelkovsky@ca.com]
> Reply To: Windows System Software Devs Interest List
> Sent: Thursday, May 03, 2007 5:27 PM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] How to build Browser Information for driver
with
WDK 6000?
>
> I transmit my project on WDK 6000.
> The problem: I can’t build browser information.
>
> I plaid with SOURCES keys BROWSERFILE, BROWSER_INFO,
> USER_ENV_BROWSER_INFO, went through Internet and Documentation.
> It is seen such as these options are not working form 6000 version.
>
> How to build Browser Information for driver with WDK 6000?
>
> Thanks for Help,
> Michael.
> >
> —
> Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
>
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Hey Martin, that was my point. You don’t need Visual Studio to use BSC files. So the “argument” Mark got is just ridiculous.
I use Multi-Edit for all development and BSC support works there. I’m quite sure because I wrote it Originally for myself and it was later added to the distribution.
Best regards,
Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]
From: xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com] on behalf of Martin O’Brien[SMTP:xxxxx@evitechnology.com]
Reply To: Windows System Software Devs Interest List
Sent: Friday, May 04, 2007 12:38 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] How to build Browser Information for driver with WDK 6000?I haven’t been following this thread very closely, so this is just an
offhand suggestion for an alternative to paying whatever it costs these
days for Visual Studio ($1000???). If you’re stuck and unwilling to pay
or at least pay immediately, you might want download a trial of
SlickEdit. I’ve used it for maybe four years (and CodeWright for six
more before that, which SlickEdit largely emulates), and, considering
only editing capabilities, I find it incomparably more enjoyable than
VS. To be clear, it offers nothing other than a very complete editor
package, at least compared to Windows editors (I’ve never used vi, for
example, and I don’t want to start the thread debating this); in
particular, it doesn’t have a debugger, Code Wizards, et. c. Salient to
this thread, it offers its own tag/symbol/reference management (in
addition to be able to use BSC files (allegedly, at least)). Although
SlickEdit’s CodeSense/auto-completion/member lookup facilities can go
haywire periodically (just rebuild the tag file), it has two very nice
features. The first is that you don’t need to build anything before
browsing works, and the second is that this (depending on what you are
doing) can speed up build times for impatient people like me. It offers
keyboard emulations for everything common, so the learning curve is
remarkably shallow. It has a ton of features, runs on Windows, OS X,
and a number of UNICIES, and is fully functional and free for thirty
days.I just went to the website to get a download link, and, unfortunately,
the price seems to have doubled. It’s now $284.00, which, if you like
it, doesn’t even chart. However, if one of the limited versions of VS
(express?) will work, then the price may not be attractive.Just something to consider.
http://www.slickedit.com/content/view/409/239/
mm
>>> xxxxx@upek.com 2007-05-03 17:59 >>>
I hope once somebody responsible for WDK distribution realizes it is
silly to not include this tool and will add it. I guess whole point to
add compiler to the WDK was to make 3rd party drivers more stable and
reliable. BSC info allows better orientation in the code, especially
when based on WDK samples, which in turn leads to better productivity
and code quality. I can hardly imagine to work without it and return to
searching or how one examines code without a browser.The answer you got is something I’d expect in a Dilbert strip…
Best regards,
Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]> ----------
> From:
xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com]
on behalf of Roddy, Mark[SMTP:xxxxx@stratus.com]
> Reply To: Windows System Software Devs Interest List
> Sent: Thursday, May 03, 2007 8:52 PM
> To: Windows System Software Devs Interest List
> Subject: RE: [ntdev] How to build Browser Information for driver
with WDK 6000?
>
> I raised this issue years ago when the DDK team did such a great job
> with getting the toolset (well almost the toolset) into the DDK. The>
> answer was something about how this one utility would ruin the VS
> revenue stream, or something to that effect. It seems that if we all
had
> bscmake in the DDK none of us would ever buy VS. Who knew? I’ve
never
> heard a good explanation for why it was held out.
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Michal
Vodicka
> Sent: Thursday, May 03, 2007 12:14 PM
> To: Windows System Software Devs Interest List
> Subject: RE: [ntdev] How to build Browser Information for driver
with
> WDK 6000?
>
> 1. set BROWSER_INFO=1 in the environment (not in SOURCES)
>
> 2. call setenv.bat with “bscmake” parameter (like setenv
x:\winddk\6000
> chk WLH bscmake)
>
> 3. make sure bscmake.exe is available for build. This is the hardest
> step because for some strange reasons bscmake tool isn’t included in
the
> WDK installation. You can use the latest version from VS8
installation;
> VS7.1 should work as well. The problem are CRT DLLs; if you simply
copy
> bscmake.exe to the directory with WDK compiler, it may not work
because
> is linked against different DLL versions (I encountered this problem
in
> the past). In this case you can add the directory with bscmake.exe
to
> the PATH but make sure it is after WDK paths. Or copy it with
> appropriate runtime to the separate directory and this directory to
the
> PATH.
>
> With WDK 6000 bscmake.exe 8.00.50727.42 from VS 8.0 works for me
> (msvcr80.dll version in the bin\x86 directory is 8.00.50727.198). I
> simply copied it there.
>
> Saying this I’d really like to know reason why such a basic tool
isn’t
> included in the WDK. The argument you need VS to use BSC database is
> moot because MS provides a DLL which allows to access BSC info and
some
> programmers editors use it.
>
> Best regards,
>
> Michal Vodicka
> UPEK, Inc.
> [xxxxx@upek.com, http://www.upek.com]
>
> > ----------
> > From:
>
xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com> ] on behalf of Grabelkovsky,
Michael[SMTP:Michael.Grabelkovsky@ca.com]
> > Reply To: Windows System Software Devs Interest List
> > Sent: Thursday, May 03, 2007 5:27 PM
> > To: Windows System Software Devs Interest List
> > Subject: [ntdev] How to build Browser Information for driver
with
> WDK 6000?
> >
> > I transmit my project on WDK 6000.
> > The problem: I can’t build browser information.
> >
> > I plaid with SOURCES keys BROWSERFILE, BROWSER_INFO,
> > USER_ENV_BROWSER_INFO, went through Internet and Documentation.
> > It is seen such as these options are not working form 6000 version.
>
> >
> > How to build Browser Information for driver with WDK 6000?
> >
> > Thanks for Help,
> > Michael.
> > >
> > —
> > Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
> >
> > To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
> >
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
> —
> Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
>
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256\>
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
Commendably impartial, Doron. I had been intending to look in to
upgrading, but hadn’t got around to it yet (probably not in a couple
versions). Personally, I gave up on Intellisense back in my CodeWright
days. While I really liked CodeWright, in particular the ability to
modify the source in satisfying but totally unnecessary ways (my
favorite was color coding matching nested parentheses), its behavior in
this are was downright pathalogical. To VisualStudio’s credit, it is
the only (C/C++) editor that I have used that actually works correctly
in this area; nothing else I have used even comes close, at least in my
experience, but I just can’t deal with the rest of it. It too has
gottten slower, and slower and slower, and the last time I looked at the
procedure for extending it I said no thanks. If they could fix this and
change the project tree so that it would allow you to (easily) create
multiple folders with the same name at different levels in the same
project, I would be a very satisfied customer. Unfortunately, both of
these issues have existed since my first version of SlickEdit (and
CodeWright for that matter, before Borland ran it in to the ground).
Leaving out intellisense, are there significant new features that you
do like?
mm
>> xxxxx@microsoft.com 2007-05-03 18:46 >>>
Having used VSE for nearly 10 years, I completely agree…although I
wish I didn’t upgrade to the latest version
(v11). Compare to v9, v11 is a dog and completely unresponsive when
pushing tags or trying to do "intellisense"ish type matching (so much
to
the point that I had to turn it off, while in previous versions I
could
leave it on). If you can get pre v11 version, I would do that
D
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Martin O’Brien
Sent: Thursday, May 03, 2007 3:38 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] How to build Browser Information for driver with
WDK 6000?
I haven’t been following this thread very closely, so this is just an
offhand suggestion for an alternative to paying whatever it costs
these
days for Visual Studio ($1000???). If you’re stuck and unwilling to
pay
or at least pay immediately, you might want download a trial of
SlickEdit. I’ve used it for maybe four years (and CodeWright for six
more before that, which SlickEdit largely emulates), and, considering
only editing capabilities, I find it incomparably more enjoyable than
VS. To be clear, it offers nothing other than a very complete editor
package, at least compared to Windows editors (I’ve never used vi, for
example, and I don’t want to start the thread debating this); in
particular, it doesn’t have a debugger, Code Wizards, et. c. Salient
to
this thread, it offers its own tag/symbol/reference management (in
addition to be able to use BSC files (allegedly, at least)). Although
SlickEdit’s CodeSense/auto-completion/member lookup facilities can go
haywire periodically (just rebuild the tag file), it has two very nice
features. The first is that you don’t need to build anything before
browsing works, and the second is that this (depending on what you
are
doing) can speed up build times for impatient people like me. It
offers
keyboard emulations for everything common, so the learning curve is
remarkably shallow. It has a ton of features, runs on Windows, OS X,
and a number of UNICIES, and is fully functional and free for thirty
days.
I just went to the website to get a download link, and, unfortunately,
the price seems to have doubled. It’s now $284.00, which, if you like
it, doesn’t even chart. However, if one of the limited versions of VS
(express?) will work, then the price may not be attractive.
Just something to consider.
http://www.slickedit.com/content/view/409/239/
mm
>> xxxxx@upek.com 2007-05-03 17:59 >>>
I hope once somebody responsible for WDK distribution realizes it is
silly to not include this tool and will add it. I guess whole point to
add compiler to the WDK was to make 3rd party drivers more stable and
reliable. BSC info allows better orientation in the code, especially
when based on WDK samples, which in turn leads to better productivity
and code quality. I can hardly imagine to work without it and return
to
searching or how one examines code without a browser.
The answer you got is something I’d expect in a Dilbert strip…
Best regards,
Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]
From:
xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com
]
on behalf of Roddy, Mark[SMTP:xxxxx@stratus.com]
Reply To: Windows System Software Devs Interest List
Sent: Thursday, May 03, 2007 8:52 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] How to build Browser Information for driver
with WDK 6000?I raised this issue years ago when the DDK team did such a great job
with getting the toolset (well almost the toolset) into the DDK. The
answer was something about how this one utility would ruin the VS
revenue stream, or something to that effect. It seems that if we all
had
bscmake in the DDK none of us would ever buy VS. Who knew? I’ve
never
heard a good explanation for why it was held out.-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Michal
Vodicka
Sent: Thursday, May 03, 2007 12:14 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] How to build Browser Information for driver
with
WDK 6000?
set BROWSER_INFO=1 in the environment (not in SOURCES)
call setenv.bat with “bscmake” parameter (like setenv
x:\winddk\6000
chk WLH bscmake)make sure bscmake.exe is available for build. This is the hardest
step because for some strange reasons bscmake tool isn’t included in
the
WDK installation. You can use the latest version from VS8
installation;
VS7.1 should work as well. The problem are CRT DLLs; if you simply
copy
bscmake.exe to the directory with WDK compiler, it may not work
because
is linked against different DLL versions (I encountered this problem
in
the past). In this case you can add the directory with bscmake.exe
to
the PATH but make sure it is after WDK paths. Or copy it with
appropriate runtime to the separate directory and this directory to
the
PATH.With WDK 6000 bscmake.exe 8.00.50727.42 from VS 8.0 works for me
(msvcr80.dll version in the bin\x86 directory is 8.00.50727.198). I
simply copied it there.Saying this I’d really like to know reason why such a basic tool
isn’t
included in the WDK. The argument you need VS to use BSC database is
moot because MS provides a DLL which allows to access BSC info and
some
programmers editors use it.Best regards,
Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]> ----------
> From:
xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com
] on behalf of Grabelkovsky,
Michael[SMTP:Michael.Grabelkovsky@ca.com]
> Reply To: Windows System Software Devs Interest List
> Sent: Thursday, May 03, 2007 5:27 PM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] How to build Browser Information for driver
with
WDK 6000?
>
> I transmit my project on WDK 6000.
> The problem: I can’t build browser information.
>
> I plaid with SOURCES keys BROWSERFILE, BROWSER_INFO,
> USER_ENV_BROWSER_INFO, went through Internet and Documentation.
> It is seen such as these options are not working form 6000
version.
>
> How to build Browser Information for driver with WDK 6000?
>
> Thanks for Help,
> Michael.
> >
> —
> Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
>
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
I like the vi emulation …but that is constant throughout all the
releases. I thought the newer versions would help with refactoring, but
that requires compiling within the editor, something that I can’t do b/c
of our build environment. I am not a power user, so there are probably
features I could use, but I don’t…so probably nothing useful to me
since v9.
d
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Martin O’Brien
Sent: Thursday, May 03, 2007 8:26 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] How to build Browser Information for driver with
WDK 6000?
Commendably impartial, Doron. I had been intending to look in to
upgrading, but hadn’t got around to it yet (probably not in a couple
versions). Personally, I gave up on Intellisense back in my CodeWright
days. While I really liked CodeWright, in particular the ability to
modify the source in satisfying but totally unnecessary ways (my
favorite was color coding matching nested parentheses), its behavior in
this are was downright pathalogical. To VisualStudio’s credit, it is
the only (C/C++) editor that I have used that actually works correctly
in this area; nothing else I have used even comes close, at least in my
experience, but I just can’t deal with the rest of it. It too has
gottten slower, and slower and slower, and the last time I looked at the
procedure for extending it I said no thanks. If they could fix this and
change the project tree so that it would allow you to (easily) create
multiple folders with the same name at different levels in the same
project, I would be a very satisfied customer. Unfortunately, both of
these issues have existed since my first version of SlickEdit (and
CodeWright for that matter, before Borland ran it in to the ground).
Leaving out intellisense, are there significant new features that you
do like?
mm
>> xxxxx@microsoft.com 2007-05-03 18:46 >>>
Having used VSE for nearly 10 years, I completely agree…although I
wish I didn’t upgrade to the latest version
(v11). Compare to v9, v11 is a dog and completely unresponsive when
pushing tags or trying to do "intellisense"ish type matching (so much
to
the point that I had to turn it off, while in previous versions I
could
leave it on). If you can get pre v11 version, I would do that
D
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Martin O’Brien
Sent: Thursday, May 03, 2007 3:38 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] How to build Browser Information for driver with
WDK 6000?
I haven’t been following this thread very closely, so this is just an
offhand suggestion for an alternative to paying whatever it costs
these
days for Visual Studio ($1000???). If you’re stuck and unwilling to
pay
or at least pay immediately, you might want download a trial of
SlickEdit. I’ve used it for maybe four years (and CodeWright for six
more before that, which SlickEdit largely emulates), and, considering
only editing capabilities, I find it incomparably more enjoyable than
VS. To be clear, it offers nothing other than a very complete editor
package, at least compared to Windows editors (I’ve never used vi, for
example, and I don’t want to start the thread debating this); in
particular, it doesn’t have a debugger, Code Wizards, et. c. Salient
to
this thread, it offers its own tag/symbol/reference management (in
addition to be able to use BSC files (allegedly, at least)). Although
SlickEdit’s CodeSense/auto-completion/member lookup facilities can go
haywire periodically (just rebuild the tag file), it has two very nice
features. The first is that you don’t need to build anything before
browsing works, and the second is that this (depending on what you
are
doing) can speed up build times for impatient people like me. It
offers
keyboard emulations for everything common, so the learning curve is
remarkably shallow. It has a ton of features, runs on Windows, OS X,
and a number of UNICIES, and is fully functional and free for thirty
days.
I just went to the website to get a download link, and, unfortunately,
the price seems to have doubled. It’s now $284.00, which, if you like
it, doesn’t even chart. However, if one of the limited versions of VS
(express?) will work, then the price may not be attractive.
Just something to consider.
http://www.slickedit.com/content/view/409/239/
mm
>> xxxxx@upek.com 2007-05-03 17:59 >>>
I hope once somebody responsible for WDK distribution realizes it is
silly to not include this tool and will add it. I guess whole point to
add compiler to the WDK was to make 3rd party drivers more stable and
reliable. BSC info allows better orientation in the code, especially
when based on WDK samples, which in turn leads to better productivity
and code quality. I can hardly imagine to work without it and return
to
searching or how one examines code without a browser.
The answer you got is something I’d expect in a Dilbert strip…
Best regards,
Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]
From:
xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com
]
on behalf of Roddy, Mark[SMTP:xxxxx@stratus.com]
Reply To: Windows System Software Devs Interest List
Sent: Thursday, May 03, 2007 8:52 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] How to build Browser Information for driver
with WDK 6000?I raised this issue years ago when the DDK team did such a great job
with getting the toolset (well almost the toolset) into the DDK. The
answer was something about how this one utility would ruin the VS
revenue stream, or something to that effect. It seems that if we all
had
bscmake in the DDK none of us would ever buy VS. Who knew? I’ve
never
heard a good explanation for why it was held out.-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Michal
Vodicka
Sent: Thursday, May 03, 2007 12:14 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] How to build Browser Information for driver
with
WDK 6000?
set BROWSER_INFO=1 in the environment (not in SOURCES)
call setenv.bat with “bscmake” parameter (like setenv
x:\winddk\6000
chk WLH bscmake)make sure bscmake.exe is available for build. This is the hardest
step because for some strange reasons bscmake tool isn’t included in
the
WDK installation. You can use the latest version from VS8
installation;
VS7.1 should work as well. The problem are CRT DLLs; if you simply
copy
bscmake.exe to the directory with WDK compiler, it may not work
because
is linked against different DLL versions (I encountered this problem
in
the past). In this case you can add the directory with bscmake.exe
to
the PATH but make sure it is after WDK paths. Or copy it with
appropriate runtime to the separate directory and this directory to
the
PATH.With WDK 6000 bscmake.exe 8.00.50727.42 from VS 8.0 works for me
(msvcr80.dll version in the bin\x86 directory is 8.00.50727.198). I
simply copied it there.Saying this I’d really like to know reason why such a basic tool
isn’t
included in the WDK. The argument you need VS to use BSC database is
moot because MS provides a DLL which allows to access BSC info and
some
programmers editors use it.Best regards,
Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]> ----------
> From:
xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com
] on behalf of Grabelkovsky,
Michael[SMTP:Michael.Grabelkovsky@ca.com]
> Reply To: Windows System Software Devs Interest List
> Sent: Thursday, May 03, 2007 5:27 PM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] How to build Browser Information for driver
with
WDK 6000?
>
> I transmit my project on WDK 6000.
> The problem: I can’t build browser information.
>
> I plaid with SOURCES keys BROWSERFILE, BROWSER_INFO,
> USER_ENV_BROWSER_INFO, went through Internet and Documentation.
> It is seen such as these options are not working form 6000
version.
>
> How to build Browser Information for driver with WDK 6000?
>
> Thanks for Help,
> Michael.
> >
> —
> Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
>
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Pretty much me either (my verison is a couple out of date).
thanks,
mm
>> xxxxx@microsoft.com 2007-05-04 00:00 >>>
I like the vi emulation
releases. I thought the newer versions would help with refactoring,
but
that requires compiling within the editor, something that I can’t do
b/c
of our build environment. I am not a power user, so there are
probably
features I could use, but I don’t…so probably nothing useful to me
since v9.
d
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Martin O’Brien
Sent: Thursday, May 03, 2007 8:26 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] How to build Browser Information for driver with
WDK 6000?
Commendably impartial, Doron. I had been intending to look in to
upgrading, but hadn’t got around to it yet (probably not in a couple
versions). Personally, I gave up on Intellisense back in my
CodeWright
days. While I really liked CodeWright, in particular the ability to
modify the source in satisfying but totally unnecessary ways (my
favorite was color coding matching nested parentheses), its behavior
in
this are was downright pathalogical. To VisualStudio’s credit, it is
the only (C/C++) editor that I have used that actually works correctly
in this area; nothing else I have used even comes close, at least in
my
experience, but I just can’t deal with the rest of it. It too has
gottten slower, and slower and slower, and the last time I looked at
the
procedure for extending it I said no thanks. If they could fix this
and
change the project tree so that it would allow you to (easily) create
multiple folders with the same name at different levels in the same
project, I would be a very satisfied customer. Unfortunately, both of
these issues have existed since my first version of SlickEdit (and
CodeWright for that matter, before Borland ran it in to the ground).
Leaving out intellisense, are there significant new features that you
do like?
mm
>> xxxxx@microsoft.com 2007-05-03 18:46 >>>
Having used VSE for nearly 10 years, I completely agree…although I
wish I didn’t upgrade to the latest version
(v11). Compare to v9, v11 is a dog and completely unresponsive when
pushing tags or trying to do "intellisense"ish type matching (so much
to
the point that I had to turn it off, while in previous versions I
could
leave it on). If you can get pre v11 version, I would do that
D
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Martin O’Brien
Sent: Thursday, May 03, 2007 3:38 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] How to build Browser Information for driver with
WDK 6000?
I haven’t been following this thread very closely, so this is just an
offhand suggestion for an alternative to paying whatever it costs
these
days for Visual Studio ($1000???). If you’re stuck and unwilling to
pay
or at least pay immediately, you might want download a trial of
SlickEdit. I’ve used it for maybe four years (and CodeWright for six
more before that, which SlickEdit largely emulates), and, considering
only editing capabilities, I find it incomparably more enjoyable than
VS. To be clear, it offers nothing other than a very complete editor
package, at least compared to Windows editors (I’ve never used vi, for
example, and I don’t want to start the thread debating this); in
particular, it doesn’t have a debugger, Code Wizards, et. c. Salient
to
this thread, it offers its own tag/symbol/reference management (in
addition to be able to use BSC files (allegedly, at least)). Although
SlickEdit’s CodeSense/auto-completion/member lookup facilities can go
haywire periodically (just rebuild the tag file), it has two very nice
features. The first is that you don’t need to build anything before
browsing works, and the second is that this (depending on what you
are
doing) can speed up build times for impatient people like me. It
offers
keyboard emulations for everything common, so the learning curve is
remarkably shallow. It has a ton of features, runs on Windows, OS X,
and a number of UNICIES, and is fully functional and free for thirty
days.
I just went to the website to get a download link, and, unfortunately,
the price seems to have doubled. It’s now $284.00, which, if you like
it, doesn’t even chart. However, if one of the limited versions of VS
(express?) will work, then the price may not be attractive.
Just something to consider.
http://www.slickedit.com/content/view/409/239/
mm
>> xxxxx@upek.com 2007-05-03 17:59 >>>
I hope once somebody responsible for WDK distribution realizes it is
silly to not include this tool and will add it. I guess whole point to
add compiler to the WDK was to make 3rd party drivers more stable and
reliable. BSC info allows better orientation in the code, especially
when based on WDK samples, which in turn leads to better productivity
and code quality. I can hardly imagine to work without it and return
to
searching or how one examines code without a browser.
The answer you got is something I’d expect in a Dilbert strip…
Best regards,
Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]
From:
xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com
]
on behalf of Roddy, Mark[SMTP:xxxxx@stratus.com]
Reply To: Windows System Software Devs Interest List
Sent: Thursday, May 03, 2007 8:52 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] How to build Browser Information for driver
with WDK 6000?I raised this issue years ago when the DDK team did such a great job
with getting the toolset (well almost the toolset) into the DDK. The
answer was something about how this one utility would ruin the VS
revenue stream, or something to that effect. It seems that if we all
had
bscmake in the DDK none of us would ever buy VS. Who knew? I’ve
never
heard a good explanation for why it was held out.-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Michal
Vodicka
Sent: Thursday, May 03, 2007 12:14 PM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] How to build Browser Information for driver
with
WDK 6000?
set BROWSER_INFO=1 in the environment (not in SOURCES)
call setenv.bat with “bscmake” parameter (like setenv
x:\winddk\6000
chk WLH bscmake)make sure bscmake.exe is available for build. This is the hardest
step because for some strange reasons bscmake tool isn’t included in
the
WDK installation. You can use the latest version from VS8
installation;
VS7.1 should work as well. The problem are CRT DLLs; if you simply
copy
bscmake.exe to the directory with WDK compiler, it may not work
because
is linked against different DLL versions (I encountered this problem
in
the past). In this case you can add the directory with bscmake.exe
to
the PATH but make sure it is after WDK paths. Or copy it with
appropriate runtime to the separate directory and this directory to
the
PATH.With WDK 6000 bscmake.exe 8.00.50727.42 from VS 8.0 works for me
(msvcr80.dll version in the bin\x86 directory is 8.00.50727.198). I
simply copied it there.Saying this I’d really like to know reason why such a basic tool
isn’t
included in the WDK. The argument you need VS to use BSC database is
moot because MS provides a DLL which allows to access BSC info and
some
programmers editors use it.Best regards,
Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]> ----------
> From:
xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com
] on behalf of Grabelkovsky,
Michael[SMTP:Michael.Grabelkovsky@ca.com]
> Reply To: Windows System Software Devs Interest List
> Sent: Thursday, May 03, 2007 5:27 PM
> To: Windows System Software Devs Interest List
> Subject: [ntdev] How to build Browser Information for driver
with
WDK 6000?
>
> I transmit my project on WDK 6000.
> The problem: I can’t build browser information.
>
> I plaid with SOURCES keys BROWSERFILE, BROWSER_INFO,
> USER_ENV_BROWSER_INFO, went through Internet and Documentation.
> It is seen such as these options are not working form 6000
version.
>
> How to build Browser Information for driver with WDK 6000?
>
> Thanks for Help,
> Michael.
> >
> —
> Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
>
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
Michal Vodicka wrote:
Hey Martin, that was my point. You don’t need Visual Studio to use
BSC files. So the “argument” Mark got is just ridiculous.
Actually, the ability to USE BSC files without Visual Studio completely
validates the argument Mark got: If you don’t need to purchase VS to
generate BSC files, more developers will do without it altogether, thus
reducing the amount of money going to the MSFT stock holders.
Another approach sometimes used by MS is to include the WDK only in
those MSDN levels which already include VS, thus making sure anyone
using the WDK toolchain has a fully paid-up VS license.
That said, it is sad that the VS team is so bad at cooperating with the
NT team, that the driver-certified toolchain (included in the WDK and
sometimes the SDK) doesn’t coexist better with the full-price but not
driver-certified toolchain. The mspdbsrv.exe fiasco is a classic example.
…
> xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com]
> on behalf of Roddy, Mark[SMTP:xxxxx@stratus.com]
>> Reply To: Windows System Software Devs Interest List Sent:
>> Thursday, May 03, 2007 8:52 PM To: Windows System Software Devs
>> Interest List Subject: RE: [ntdev] How to build Browser
>> Information for driver
> with WDK 6000?
>> I raised this issue years ago when the DDK team did such a great
>> job with getting the toolset (well almost the toolset) into the
>> DDK. The> answer was something about how this one utility would
>> ruin the VS revenue stream, or something to that effect. It seems
>> that if we all
> had
>> bscmake in the DDK none of us would ever buy VS. Who knew? I’ve
> never
>> heard a good explanation for why it was held out.
>>
–
Jakob B?hm, M.Sc.Eng. * xxxxx@danware.dk * direct tel:+45-45-90-25-33
Danware Data A/S * Bregnerodvej 127 * DK-3460 Birkerod * DENMARK
http://www.netop.com * tel:+45-45-90-25-25 * fax tel:+45-45-90-25-26
Information in this mail is hasty, not binding and may not be right
> -----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-285707-
xxxxx@lists.osr.com] On Behalf Of Jakob Bohm
Sent: Sunday, May 06, 2007 6:12 AM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] How to build Browser Information for driver with
WDK 6000?Michal Vodicka wrote:
> Hey Martin, that was my point. You don’t need Visual Studio to use
> BSC files. So the “argument” Mark got is just ridiculous.
>
Actually, the ability to USE BSC files without Visual Studio completely
validates the argument Mark got: If you don’t need to purchase VS to
generate BSC files, more developers will do without it altogether, thus
reducing the amount of money going to the MSFT stock holders.
“Completely validates” is a bit harsh. I’d say that it was at best a weak
argument that might cover about .01% of VS purchase decisions by driver
developers. “driver developers”: how big is that market? 1,000?
Companies doing this sort of development tend to have some sort of site
license arrangement that includes VS, or they just buy an MSDN subscription
for each developer that includes VS (and since the MSDN re-org that really
means they buy a VS subscription that includes MSDN.)
The end result is that one has to ‘go fish’ for the correct version of
bscmake and end up in the same fragile mess (although on a smaller scale)
that motivated packaging the toolchain with the ddk to begin with.