Win2K build environment in .NET RC2 DDK

NTDEV
1

Yesterday I took a WDM driver I’ve been developing and built it using
the Windows 2000, Windows XP, and Windows .NET DDK build environments of
the .NET RC2 DDK (both checked and free build for each) to be sure it
builds in all configurations. It built fine w/o any errors or warnings
in all cases.

Then I built it once more using the checked and free build environments
from the Windows 2000 DDK. This time I got a compiler warning in both
builds (something stupid).

Thus, it’s clear that there are some differences between the Windows
2000 build environments you get with Windows .NET RC2 DDK vs. what you
get with the original Windows 2000 DDK. Before I spend any time digging
into what’s different, has anybody else done this exercise?

Does the Windows 2000 build environment in the .NET RC2 DDK use the .NET
compiler bundled with the DDK, or does it use the Visual Studio compiler
installed on the machine like the Windows 2000 DDK build environments?

If the driver I am developing is targeted to ultimately be a single
binary that can run on Windows 2000, XP, Server 2003, and, hopefully on
Longhorn, when I am done with development and debug, which build
environment from which DDK should I use to build the final product?
Note that there is nothing in the driver that is OS version dependent,
and all of the variants built in the build environments for previous OS
versions have been tested and run fine on the later OS versions
(however, no attempt was made to test the other way around, that is, the
version built in the .NET build environment was not tested on Win2K).

I’m assuming it’s a choice between using the original Win2K DDK, or the
Win2K build environment in the .NET DDK, since the driver is targeted to
run on everything from Win2K forward. FYI, I’m assuming the final
Windows Server 2003 DDK will be out by the time this project is complete
(there is a lot of other non-driver related work still to be done), so
assuming it still includes a Win2K build environment, that’s also an
option.

Comments, thoughts, opinions, suggestions, rants, pontifications,
etc…?

  • Jay

Jay Talbott
Principal Consulting Engineer
SysPro Consulting, LLC
3519 E. South Fork Drive
Suite 201
Phoenix, AZ 85044
(480) 704-8045
xxxxx@sysproconsulting.com
http://www.sysproconsulting.com

2

The win2k ddk uses the vs compiler, the .net ddk uses its own compiler. I
suggest using the .net ddk for all w2k and later platforms, as it uses a
common toolset and it is a supported product.

On an almost unrelated topic, I’d almost suggest flushing visual studio ide
from your system, except that I have still not convinced myself that the
.net ide replacement is usable, that is if you even use an ide.

-----Original Message-----
From: Jay Talbott [mailto:xxxxx@sysproconsulting.com]
Sent: Thursday, January 30, 2003 11:35 AM
To: NT Developers Interest List
Subject: [ntdev] Win2K build environment in .NET RC2 DDK

Yesterday I took a WDM driver I’ve been developing and built
it using the Windows 2000, Windows XP, and Windows .NET DDK
build environments of the .NET RC2 DDK (both checked and free
build for each) to be sure it builds in all configurations.
It built fine w/o any errors or warnings in all cases.

Then I built it once more using the checked and free build
environments from the Windows 2000 DDK. This time I got a
compiler warning in both builds (something stupid).

Thus, it’s clear that there are some differences between the
Windows 2000 build environments you get with Windows .NET RC2
DDK vs. what you get with the original Windows 2000 DDK.
Before I spend any time digging into what’s different, has
anybody else done this exercise?

Does the Windows 2000 build environment in the .NET RC2 DDK
use the .NET compiler bundled with the DDK, or does it use
the Visual Studio compiler installed on the machine like the
Windows 2000 DDK build environments?

If the driver I am developing is targeted to ultimately be a
single binary that can run on Windows 2000, XP, Server 2003,
and, hopefully on Longhorn, when I am done with development
and debug, which build environment from which DDK should I
use to build the final product? Note that there is nothing in
the driver that is OS version dependent, and all of the
variants built in the build environments for previous OS
versions have been tested and run fine on the later OS
versions (however, no attempt was made to test the other way
around, that is, the version built in the .NET build
environment was not tested on Win2K).

I’m assuming it’s a choice between using the original Win2K
DDK, or the Win2K build environment in the .NET DDK, since
the driver is targeted to run on everything from Win2K
forward. FYI, I’m assuming the final Windows Server 2003 DDK
will be out by the time this project is complete (there is a
lot of other non-driver related work still to be done), so
assuming it still includes a Win2K build environment, that’s
also an option.

Comments, thoughts, opinions, suggestions, rants,
pontifications, etc…?

  • Jay

Jay Talbott
Principal Consulting Engineer
SysPro Consulting, LLC
3519 E. South Fork Drive
Suite 201
Phoenix, AZ 85044
(480) 704-8045
xxxxx@sysproconsulting.com
http://www.sysproconsulting.com

You are currently subscribed to ntdev as:
xxxxx@stratus.com To unsubscribe send a blank email to
xxxxx@lists.osr.com

3

What other differences are there besides the compiler version used?

  • Jay

Jay Talbott
Principal Consulting Engineer
SysPro Consulting, LLC
3519 E. South Fork Drive
Suite 201
Phoenix, AZ 85044
(480) 704-8045
xxxxx@sysproconsulting.com
http://www.sysproconsulting.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Roddy, Mark
Sent: Thursday, January 30, 2003 9:44 AM
To: NT Developers Interest List
Subject: [ntdev] RE: Win2K build environment in .NET RC2 DDK

The win2k ddk uses the vs compiler, the .net ddk uses its own
compiler. I
suggest using the .net ddk for all w2k and later platforms,
as it uses a
common toolset and it is a supported product.

On an almost unrelated topic, I’d almost suggest flushing
visual studio ide
from your system, except that I have still not convinced
myself that the
.net ide replacement is usable, that is if you even use an ide.

> -----Original Message-----
> From: Jay Talbott [mailto:xxxxx@sysproconsulting.com]
> Sent: Thursday, January 30, 2003 11:35 AM
> To: NT Developers Interest List
> Subject: [ntdev] Win2K build environment in .NET RC2 DDK
>
>
> Yesterday I took a WDM driver I’ve been developing and built
> it using the Windows 2000, Windows XP, and Windows .NET DDK
> build environments of the .NET RC2 DDK (both checked and free
> build for each) to be sure it builds in all configurations.
> It built fine w/o any errors or warnings in all cases.
>
> Then I built it once more using the checked and free build
> environments from the Windows 2000 DDK. This time I got a
> compiler warning in both builds (something stupid).
>
> Thus, it’s clear that there are some differences between the
> Windows 2000 build environments you get with Windows .NET RC2
> DDK vs. what you get with the original Windows 2000 DDK.
> Before I spend any time digging into what’s different, has
> anybody else done this exercise?
>
> Does the Windows 2000 build environment in the .NET RC2 DDK
> use the .NET compiler bundled with the DDK, or does it use
> the Visual Studio compiler installed on the machine like the
> Windows 2000 DDK build environments?
>
> If the driver I am developing is targeted to ultimately be a
> single binary that can run on Windows 2000, XP, Server 2003,
> and, hopefully on Longhorn, when I am done with development
> and debug, which build environment from which DDK should I
> use to build the final product? Note that there is nothing in
> the driver that is OS version dependent, and all of the
> variants built in the build environments for previous OS
> versions have been tested and run fine on the later OS
> versions (however, no attempt was made to test the other way
> around, that is, the version built in the .NET build
> environment was not tested on Win2K).
>
> I’m assuming it’s a choice between using the original Win2K
> DDK, or the Win2K build environment in the .NET DDK, since
> the driver is targeted to run on everything from Win2K
> forward. FYI, I’m assuming the final Windows Server 2003 DDK
> will be out by the time this project is complete (there is a
> lot of other non-driver related work still to be done), so
> assuming it still includes a Win2K build environment, that’s
> also an option.
>
> Comments, thoughts, opinions, suggestions, rants,
> pontifications, etc…?
>
> - Jay
>
> Jay Talbott
> Principal Consulting Engineer
> SysPro Consulting, LLC
> 3519 E. South Fork Drive
> Suite 201
> Phoenix, AZ 85044
> (480) 704-8045
> xxxxx@sysproconsulting.com
> http://www.sysproconsulting.com
>
>
>
> —
> You are currently subscribed to ntdev as:
> xxxxx@stratus.com To unsubscribe send a blank email to
> xxxxx@lists.osr.com
>

You are currently subscribed to ntdev as:
xxxxx@sysproconsulting.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

4

>

What other differences are there besides the compiler version used?

For building w2k drivers? Not much, other than the default directory
structure changed names just so everyone’s global build makefiles would get
broken :slight_smile:

The change I think is compelling is the single toolset. This has always been
the achilles heal of prior ddks. We out here in that small part of the world
that doesn’t work for BillG were always vulnerable to whimsy from the
compiler products division of the The One True and Universal Corporation.
The other thing is that the xp and soon the .net ddks are supported while
the w2k ddk isn’t even a download anymore. Oh and the docs are better.

  • Jay

Jay Talbott
Principal Consulting Engineer
SysPro Consulting, LLC
3519 E. South Fork Drive
Suite 201
Phoenix, AZ 85044
(480) 704-8045
xxxxx@sysproconsulting.com
http://www.sysproconsulting.com

> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Roddy, Mark
> Sent: Thursday, January 30, 2003 9:44 AM
> To: NT Developers Interest List
> Subject: [ntdev] RE: Win2K build environment in .NET RC2 DDK
>
>
> The win2k ddk uses the vs compiler, the .net ddk uses its own
> compiler. I
> suggest using the .net ddk for all w2k and later platforms,
> as it uses a
> common toolset and it is a supported product.
>
> On an almost unrelated topic, I’d almost suggest flushing
> visual studio ide
> from your system, except that I have still not convinced
> myself that the
> .net ide replacement is usable, that is if you even use an ide.
>
> > -----Original Message-----
> > From: Jay Talbott [mailto:xxxxx@sysproconsulting.com]
> > Sent: Thursday, January 30, 2003 11:35 AM
> > To: NT Developers Interest List
> > Subject: [ntdev] Win2K build environment in .NET RC2 DDK
> >
> >
> > Yesterday I took a WDM driver I’ve been developing and built
> > it using the Windows 2000, Windows XP, and Windows .NET DDK
> > build environments of the .NET RC2 DDK (both checked and free
> > build for each) to be sure it builds in all configurations.
> > It built fine w/o any errors or warnings in all cases.
> >
> > Then I built it once more using the checked and free build
> > environments from the Windows 2000 DDK. This time I got a
> > compiler warning in both builds (something stupid).
> >
> > Thus, it’s clear that there are some differences between the
> > Windows 2000 build environments you get with Windows .NET RC2
> > DDK vs. what you get with the original Windows 2000 DDK.
> > Before I spend any time digging into what’s different, has
> > anybody else done this exercise?
> >
> > Does the Windows 2000 build environment in the .NET RC2 DDK
> > use the .NET compiler bundled with the DDK, or does it use
> > the Visual Studio compiler installed on the machine like the
> > Windows 2000 DDK build environments?
> >
> > If the driver I am developing is targeted to ultimately be a
> > single binary that can run on Windows 2000, XP, Server 2003,
> > and, hopefully on Longhorn, when I am done with development
> > and debug, which build environment from which DDK should I
> > use to build the final product? Note that there is nothing in
> > the driver that is OS version dependent, and all of the
> > variants built in the build environments for previous OS
> > versions have been tested and run fine on the later OS
> > versions (however, no attempt was made to test the other way
> > around, that is, the version built in the .NET build
> > environment was not tested on Win2K).
> >
> > I’m assuming it’s a choice between using the original Win2K
> > DDK, or the Win2K build environment in the .NET DDK, since
> > the driver is targeted to run on everything from Win2K
> > forward. FYI, I’m assuming the final Windows Server 2003 DDK
> > will be out by the time this project is complete (there is a
> > lot of other non-driver related work still to be done), so
> > assuming it still includes a Win2K build environment, that’s
> > also an option.
> >
> > Comments, thoughts, opinions, suggestions, rants,
> > pontifications, etc…?
> >
> > - Jay
> >
> > Jay Talbott
> > Principal Consulting Engineer
> > SysPro Consulting, LLC
> > 3519 E. South Fork Drive
> > Suite 201
> > Phoenix, AZ 85044
> > (480) 704-8045
> > xxxxx@sysproconsulting.com http://www.sysproconsulting.com
> >
> >
> >
> > —
> > You are currently subscribed to ntdev as:
> > xxxxx@stratus.com To unsubscribe send a blank email to
> > xxxxx@lists.osr.com
> >
>
>
> —
> You are currently subscribed to ntdev as:
> xxxxx@sysproconsulting.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>

You are currently subscribed to ntdev as: xxxxx@stratus.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

5

> ----------

From: xxxxx@stratus.com[SMTP:xxxxx@stratus.com]
Reply To: xxxxx@lists.osr.com
Sent: Thursday, January 30, 2003 5:44 PM
To: xxxxx@lists.osr.com
Subject: [ntdev] RE: Win2K build environment in .NET RC2 DDK

On an almost unrelated topic, I’d almost suggest flushing visual studio
ide
from your system, except that I have still not convinced myself that the
.net ide replacement is usable, that is if you even use an ide.

I installed VS .NET recently (curiousness) and was shocked. It seems almost
unusable. Is anybody here using it for C/C++ or even driver development?

(sorry for off topic)

Best regards,

Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]

6

“Michal Vodicka” wrote in message
news:xxxxx@ntdev…
>
> > ----------
> > From: xxxxx@stratus.com[SMTP:xxxxx@stratus.com]
> > Reply To: xxxxx@lists.osr.com
> > Sent: Thursday, January 30, 2003 5:44 PM
> > To: xxxxx@lists.osr.com
> > Subject: [ntdev] RE: Win2K build environment in .NET RC2 DDK
> >
> > On an almost unrelated topic, I’d almost suggest flushing visual studio
> > ide
> > from your system, except that I have still not convinced myself that the
> > .net ide replacement is usable, that is if you even use an ide.
> >
> I installed VS .NET recently (curiousness) and was shocked. It seems
almost
> unusable. Is anybody here using it for C/C++ or even driver development?

I jump back and forth between VS.NET and SlickEdit. SlickEdit is almost
good enough for drivers, if you only build in one environment, because of
the way it handles preprocessing (very poorly). But it understands
templates better than VS.NET, so it can auto-complete things that confuse
VS.NET.

VS.NET, on the other hand, has a feature that was a very pleasant surprise.
It seems to use open files to augment the Intellisense db, so if you need
the DDK functions, open NTDDK.h or WDM.h, and it will auto-complete and
provide parameter info for most of the functions therein. I haven’t figured
out why it seems to miss a few, though. Although it seems a big step
backward in many respects, that is one that seems to be a step forward.

Phil
–
Philip D. Barila
Seagate Technology, LLC
(720) 684-1842
As if I need to say it: Not speaking for Seagate.

7

I do … using a makefile project and DDKBUILD. Functional but lots to be
desired.

I have experimented with the IDE and that seems to be VERY satisfactory. I
used Walters wizard to create a VS 6.0 driver project, “fixed” it, and then
added it to a solution under VS .NET. I then had to set a LINK switchg and
add the WinDDK executables to the directory paths. The driver does build…

–
Gary G. Little
Have Computer, will travel …
909-698-3191
909-551-2105

“Michal Vodicka” wrote in message
news:xxxxx@ntdev…
>
> > ----------
> > From: xxxxx@stratus.com[SMTP:xxxxx@stratus.com]
> > Reply To: xxxxx@lists.osr.com
> > Sent: Thursday, January 30, 2003 5:44 PM
> > To: xxxxx@lists.osr.com
> > Subject: [ntdev] RE: Win2K build environment in .NET RC2 DDK
> >
> > On an almost unrelated topic, I’d almost suggest flushing visual studio
> > ide
> > from your system, except that I have still not convinced myself that the
> > .net ide replacement is usable, that is if you even use an ide.
> >
> I installed VS .NET recently (curiousness) and was shocked. It seems
almost
> unusable. Is anybody here using it for C/C++ or even driver development?
>
> (sorry for off topic)
>
> Best regards,
>
> Michal Vodicka
> STMicroelectronics Design and Application s.r.o.
> [michal.vodicka@st.com, http:://www.st.com]
>
>
>
>
>
>

8

> ----------

From:
xxxxx@Seagate.com[SMTP:xxxxx@Seagate.com]
Reply To: xxxxx@lists.osr.com
Sent: Friday, January 31, 2003 1:08 AM
To: xxxxx@lists.osr.com
Subject: [ntdev] Re: Win2K build environment in .NET RC2 DDK

VS.NET, on the other hand, has a feature that was a very pleasant
surprise.
It seems to use open files to augment the Intellisense db, so if you need
the DDK functions, open NTDDK.h or WDM.h, and it will auto-complete and
provide parameter info for most of the functions therein. I haven’t
figured
out why it seems to miss a few, though. Although it seems a big step
backward in many respects, that is one that seems to be a step forward.

I believe it is also possible in VS 6.0 if you enable BSC database
(BROWSER_INFO=1 in SOURCES) which contains all symbols from all used
headers. I’m not quite sure because use Multi-Edit instead.

Best regards,

Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]

9

At 12:36 AM 1/31/2003 +0100, Michal Vodicka wrote:

> ----------
> From: xxxxx@stratus.com[SMTP:xxxxx@stratus.com]
> Reply To: xxxxx@lists.osr.com
> Sent: Thursday, January 30, 2003 5:44 PM
> To: xxxxx@lists.osr.com
> Subject: [ntdev] RE: Win2K build environment in .NET RC2 DDK
>
> On an almost unrelated topic, I’d almost suggest flushing visual studio
> ide
> from your system, except that I have still not convinced myself that the
> .net ide replacement is usable, that is if you even use an ide.
>
I installed VS .NET recently (curiousness) and was shocked. It seems almost
unusable. Is anybody here using it for C/C++ or even driver development?

I currently use VS .NET to develop our inhouse PCI board driver using
Driver Works. It works fine for me. The trick is getting the environment
setup right. I even built the Driver Works class library distribution using
the VS .NET IDE. I have VS solutions for both.

I can also build everything as a makefile project as well as an IDE project.

Russ Poffenberger
NPTest, Inc.
xxxxx@NPTest.com

10

I have been getting my feet wet with VS.NET.

My experience so far has been that existing VC++ 6.0 user mode C/C++
projects convert fairly painlessly to VC++ 7.0.

I have also been dabbling with writing managed C++ extensions to interface
existing APIs (exported from DLL) to the .NET frame work. Seems to be going
pretty well.

Also, I’m starting to like C# for user mode applications.

I don’t use the IDE for driver development at this time.

FWIW,

Thos

“Michal Vodicka” wrote in message
news:xxxxx@ntdev…
>
> > ----------
> > From: xxxxx@stratus.com[SMTP:xxxxx@stratus.com]
> > Reply To: xxxxx@lists.osr.com
> > Sent: Thursday, January 30, 2003 5:44 PM
> > To: xxxxx@lists.osr.com
> > Subject: [ntdev] RE: Win2K build environment in .NET RC2 DDK
> >
> > On an almost unrelated topic, I’d almost suggest flushing visual studio
> > ide
> > from your system, except that I have still not convinced myself that the
> > .net ide replacement is usable, that is if you even use an ide.
> >
> I installed VS .NET recently (curiousness) and was shocked. It seems
almost
> unusable. Is anybody here using it for C/C++ or even driver development?
>
> (sorry for off topic)
>
> Best regards,
>
> Michal Vodicka
> STMicroelectronics Design and Application s.r.o.
> [michal.vodicka@st.com, http:://www.st.com]
>
>
>
>
>
>

11

>

VS.NET, on the other hand, has a feature that was a very pleasant
surprise.
It seems to use open files to augment the Intellisense db, so if you need
the DDK functions, open NTDDK.h or WDM.h, and it will auto-complete and
provide parameter info for most of the functions therein. I haven’t
figured
out why it seems to miss a few, though. Although it seems a big step
backward in many respects, that is one that seems to be a step forward.

Phil

Philip D. Barila
Seagate Technology, LLC
(720) 684-1842
As if I need to say it: Not speaking for Seagate.

It seems , the .NET must be able to find them within is own include
path settings if you don 't want to miss them . No more nor less. Pay
also attention that it might popup definitions with the same name
which are defined in user-program headers if you don’t adapt the
include path.

Christiaan

You are currently subscribed to ntdev as: xxxxx@compaqnet.be
To unsubscribe send a blank email to xxxxx@lists.osr.com

12

Have any of you guys tried the MSVC add-on from Whole Tomato ? I think it’s
worth a shot.

Alberto.

-----Original Message-----
From: Michal Vodicka [mailto:xxxxx@veridicom.cz.nospam]
Sent: Thursday, January 30, 2003 7:29 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Win2K build environment in .NET RC2 DDK

From:
xxxxx@Seagate.com[SMTP:xxxxx@Seagate.com]
Reply To: xxxxx@lists.osr.com
Sent: Friday, January 31, 2003 1:08 AM
To: xxxxx@lists.osr.com
Subject: [ntdev] Re: Win2K build environment in .NET RC2 DDK

VS.NET, on the other hand, has a feature that was a very pleasant
surprise.
It seems to use open files to augment the Intellisense db, so if you need
the DDK functions, open NTDDK.h or WDM.h, and it will auto-complete and
provide parameter info for most of the functions therein. I haven’t
figured
out why it seems to miss a few, though. Although it seems a big step
backward in many respects, that is one that seems to be a step forward.

I believe it is also possible in VS 6.0 if you enable BSC database
(BROWSER_INFO=1 in SOURCES) which contains all symbols from all used
headers. I’m not quite sure because use Multi-Edit instead.

Best regards,

Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]

You are currently subscribed to ntdev as: xxxxx@compuware.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it.

13

“Michal Vodicka” wrote in message
news:xxxxx@ntdev…
>
> > ----------
> > From:
> > xxxxx@Seagate.com[SMTP:xxxxx@Seagate.com]
> > Reply To: xxxxx@lists.osr.com
> > Sent: Friday, January 31, 2003 1:08 AM
> > To: xxxxx@lists.osr.com
> > Subject: [ntdev] Re: Win2K build environment in .NET RC2 DDK
> >
> > VS.NET, on the other hand, has a feature that was a very pleasant
> > surprise.
> > It seems to use open files to augment the Intellisense db, so if you
need
> > the DDK functions, open NTDDK.h or WDM.h, and it will auto-complete and
> > provide parameter info for most of the functions therein. I haven’t
> > figured
> > out why it seems to miss a few, though. Although it seems a big step
> > backward in many respects, that is one that seems to be a step forward.
> >
> I believe it is also possible in VS 6.0 if you enable BSC database
> (BROWSER_INFO=1 in SOURCES) which contains all symbols from all used
> headers. I’m not quite sure because use Multi-Edit instead.

That allowed you to get definitions and references, but it didn’t enable any
autocompletion.

Phil
–
Philip D. Barila
Seagate Technology, LLC
(720) 684-1842
As if I need to say it: Not speaking for Seagate.

14

Michal,

Yes, I use it all the time. It works.

Alberto.

-----Original Message-----
From: Michal Vodicka [mailto:xxxxx@veridicom.cz.nospam]
Sent: Thursday, January 30, 2003 6:36 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Win2K build environment in .NET RC2 DDK

From: xxxxx@stratus.com[SMTP:xxxxx@stratus.com]
Reply To: xxxxx@lists.osr.com
Sent: Thursday, January 30, 2003 5:44 PM
To: xxxxx@lists.osr.com
Subject: [ntdev] RE: Win2K build environment in .NET RC2 DDK

On an almost unrelated topic, I’d almost suggest flushing visual studio
ide
from your system, except that I have still not convinced myself that the
.net ide replacement is usable, that is if you even use an ide.

I installed VS .NET recently (curiousness) and was shocked. It seems almost
unusable. Is anybody here using it for C/C++ or even driver development?

(sorry for off topic)

Best regards,

Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]

You are currently subscribed to ntdev as: xxxxx@compuware.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it.

15

Me too.
I’ve been using it (VisualAssist) for the last year and a half, with
VS6, for driver development.
Wouldn’t want to miss it now - highly recommended.

BTW: I also tried out VS.NET and got it to work with DDKBUILD without
major difficulties.
As others have noted here, the interface is a bit different to VS6…
but not so much as to
persuade me, in the absense of other factors, one way or the other.

As it happens, I’m sticking with VS6 mainly because I don’t (yet) have
VisualAssist.NET

My 0.02EUR

jim

Jim Spriggs
Software Consultant
Currently hacking lasers.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Moreira, Alberto
Sent: Freitag, 31. Januar 2003 17:03
To: NT Developers Interest List
Subject: [ntdev] Re: Win2K build environment in .NET RC2 DDK

Have any of you guys tried the MSVC add-on from Whole Tomato ? I think
it’s
worth a shot.

Alberto.

-----Original Message-----
From: Michal Vodicka [mailto:xxxxx@veridicom.cz.nospam]
Sent: Thursday, January 30, 2003 7:29 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Win2K build environment in .NET RC2 DDK

> ----------
> From:
> xxxxx@Seagate.com[SMTP:xxxxx@Seagate.com]
> Reply To: xxxxx@lists.osr.com
> Sent: Friday, January 31, 2003 1:08 AM
> To: xxxxx@lists.osr.com
> Subject: [ntdev] Re: Win2K build environment in .NET RC2 DDK
>
> VS.NET, on the other hand, has a feature that was a very pleasant
> surprise.
> It seems to use open files to augment the Intellisense db, so if you
need
> the DDK functions, open NTDDK.h or WDM.h, and it will auto-complete
and
> provide parameter info for most of the functions therein. I haven’t
> figured
> out why it seems to miss a few, though. Although it seems a big step
> backward in many respects, that is one that seems to be a step
forward.
>
I believe it is also possible in VS 6.0 if you enable BSC database
(BROWSER_INFO=1 in SOURCES) which contains all symbols from all used
headers. I’m not quite sure because use Multi-Edit instead.

Best regards,

Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]

—
You are currently subscribed to ntdev as: xxxxx@compuware.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

The contents of this e-mail are intended for the named addressee only.
It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or
disclose
it to anyone else. If you received it in error please notify us
immediately
and then destroy it.

—
You are currently subscribed to ntdev as: xxxxx@t-online.de
To unsubscribe send a blank email to xxxxx@lists.osr.com

16

Alberto,

yes, it works. It would be very bad if doesn’t. I meant user interface which
seems bloated, slow and very inefficient to use. There are even some old
good functions missing. Well, I’m biased because even VS6 with Visual Assist
wasn’t good enough for me. I was only suprised with the fact that new
version seems worse than older. Other replies indicate that opinions may
differ.

On the other hand, I appreciate new compiler (also DDK version) and STL
update conforming to standard (finally!).

Best regards,

Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]

From:
xxxxx@compuware.com[SMTP:xxxxx@compuware.com]
Reply To: xxxxx@lists.osr.com
Sent: Friday, January 31, 2003 5:05 PM
To: xxxxx@lists.osr.com
Subject: [ntdev] RE: Win2K build environment in .NET RC2 DDK

Michal,

Yes, I use it all the time. It works.

Alberto.

-----Original Message-----
From: Michal Vodicka [mailto:xxxxx@veridicom.cz.nospam]
Sent: Thursday, January 30, 2003 6:36 PM
To: NT Developers Interest List
Subject: [ntdev] RE: Win2K build environment in .NET RC2 DDK

> ----------
> From: xxxxx@stratus.com[SMTP:xxxxx@stratus.com]
> Reply To: xxxxx@lists.osr.com
> Sent: Thursday, January 30, 2003 5:44 PM
> To: xxxxx@lists.osr.com
> Subject: [ntdev] RE: Win2K build environment in .NET RC2 DDK
>
> On an almost unrelated topic, I’d almost suggest flushing visual studio
> ide
> from your system, except that I have still not convinced myself that the
> .net ide replacement is usable, that is if you even use an ide.
>
I installed VS .NET recently (curiousness) and was shocked. It seems
almost
unusable. Is anybody here using it for C/C++ or even driver development?

(sorry for off topic)

Best regards,

Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]

You are currently subscribed to ntdev as: xxxxx@compuware.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or
disclose
it to anyone else. If you received it in error please notify us
immediately
and then destroy it.

You are currently subscribed to ntdev as: michal.vodicka@st.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

17

On Fri, 2003-01-31 at 16:26, Michal Vodicka wrote:

good functions missing. Well, I’m biased because even VS6 with Visual Assist
wasn’t good enough for me.

Wow, then what *do* you use, if you don’t mind me asking? We mostly use
vim around my office, but i tried the visual assist plugin on alberto’s
recommendation and found it to be really good.

-sd

18

> ----------

From:
xxxxx@positivenetworks.net[SMTP:xxxxx@positivenetworks.net]
Reply To: xxxxx@lists.osr.com
Sent: Friday, January 31, 2003 11:45 PM
To: xxxxx@lists.osr.com
Subject: [ntdev] RE: Win2K build environment in .NET RC2 DDK

On Fri, 2003-01-31 at 16:26, Michal Vodicka wrote:
> good functions missing. Well, I’m biased because even VS6 with Visual
Assist
> wasn’t good enough for me.

Wow, then what *do* you use, if you don’t mind me asking? We mostly use
vim around my office, but i tried the visual assist plugin on alberto’s
recommendation and found it to be really good.

Multi-Edit. Partially for historical reasons (I use different versions
almost 15 years) and mainly because it is totally customisable. Everything
can be mapped to a hotkey and mouse is unnecessary for editing. It is no
problem to add a new compiler or build utility or even programming language
(not needed because almost everything is already included). And if something
is missing, user can write it in C-like macro language (several years before
I wrote support for BSC based browsing, now included in release).

Visual Assist isn’t bad but because it is integrated to VS, mouse is
necessary which makes editing inefficient.

Best regards,

Michal Vodicka
STMicroelectronics Design and Application s.r.o.
[michal.vodicka@st.com, http:://www.st.com]