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

VB2005 - Setup Project => Add an uninstall icon in 'All Programs' ?

P: n/a
Hi ,

not much trouble in making a setup project, but I'd like also an icon in All
Programs
to uninstall the application. I can't find a good explanation on the net so
far...

--
Filip
http://www.ww2airborne.net/
Official Site of the 101st Airborne - 463rd PFA
skype: airborne463pfa-fiwi

P.S. Sorry I multiposted also in microsoft.public.dotnet.languages.vb, but I
didn't get an answer from anybody...
so I thoughtabout trying it here as well... :-/
Oct 4 '06 #1
Share this Question
Share on Google+
5 Replies

P: n/a
Hi,

Take a look at the following link; The /x switch in particular might be of interest to you:

Msiexec command line options on MSDN:
http://msdn.microsoft.com/library/de...ne_options.asp

You can obtain the product code for your setup project by selecting the project node in Solution Explorer and locating the
ProductCode row in the property window.

1. Try creating a batch file that executes the msiexec program with the appropriate command line arguments to uninstall your
application.
2. Add the batch file to the installer under the Application Folder in the File System Editor.
3. Create a shortcut to the batch file:
A. Browse to your application's folder under Programs Menu, or wherever you would like the shortcut to exist
B. Right mouse click the empty area of the File System Editor and select Create Shortcut; Browse to batch file.

Please let us know if that works for you.

--
Dave Sexton

" Screaming Eagles 101" <se*********@online.pleasewrote in message news:B7******************************@scarlet.biz. ..
Hi ,

not much trouble in making a setup project, but I'd like also an icon in All
Programs
to uninstall the application. I can't find a good explanation on the net so
far...

--
Filip
http://www.ww2airborne.net/
Official Site of the 101st Airborne - 463rd PFA
skype: airborne463pfa-fiwi

P.S. Sorry I multiposted also in microsoft.public.dotnet.languages.vb, but I didn't get an answer from anybody...
so I thoughtabout trying it here as well... :-/

Oct 5 '06 #2

P: n/a
"Dave Sexton" <dave@jwa[remove.this]online.comschreef in bericht
news:e6**************@TK2MSFTNGP03.phx.gbl...
Hi,

Take a look at the following link; The /x switch in particular might be
of interest to you:

Msiexec command line options on MSDN:
http://msdn.microsoft.com/library/de...ne_options.asp

You can obtain the product code for your setup project by selecting the
project node in Solution Explorer and locating the ProductCode row in the
property window.

1. Try creating a batch file that executes the msiexec program with the
appropriate command line arguments to uninstall your application.
2. Add the batch file to the installer under the Application Folder in the
File System Editor.
3. Create a shortcut to the batch file:
A. Browse to your application's folder under Programs Menu, or wherever
you would like the shortcut to exist
B. Right mouse click the empty area of the File System Editor and
select Create Shortcut; Browse to batch file.

Please let us know if that works for you.

--
Dave Sexton

" Screaming Eagles 101" <se*********@online.pleasewrote in message
news:B7******************************@scarlet.biz. ..
<<cut>>
>
Thanks,

this seems to work fine, except for the command window executing the bat
file, so for a start I minimised it at start-up. By adding START in the BAT
file
just before the MSIEXEC command
syntax, and an EXIT on the 2nd command line behind that,
the command window opens only for a sec (in the taskbar only), which is
acceptable...
Thanks
--
Filip
http://www.ww2airborne.net/
Official Site of the 101st Airborne - 463rd PFA
skype: airborne463pfa-fiwi
-------------------------------------------------

Oct 5 '06 #3

P: n/a
Hi,

START was a good idea. Thanks for the follow-up.

I know you said the window flashing in the task bar is acceptable, but if you really don't like it you could always put together a
small .NET program to do the trick without any interface. Just make a WinForms project and don't show any forms.

HTH

--
Dave Sexton

" Screaming Eagles 101" <se*********@online.pleasewrote in message news:Q4********************@scarlet.biz...
"Dave Sexton" <dave@jwa[remove.this]online.comschreef in bericht
news:e6**************@TK2MSFTNGP03.phx.gbl...
>Hi,

Take a look at the following link; The /x switch in particular might be
of interest to you:

Msiexec command line options on MSDN:
http://msdn.microsoft.com/library/de...ne_options.asp

You can obtain the product code for your setup project by selecting the
project node in Solution Explorer and locating the ProductCode row in the
property window.

1. Try creating a batch file that executes the msiexec program with the
appropriate command line arguments to uninstall your application.
2. Add the batch file to the installer under the Application Folder in the
File System Editor.
3. Create a shortcut to the batch file:
A. Browse to your application's folder under Programs Menu, or wherever
you would like the shortcut to exist
B. Right mouse click the empty area of the File System Editor and
select Create Shortcut; Browse to batch file.

Please let us know if that works for you.

--
Dave Sexton

" Screaming Eagles 101" <se*********@online.pleasewrote in message
news:B7******************************@scarlet.biz ...
<<cut>>
>>
Thanks,

this seems to work fine, except for the command window executing the bat
file, so for a start I minimised it at start-up. By adding START in the BAT file
just before the MSIEXEC command
syntax, and an EXIT on the 2nd command line behind that,
the command window opens only for a sec (in the taskbar only), which is acceptable...
Thanks
--
Filip
http://www.ww2airborne.net/
Official Site of the 101st Airborne - 463rd PFA
skype: airborne463pfa-fiwi
-------------------------------------------------

Oct 5 '06 #4

P: n/a

"Dave Sexton" <dave@jwa[remove.this]online.comschreef in bericht
news:ev**************@TK2MSFTNGP06.phx.gbl...
Hi,

START was a good idea. Thanks for the follow-up.

I know you said the window flashing in the task bar is acceptable, but if
you really don't like it you could always put together a small .NET
program to do the trick without any interface. Just make a WinForms
project and don't show any forms.

HTH

--
Dave Sexton

That's an excellent idea.
In VB6 it's done with WinExec I think (to start another application), but I
didn't make anything like it in .net just yet, but I 'm confident I'll find
that line of code easily on the net, won't be much trouble.
Thanks for the idea !
--
Filip
http://www.ww2airborne.net/
Official Site of the 101st Airborne - 463rd PFA
skype: airborne463pfa-fiwi
-------------------------------------------------
Oct 6 '06 #5

P: n/a
" Screaming Eagles 101" <se*********@online.pleaseschreef in bericht
news:Kb******************************@scarlet.biz. ..
>
"Dave Sexton" <dave@jwa[remove.this]online.comschreef in bericht
news:ev**************@TK2MSFTNGP06.phx.gbl...
>Hi,

START was a good idea. Thanks for the follow-up.

I know you said the window flashing in the task bar is acceptable, but if
you really don't like it you could always put together a small .NET
program to do the trick without any interface. Just make a WinForms
project and don't show any forms.

HTH

--
Dave Sexton


That's an excellent idea.
In VB6 it's done with WinExec I think (to start another application), but
I didn't make anything like it in .net just yet, but I 'm confident I'll
find
that line of code easily on the net, won't be much trouble.
Thanks for the idea !
--
Filip
http://www.ww2airborne.net/
Official Site of the 101st Airborne - 463rd PFA
skype: airborne463pfa-fiwi
-------------------------------------------------
FOUND : -)
System.Diagnostics.Process.Start("C:\WINDOWS\syste m32\CALC.EXE")
Oct 6 '06 #6

This discussion thread is closed

Replies have been disabled for this discussion.