Windows Develop Bookmark and Share   
 index > ClickOnce and Setup & Deployment Projects > Forced to enter an Installation URL when same as FTP publishing location
 

Forced to enter an Installation URL when same as FTP publishing location

VS 2005 forces me to enter an Installation URL when the ClickOnce Publishing Location is an ftp server, but the intallation URL should be optional. How do I publish to an FTP site without specifying an Installation URL?I want users to go directly to the ftp server to access the installation (access thesetup.exe).

Thank you,

Barry

Barry6319078  Tuesday, April 03, 2007 10:38 PM
I have worked out the answer to my question about being forced by Visual Studio to include an "optional" Installation URL when publishing to an FTP server:
The reason is that FTP deployment (end user installation) is not supported, only FTP publishing (copying ClickOnce files to the deployment server). So, a URL would be required for deployment.
Barry6319078  Thursday, April 12, 2007 8:45 PM
I have worked out the answer to my question about being forced by Visual Studio to include an "optional" Installation URL when publishing to an FTP server:
The reason is that FTP deployment (end user installation) is not supported, only FTP publishing (copying ClickOnce files to the deployment server). So, a URL would be required for deployment.
Barry6319078  Thursday, April 12, 2007 8:45 PM

You can use google to search for other answers

Custom Search

More Threads

• *.vdproj help
• Installing a url automaticlly as atrusted site
• unable to import merge module 'vc_user_crt71_rtl_x86_---'
• Embedded control keeps crashing...
• problem updating ClickOnce application - Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
• Deploying custom client configuration files with click once deployment.
• Clickonce - What is the difference between data file and data file (auto)
• msi to copy file
• VB Express ClickOnce crashing after install
• Application install fails from server with application deployed with ClickOnce (manifest may not be valid or the file could not be opened.)