Microsoft setup and deployment - launch an application at the end of installation

[Sue]

How do I launch an executable at the end of an installation created by
Microsoft Visual Studio setup and deployment project?

 

[Peter Rilling]

You might be able to create a custom action and use the Process class to
launch the application.

 

[Mike Wade [MSFT]]

There is no support within VS to do this. However, there is a topic in the Windows Installer Platform SDK help to do
this. See the link below (careful for linewrap).

http://msdn.microsoft.com/library/default.asp?url=/library/en-
us/msi/setup/how_do_i_use_a_custom_action_to_launch_an_installed_file_at_the_end_of_the_installation.asp

 

[Sue Dana]

Thanks a lot for the information.

I also have another question. I have a Visual Studio.net application,
which uses MSCOMM32.OCX. This control has license problem at runtime. Is
there any setup/installation steps to fix the problem. The application
works fine on a developer machine, but, displays license error on a
end-user machine.

Thanks again.

 

[Sue Dana]

Thanks a lot for the information.

I also have another question. I have a Visual Studio.net application,
which uses MSCOMM32.OCX. This control has license problem at runtime. Is
there any setup/installation steps to fix the problem. The application
works fine on a developer machine, but, displays license error on a
end-user machine.

Thanks again.

 

[Sergei Gnezdov]

Thanks a lot for the information.

I also have another question. I have a Visual Studio.net application,
which uses MSCOMM32.OCX. This control has license problem at runtime. Is
there any setup/installation steps to fix the problem. The application
works fine on a developer machine, but, displays license error on a
end-user machine.

Thanks again.

I am not an expert in ActiveX area, but here is what I am aware of:

You have to make sure that your OCX file does not have yellow icon
(warning) when you deploy the application.

Also, make sure that deployment project contains OCX file as its
dependency.

Any warning about OCX file sent to output during the build process
will result in problems with OCX file.

MS installation process will always unregister your OCX file every
time you uninstall your product with OCX. Building a product on a
machine which does not have OCX file registered will result in
problems as well.

I hope this helps...