Windows Develop Bookmark and Share   
 index > ClickOnce and Setup & Deployment Projects > VS2005 deployment solution lacks an "install-to-custom-path" feature? Can it be?
 

VS2005 deployment solution lacks an "install-to-custom-path" feature? Can it be?

Hello,

I am trying to use the Visual Studio 2005 deployment solution from my Window app's property pages and I've done it so far but the generated installer (setup.exe) does not ask WHERE the application will be installed. Instead, it just installs it into a rather strange location (C:\Documents and Settings\... ... ...). I need a little more flexibility from my installer. Can you help me?

Thanks
mARiO6  Monday, January 28, 2008 1:44 AM
In a setup&deployment project most of the files you install should be in the Application Folder in the file system view. That defaults to a program files folder location and is the one that the dialog lets you change.

PhilWilson  Tuesday, January 29, 2008 7:29 PM

Hi, Mario,

Based on my understanding, you want to know why the "setup.exe" does not let you choose the installation location,don't you?

If the setup.exe is generated from the property window of your project, you are actually using ClickOnce deploymentinstead of a Setup Project.

In a ClickOnce deployment, currently, changing the installation path is not supported. Because it is by the design of ClickOnce. It is a per-user installation.

If you want to make a installation package which supports path option, you should choose Setup Project and do like PhilWilson said.

Please check this article for more details between ClickOnce and Setup Project.

http://msdn2.microsoft.com/en-us/library/142dbbz4(VS.80).aspx

Hope this Helps,

Regards

Yu Guo â€?MSFT  Thursday, January 31, 2008 6:03 AM
In a setup&deployment project most of the files you install should be in the Application Folder in the file system view. That defaults to a program files folder location and is the one that the dialog lets you change.

PhilWilson  Tuesday, January 29, 2008 7:29 PM

Hi, Mario,

Based on my understanding, you want to know why the "setup.exe" does not let you choose the installation location,don't you?

If the setup.exe is generated from the property window of your project, you are actually using ClickOnce deploymentinstead of a Setup Project.

In a ClickOnce deployment, currently, changing the installation path is not supported. Because it is by the design of ClickOnce. It is a per-user installation.

If you want to make a installation package which supports path option, you should choose Setup Project and do like PhilWilson said.

Please check this article for more details between ClickOnce and Setup Project.

http://msdn2.microsoft.com/en-us/library/142dbbz4(VS.80).aspx

Hope this Helps,

Regards

Yu Guo â€?MSFT  Thursday, January 31, 2008 6:03 AM

You can use google to search for other answers

Custom Search

More Threads

• C# ClickOnce web deployment issue: seeing code instead of the proper functionality with the "launch" hyperlink on publish.htm
• UIPermission on System.Form.Control hosted in IE
• ClickOnce Publishing Error
• Including redist. components in setup project?
• Custom Action runs from version being replaced
• Question re VS 2005 setup projects
• Assembly being added to Setup project unexpectantly
• How to debug ClickOnce application ?
• Update Button
• Does VisualStudio always use MSBuild