VS2008 *.reg file

  • Thread starter Thread starter AA2e72E
  • Start date Start date
A

AA2e72E

Is there a way to make VS2008 create a *.reg file when compiling a COM
Interrop DLL?

The compilation process creates the *.DLL file and registers it: it would be
useful to have the *.reg file to see the chanhes it makes to the Registry as
well as for deployment purposes.

Thanks.
 
AA2e72E said:
Is there a way to make VS2008 create a *.reg file when compiling a COM
Interrop DLL?
Click to expand...

Not as far as I know.
The compilation process creates the *.DLL file and registers it: it would be
useful to have the *.reg file to see the chanhes it makes to the Registry as
well as for deployment purposes.
Click to expand...

The DLL can self-register with regsvr32. You shouldn't need a .reg file
to register the DLL during deployment.

Pete
 
regsvr32?

My experience is that you need to use

regasm my.dll /codebase

for the DLL (I did say COM Interop) to be available as a server.

There is an option to acquire the *.reg file with

regasm my.dll /codebase /regfile:mydll.reg

I was hoping for a way to get VS2008 to create the mydll.reg file, perhaps
in the release folder.
 
Hi!


regasm my.dll /codebase /regfile:mydll.reg
Click to expand...
I was hoping for a way to get VS2008 to create the mydll.reg file, perhaps
in the release folder.
Click to expand...

Just check the Build Events options of your project. Did you try to run that
command in the "Post-build event command line"?

That way I would add special commands that I want the System to do
automatically inside the build. And through "Edit Post-build ..." button you
get access to the Macros (which are simply a set of predefined variables).

Hope this helps a little.

Konrad
 
Thanks for the hint Konrad.

I've never used build events: it is time for me to learn how to use them.
 
AA2e72E said:
regsvr32?

My experience is that you need to use

regasm my.dll /codebase

for the DLL (I did say COM Interop) to be available as a server.
Click to expand...

That's fine. It's basically the same idea as regsvr32. The point being
that you can register the DLL without dealing with a .reg file.

If you want to use regasm to register your DLL, just do that as part of
your deployment.

Pete
 
I specified as post build event (to be run on successful completion) as

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\regasm
$(TargetDir)\$(TargetFileName) codebase /regfile:$(TargetDir)\mydll.reg

It worked! Thanks for the hint.
 
Hi!

AA2e72E said:
I specified as post build event (to be run on successful completion) as

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\regasm
$(TargetDir)\$(TargetFileName) codebase
/regfile:$(TargetDir)\mydll.reg

It worked! Thanks for the hint.
Click to expand...

Great that I could help you.

But when deploying the DLL you should keep in mind what Peter told you.
It is better to use the right installation way instead of simply adding
some registry keys (But you never said that you need the reg file for a
deployment. So maybe you can simply ignore this comment.)

Konrad
 
Back
Top