M
Marc Champagne
Hi folks!
I have built a VB project in VS.NET 7 which also includes a
deployment project.
Everything builds ok.
When I install the setup package, it installs without a
glitch.
Then all subsequent runs of the application via any shortcut
that was made in deployment that refers to "Shortcut to
Primary output xxx (Active)", starts-up the installer which
then appears to cancels itself and then runs the application.
How can I bypass this type of shortcut and create a standard
one in deployment that will not kick in the installer every
time?
Thanks
I have built a VB project in VS.NET 7 which also includes a
deployment project.
Everything builds ok.
When I install the setup package, it installs without a
glitch.
Then all subsequent runs of the application via any shortcut
that was made in deployment that refers to "Shortcut to
Primary output xxx (Active)", starts-up the installer which
then appears to cancels itself and then runs the application.
How can I bypass this type of shortcut and create a standard
one in deployment that will not kick in the installer every
time?
Thanks