vb.net windows deployment

[RustyLI via .NET 247]

when creating a setup project how can you control what is the default folder name and path that the deployment should place the executable.
Then how do you make it create a link to that exe from either the windows start menu or windows desktop.

I have created deployment .msi files but I have no control over the placement folder it uses the name of the setup project.
When I use the application folders in deployment it creates two exe's on the user's pc.

Basically need some way of controlling all of this.
The on line help still leaves me clueless

 

[Crouchie1998]

Go to the Special folders; program files, create a new file with whatever
name you want, add your assembly...

 

[Herfried K. Wagner [MVP]]

when creating a setup project how can you control what is the default
folder name and path that the deployment should place the executable.
Then how do you make it create a link to that exe from either the windows
start menu or windows desktop.

I have created deployment .msi files but I have no control over the
placement folder it uses the name of the setup project.
When I use the application folders in deployment it creates two exe's on
the user's pc.

Inside the setup project, have a look at the buttons above the "solution"
explorer. There is one view that will show you the file system of the
destination computer. You can place the files to be copied there.

 

[rustyLI via DotNetMonster.com]

Hi guys,
thanks for the response.
My problem is not that the correct exe is not getting "deployed"
There are two problems:
1) I can not put it in the correct folder
i.e programfiles/myfolder

2) the user start menu loads another exe so I have two - not one with a
shortcut

thanks

 

[Crouchie1998]

To create a link to the Desktop:

Go to your output directory, right-click, new shortcut.... Now, cut this
shortcut, choose Desktop on the left (special folders), paste it & if no
line appears then you are ok. The icon will then be the default program icon

In the online MSDN help is a simple example of setup programs... These show
you what you need to know

 

[rustyLI via DotNetMonster.com]

I wish I understood where in msdn online my questions were answered - right
now

Using your suggestion the following happens:
When installing:
The first message reads installer will install setupMyProject
to the following folder:
c:\program files\somename\setupMyProject
1) setupMyProject = the name of the setup project in my Applications
solution.
2)somename = a default name that I have no idea where it came from

It actually creates this default folder and places
msvcp71.dll and msvcr71.dll in the folder some c++ runtime dll's which I
don't need and are no where in my vs.net project

Yes it does create an icon on my desk top but it also puts the
app.exe.config file on the desktop. The location path is C:\Documents and
Settings\myname\Desktop

What I wanted is a shortcut on the desktop to an exe and config file in
the folder: Program files\myApp

I would really appreciate it If someone could point to a link that
describes how to really do this or tell me how.

thanks

 

[rustyLI via DotNetMonster.com]

Well I was sort of able to figure this all out.
The real big problem was making sure "the always create" property was set
to true for all the folders I was using under "file system on target
machine".

I was able to create a new folder under "program files" with the primary
output of the application project; and also the icon I wanted to show on
the desk top.

I was able to create a short cut to the primary output and drag that into
the User's Desktop. I had to use properties to change the name on the
shortcut and point to the icon I wanted it to display.

Setup worked OK except that I still get a misleading message of where I
want to place the setup - usually you are asked where do you want to put
the actual application exe; and it is loading the c++ files in the strange
default folder.

If someone could tell me how to get rid of the "unneeded ?" C++ files, and
the strange default - I will be A-OK.