Dll Build

I am trying to build a class installer dll and I want to use a .def file to
specify the exported functions. After looking at the SDK and some DDK
samples, I'm still a bit confused. How should I be building the dll: use
the command line utility included with the SDK or the VC++ build enviroment?
Is it just a matter of preference? I found a section in the MSDN library
about how to use a .def file in the VC++ IDE, but was unable to locate the
"project Property Page" to set the /DEF option. Can someone explain the
steps needed to export functions in a dll using either the VC++ IDE or
command line? Or point me to an article. Thank you for your time.

Maxim
Tue Oct 12 17:39:59 CDT 2004

I would use SOURCES to build such a DLL. In this case, no need to do
anything to include .DEF to a project - just put it in the same directory, and
all will be OK.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com

"Ben Geib" <BenGeib@discussions.microsoft.com> wrote in message
news:A95DBC57-58A5-4D93-B002-53B39F95B9D0@microsoft.com...
> I am trying to build a class installer dll and I want to use a .def file to
> specify the exported functions. After looking at the SDK and some DDK
> samples, I'm still a bit confused. How should I be building the dll: use
> the command line utility included with the SDK or the VC++ build enviroment?
> Is it just a matter of preference? I found a section in the MSDN library
> about how to use a .def file in the VC++ IDE, but was unable to locate the
> "project Property Page" to set the /DEF option. Can someone explain the
> steps needed to export functions in a dll using either the VC++ IDE or
> command line? Or point me to an article. Thank you for your time.

pavel_a
Tue Oct 12 18:53:01 CDT 2004

Visual Studio is a product totally independent from DDK or SDK.
Therefore, the DDK build process is independent from any version of Visual
Studio that happens to be installed on your machine.
Isn't this nice?

Visual Studio can build usermode DLLs, if you create a VS type project and
provide all nesessary headers and libs. Of course, some DDK headers may
require features that are not available in some versions of Visual Studio.

--PA

"Ben Geib" wrote:
> I am trying to build a class installer dll and I want to use a .def file to
> specify the exported functions. After looking at the SDK and some DDK
> samples, I'm still a bit confused. How should I be building the dll: use
> the command line utility included with the SDK or the VC++ build enviroment?
> Is it just a matter of preference? I found a section in the MSDN library
> about how to use a .def file in the VC++ IDE, but was unable to locate the
> "project Property Page" to set the /DEF option. Can someone explain the
> steps needed to export functions in a dll using either the VC++ IDE or
> command line? Or point me to an article. Thank you for your time.

BenGeib
Wed Oct 13 09:35:02 CDT 2004

Thanks for the info. You mentioned that Visual Studio can build usermode
DLLs. Are property page, co-installer, and class installer Dlls considered
to be user or kernel mode? I was planning on using the command line build
utility to build my class installer/property page provider, should I
therefore be using the enviroment/utility included with the SDK or DDK?
Thank you for your time.

"Pavel A." wrote:

> Visual Studio is a product totally independent from DDK or SDK.
> Therefore, the DDK build process is independent from any version of Visual
> Studio that happens to be installed on your machine.
> Isn't this nice?
>
> Visual Studio can build usermode DLLs, if you create a VS type project and
> provide all nesessary headers and libs. Of course, some DDK headers may
> require features that are not available in some versions of Visual Studio.
>
> --PA
>
> "Ben Geib" wrote:
> > I am trying to build a class installer dll and I want to use a .def file to
> > specify the exported functions. After looking at the SDK and some DDK
> > samples, I'm still a bit confused. How should I be building the dll: use
> > the command line utility included with the SDK or the VC++ build enviroment?
> > Is it just a matter of preference? I found a section in the MSDN library
> > about how to use a .def file in the VC++ IDE, but was unable to locate the
> > "project Property Page" to set the /DEF option. Can someone explain the
> > steps needed to export functions in a dll using either the VC++ IDE or
> > command line? Or point me to an article. Thank you for your time.

Maxim
Wed Oct 13 12:24:00 CDT 2004

> DLLs. Are property page, co-installer, and class installer Dlls considered
> to be user or kernel mode?

User.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com

pavel_a
Wed Oct 13 14:25:08 CDT 2004

"Ben Geib" wrote:
> Are property page, co-installer, and class installer Dlls considered
> to be user or kernel mode?

Pardon me, it is sort of sarcasm or are you serious.
The subset of English that I understand is very limited :(

> I was planning on using the command line build
> utility to build my class installer/property page provider, should I
> therefore be using the enviroment/utility included with the SDK or DDK?

The DDK build environment allows building all parts of project at once, both
kernel and usermode. Some people find it easier to develop and debug usermode
stuff in Visual Studio IDE and only then convert the project to DDK build
form.
Again, this can be not trivial because you need to replace all .H files and
libs from VS environment (or VS+SDK) to those provided with DDK, and be
prepared to handle compatibilty issues.

--PA