I've managed to publish the project at home on the local network successfully.However, when trying to publish it to a hosting acc such as godaddy.com where it asks for a usrn and pw to connect to, it fails to connect. Ther error also was "can't communicate with front page extensions". Which I have already installed on the hosting acc. sucessfully. It still wont connect to the hosting acc. I'm thinking that's because it requires a usrn and pw.Is it possible to publish the project somewhere on the internet so that someone else can download it to theire pc, then run the setup.exe fileto install it and run it as an exe on their computer?

Hi learningvb8,

It sounds like you're having trouble publishing your app. First of all, is the web server running some kind of Unix or is it windows Server? The Front Page extensions are only required when using Windows Server, and you are deploying to the web server using http.
If you can't connect to godaddy, then that is a problem you need to talk to godaddy about. Do they allow you to access your web server area with http? Many sites allow you R/W access with FTP, and they set up an alias URL to point at that area.

You might try this and see if it works. Here's an example:
publishing file location: ftp://myhost.com/MyFolder/MyAppName/
installation url http://myurl.com/MyAppName

I would talk to GoDaddy about it. With FTP, it should come up and ask for a username and password. If you are publishing using http, and the publishing file location is the same as the installation URL, that's not going to work, because your customers/users must have unimpeded access to the deployment. You can not have a username/password between the user's machine and the server; ClickOnce will not do credentials.

Once you've successfully published your application, for the user to install from godaddy, you will need to make sure they have the correct MIME types set up. Here they are:

.application --> application/x-ms-application
.manifest --> application/x-ms-application
.deploy --> application/octet stream

If you are deploying .Net 3.5 as a prerequisite, and/or your application targets .Net 3.5, you need these as well:

.msp --> application/microsoftpatch
.msu --> application/microsoftupdate

If you have vsto apps, you need this one:

.vsto --> application/x-ms-vsto

Hope this helps.

RobinDotNet

---

Click here to visit my ClickOnce blog!

Please check this thread for reference: How to Deploy, Install and Automatic Update your application via the ClickOnce deployment.

http://social.msdn.microsoft.com/Forums/en-US/vbgeneral/thread/446cbc20-e339-4cf3-9048-de54fe16f79b

Move it to ClickOnce Deployment forum for better support.

Hi learningvb8,

It sounds like you're having trouble publishing your app. First of all, is the web server running some kind of Unix or is it windows Server? The Front Page extensions are only required when using Windows Server, and you are deploying to the web server using http.
If you can't connect to godaddy, then that is a problem you need to talk to godaddy about. Do they allow you to access your web server area with http? Many sites allow you R/W access with FTP, and they set up an alias URL to point at that area.

You might try this and see if it works. Here's an example:
publishing file location: ftp://myhost.com/MyFolder/MyAppName/
installation url http://myurl.com/MyAppName

I would talk to GoDaddy about it. With FTP, it should come up and ask for a username and password. If you are publishing using http, and the publishing file location is the same as the installation URL, that's not going to work, because your customers/users must have unimpeded access to the deployment. You can not have a username/password between the user's machine and the server; ClickOnce will not do credentials.

Once you've successfully published your application, for the user to install from godaddy, you will need to make sure they have the correct MIME types set up. Here they are:

.application --> application/x-ms-application
.manifest --> application/x-ms-application
.deploy --> application/octet stream

If you are deploying .Net 3.5 as a prerequisite, and/or your application targets .Net 3.5, you need these as well:

.msp --> application/microsoftpatch
.msu --> application/microsoftupdate

If you have vsto apps, you need this one:

.vsto --> application/x-ms-vsto

Hope this helps.

RobinDotNet

---

Click here to visit my ClickOnce blog!