index > ClickOnce and Setup & Deployment Projects > Walk-through / FAQ for non-IIS servers

Walk-through / FAQ for non-IIS servers

Ok, I understand that there are some MS developers who have worked very hard on the click-once feature and by the looks of the video on Channel 9 are quite proud of it. I for one think its a great alternative to MSI and am very excited to use it. But I think it is quickly becoming clear that there is not enough information presented on this feature for it to be very useful in this beta release.

In another thread within this forum an MS developer admitted that having spaces in your assembly name can cause the manifest to not be properly signed. Because a desktop shortcut is supposed to have spaces in it, there are alot of assemblies that use spaces. This is a big hole that I wish was plugged already.

As for the application mime type, for those of us not running IIS (and lets face it, that's most of us) hopefully you have access to cpanel or the server directly because you are going to have to add the application type to it. This really needs to explained alot clearer. (Hint: In the wizard)

The following blurb from: http://msdn2.microsoft.com/library/ms165433(en-us,vs.80).aspx doesn't even begin to offer useful information.

"ClickOnce supports installing applications from any HTTP 1.1 Web server or file server. FTP protocol is not supported. You can use the ftp:// protocol to publish applications, but you must perform installations using the http://, https://, or file:// protocol."

Note to MS: If you want people to be able to use and take Click-Once seriously then stop writing everything as it pertains to IIS. If you have IIS then are probably not going to have the slew of problems that a FAQ or walk-through is going to cover.

I think I speak for alot of users on this forum when I sincerely ask for a Click-Once walkthrough for non-IIS servers.

I would like to hear any response from an MS employee on these issues.

Jared - http://www.wikireference.com - A Programming Reference

JBrown9264

Hi,

I have to emphaze also that in the article it start with "when you publish over HTTP". So I did not read it because I was publishing over FTP (and installing over HTTP) (I know the words publish / install may have overlapped meaning).

Secondly there is spoken about MIME witch is in fact a protocol used for email attachments, so I was very confused about that. It is probably fine for IIS users as they know the terms used in it.. But if there was just stated that an application type has to be add in the HTTP headers, in the "Content-Type" header, then it would be very simple to understeand what was going on for all programmers. Of course the usage for IIS could be explained too, it is handy for people using it.

Wilfried Mestdagh

reply 2