By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
458,221 Members | 1,144 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 458,221 IT Pros & Developers. It's quick & easy.

VS.NET 7 - Deployment Project Blues

P: n/a
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
Jul 21 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
I don't think there is any way to create a "standard" shortcut within the project itself. You could probably write
code to do that, and then add that as a custom action. Check out:
http://msdn.microsoft.com/library/de...teshortcut.asp
to get you started.

Have you investigated why the installer starts up when you use the shortcut, and addressed the situation that
way? The best place to start that investigation woul be to look at the Application section of the Event Viewer on
your OS.
--
Mike Wade, VB Team
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
Newsgroups: microsoft.public.dotnet.general
Subject: VS.NET 7 - Deployment Project Blues
From: Marc Champagne <ne**@ctldirect.DOT.com.invalid>
Date: Tue, 28 Oct 2003 17:16:43 GMT

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


Jul 21 '05 #2

P: n/a
mw***@online.microsoft.com (Mike Wade [MSFT]) wrote in
news:Pk*************@cpmsftngxa06.phx.gbl:
I don't think there is any way to create a "standard"
shortcut within the project itself. You could probably
write code to do that, and then add that as a custom
action. Check out:
http://msdn.microsoft.com/library/de...url=/library/e
n-us/script56/html/wsmthcreateshortcut.asp to get you
started.

Have you investigated why the installer starts up when you
use the shortcut, and addressed the situation that way?
The best place to start that investigation woul be to look
at the Application section of the Event Viewer on your OS.


Bingo! did not think of looking there. both default registry
entries were set (always create: false).

Changed them to true and voila, the trick is in the bag.

Thanks

--
Marc Champagne
marcch.AT.videoSPAMNOTtron.DOT.ca.invalid
Montreal, Canada
Jul 21 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.