I have an app that utilizes a DLL provided by a 3rd party. This DLL requires
registration via "regsvr32" before adding it successfully as a reference in
Visual Studio during development.
This DLL has been added to the deployment project such that it is placed in
the application directory up building the solution and subsequently
installing the app.
What is the appropriate/recommended method of having this DLL "register
itself" upon installation of the app on a target machine?
Its "register" property was set to "vsdrfCOM". This was clearly NOT the
correct option, or I have overlooked other details.
What is the correct approach.
BTW, afer installing the app and MANUALLY registering the DLL (regsvr32
....), all works great. What am I missing?
Thank you for your time....
--
Grumpy Aero Guy
registration via "regsvr32" before adding it successfully as a reference in
Visual Studio during development.
This DLL has been added to the deployment project such that it is placed in
the application directory up building the solution and subsequently
installing the app.
What is the appropriate/recommended method of having this DLL "register
itself" upon installation of the app on a target machine?
Its "register" property was set to "vsdrfCOM". This was clearly NOT the
correct option, or I have overlooked other details.
What is the correct approach.
BTW, afer installing the app and MANUALLY registering the DLL (regsvr32
....), all works great. What am I missing?
Thank you for your time....
--
Grumpy Aero Guy