| Groups | Blog | Home |
visual c : DllRegisterServer
>I am wondering when function DllRegisterServer will be invoked? Whenever something calls it! [quoted text, click to view] >1. During the build process or during the DLL initialization process? Does you build process have a step to call regsvr32 to register (i.e. call that function)? [quoted text, click to view] >2. I find this function only works for debug mode, not release mode. Is that >correct? It may only be getting called in the debug configuration of your project.
[quoted text, click to view]
>I do not explicitly call regsvr32 in build process. For the build process, I >simply use Visual Studio 2005 IDE to build. :-) > >I suspect regsvr32 invokes DllRegisterServer since I set the following >option to yes in debug configuration, > >Linker --> General --> Register Output to yes > >But I am not sure. Any comments? Yes, that's what that option does: "Register Output Run regsvr32.exe /s $(TargetPath), which is valid only on .dll projects. "
[quoted text, click to view]
>Where do you find the statements? > >> "Register Output >> Run regsvr32.exe /s $(TargetPath), which is valid only on .dll >> projects. >> " > >from MSDN or? I want to take a formal look. Thanks. Yes, it's in MSDN help - I just clicked the ? help icon in the caption bar of that property page.
Hello everyone,
I am wondering when function DllRegisterServer will be invoked? I am using Visual Studio 2005 to develop an in-process native (unmanaged) C++ COM. I am wondering when it will be invoked? 1. During the build process or during the DLL initialization process? 2. I find this function only works for debug mode, not release mode. Is that correct? In MSDN, http://msdn2.microsoft.com/en-us/library/ms682162.aspx there are not too much information about when this method will be invoked and whether it works for both debug mode code and release mode code. thanks in advance,
Thanks Dave,
I do not explicitly call regsvr32 in build process. For the build process, I simply use Visual Studio 2005 IDE to build. :-) I suspect regsvr32 invokes DllRegisterServer since I set the following option to yes in debug configuration, Linker --> General --> Register Output to yes But I am not sure. Any comments? regards, George [quoted text, click to view] "David Lowndes" wrote:
> >I am wondering when function DllRegisterServer will be invoked? > > Whenever something calls it! > > >1. During the build process or during the DLL initialization process? > > Does you build process have a step to call regsvr32 to register (i.e. > call that function)? > > >2. I find this function only works for debug mode, not release mode. Is that > >correct? > > It may only be getting called in the debug configuration of your > project. > > Dave
Thanks Dave,
Where do you find the statements? [quoted text, click to view] > "Register Output > Run regsvr32.exe /s $(TargetPath), which is valid only on .dll > projects. > " from MSDN or? I want to take a formal look. Thanks. regards, George [quoted text, click to view] "David Lowndes" wrote:
> >I do not explicitly call regsvr32 in build process. For the build process, I > >simply use Visual Studio 2005 IDE to build. :-) > > > >I suspect regsvr32 invokes DllRegisterServer since I set the following > >option to yes in debug configuration, > > > >Linker --> General --> Register Output to yes > > > >But I am not sure. Any comments? > > Yes, that's what that option does: > > "Register Output > Run regsvr32.exe /s $(TargetPath), which is valid only on .dll > projects. > " > > Dave
Thanks Dave,
I have found it. I think DllRegisterServer and Register output option should work for both debug version and release version, right? regards, George [quoted text, click to view] "David Lowndes" wrote:
> >Where do you find the statements? > > > >> "Register Output > >> Run regsvr32.exe /s $(TargetPath), which is valid only on .dll > >> projects. > >> " > > > >from MSDN or? I want to take a formal look. Thanks. > > Yes, it's in MSDN help - I just clicked the ? help icon in the caption > bar of that property page. > > Dave
Thanks for all the help, Dave!
regards, George [quoted text, click to view] "David Lowndes" wrote:
> >Thanks Dave, > > > >I have found it. I think DllRegisterServer and Register output option should > >work for both debug version and release version, right? > > There's no reason I can think of why they shouldn't! :) > > Dave
[quoted text, click to view]
"David Lowndes" <DavidL@example.invalid> wrote in message news:lrqbi39plp5j82afub1kk22nu7e2rut3q3@4ax.com... > >Thanks Dave, >> >>I have found it. I think DllRegisterServer and Register output option >>should >>work for both debug version and release version, right? > > There's no reason I can think of why they shouldn't! :) > > Dave Actually, the reason is because the installation software is supposed to register the DLL during installation. The debug version is setup to register the DLL for debugging. -- ============ Frank Hickman NobleSoft, Inc. ============ Replace the _nosp@m_ with @ to reply.
[quoted text, click to view]
>Thanks Dave, > >I have found it. I think DllRegisterServer and Register output option should >work for both debug version and release version, right? There's no reason I can think of why they shouldn't! :)
[quoted text, click to view]
"David Lowndes" <DavidL@example.invalid> wrote in message news:1f9ci314i9sjsp59apgp6fps8sg0325vbk@4ax.com... > >Actually, the reason is because the installation software is supposed to >>register the DLL during installation. The debug version is setup to >>register the DLL for debugging. > > Yes, that's the reason the default's are the way they are, but there's > nothing to prevent anyone changing it if they want to. > > Dave Very true. -- ============ Frank Hickman NobleSoft, Inc. ============ Replace the _nosp@m_ with @ to reply.
[quoted text, click to view]
>Actually, the reason is because the installation software is supposed to >register the DLL during installation. The debug version is setup to >register the DLL for debugging. Yes, that's the reason the default's are the way they are, but there's nothing to prevent anyone changing it if they want to.
Thanks Frank,
I think you mean there are some difference configurations for debug build and release build in Visual Studio 2005, which causes the different behavior, right? Could you point out what do you mean the different setting in Visual Studio 2005 which is the root cause please? regards, George [quoted text, click to view] "Frank Hickman" wrote:
> "David Lowndes" <DavidL@example.invalid> wrote in message > news:lrqbi39plp5j82afub1kk22nu7e2rut3q3@4ax.com... > > >Thanks Dave, > >> > >>I have found it. I think DllRegisterServer and Register output option > >>should > >>work for both debug version and release version, right? > > > > There's no reason I can think of why they shouldn't! :) > > > > Dave > > Actually, the reason is because the installation software is supposed to > register the DLL during installation. The debug version is setup to > register the DLL for debugging. > > -- > ============ > Frank Hickman > NobleSoft, Inc. > ============ > Replace the _nosp@m_ with @ to reply. > >
Thanks Frank,
I think if we set Linker->General->Register Output to true in release mode, it should also work, right? regards, George [quoted text, click to view] "Frank Hickman" wrote:
> "George" <George@discussions.microsoft.com> wrote in message > news:99FE747D-F5D5-43E8-8A2D-134C277F56F6@microsoft.com... > > Thanks Frank, > > > > > > I think you mean there are some difference configurations for debug build > > and release build in Visual Studio 2005, which causes the different > > behavior, > > right? Could you point out what do you mean the different setting in > > Visual > > Studio 2005 which is the root cause please? > > > > > > regards, > > George > > > > Just as you mentioned and David confirmed, the configuration setting > "Linker->General->Register Output" is set for the debug config and not the > release. This is by default the way it is set when the project is created > because of the previously mentioned reason. > > -- > ============ > Frank Hickman > NobleSoft, Inc. > ============ > Replace the _nosp@m_ with @ to reply. > >
[quoted text, click to view]
"George" <George@discussions.microsoft.com> wrote in message news:99FE747D-F5D5-43E8-8A2D-134C277F56F6@microsoft.com... > Thanks Frank, > > > I think you mean there are some difference configurations for debug build > and release build in Visual Studio 2005, which causes the different > behavior, > right? Could you point out what do you mean the different setting in > Visual > Studio 2005 which is the root cause please? > > > regards, > George > Just as you mentioned and David confirmed, the configuration setting "Linker->General->Register Output" is set for the debug config and not the release. This is by default the way it is set when the project is created because of the previously mentioned reason. -- ============ Frank Hickman NobleSoft, Inc. ============ Replace the _nosp@m_ with @ to reply.
[quoted text, click to view]
"George" <George@discussions.microsoft.com> wrote in message news:3ABF226E-6C6E-4202-B71D-8F9B7B5C9733@microsoft.com... > Thanks Frank, > > > I think if we set Linker->General->Register Output to true in release > mode, > it should also work, right? > > > regards, > George > Yes. -- ============ Frank Hickman NobleSoft, Inc. ============ Replace the _nosp@m_ with @ to reply.
[quoted text, click to view]
"Frank Hickman" <fhickman3_NOSP@M_noblesoft.net> wrote in message news:%23juoxIyGIHA.4712@TK2MSFTNGP04.phx.gbl... > "George" <George@discussions.microsoft.com> wrote in message > news:3ABF226E-6C6E-4202-B71D-8F9B7B5C9733@microsoft.com... >> Thanks Frank, >> >> >> I think if we set Linker->General->Register Output to true in release >> mode, >> it should also work, right? >> >> >> regards, >> George >> > > Yes. > I should mention that in a batch build, the debug version usually builds last by default, just the order the project settings are created when the project is created, so your debug version would be the one registered last. -- ============ Frank Hickman NobŸ/ft, Inc. ============ Replace the _nosp@m_ with @ to reply.
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |