Dave Burke : Freelance .NET Web Developer specializing in Online Communities

ClickOnce. Tricked Twice. ASPNET configuration pre-reqs

Yessir, that new ClickOnce deployment is quite sweet, like a Vermont Strawberry in July.

You may receive File Not Found 404 errors on .manifest, .application, .deploy and other ClickOnce-specific filetypes after clicking that magical [INSTALL] button on the web page ClickOnce creates.  The documentation says IIS supports these filetypes automatically with the installation of ASP.NET 2.0, but that hasn't been the case for me.  You'll need to go into IIS and add the mime-types before experiencing ClickOnce Love.

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

IISRESET.

[insert longneck bottle of Budweiser or your personal metaphor for a big red heart with arrow through it here...]

 

Comments (2) | Post RSS RSS comment feed

Posted on 7/18/2005 11:25:00 AM by Dave Burke
Categories: .NET
Tags:

Related posts

Comments (2) -

7/19/2005 2:21:16 AM Permalink

Does ClickOnce require ASP.NET 2.0 on the server, Dave? My little test IIS box simply returns the .application file to my web browser as an XML file, even with the .application MIME type added.

I'm sure it's something forehead-slappingly simple such as not having ASP.NET 2.0 on the server itself.

mabster |

7/19/2005 2:26:47 AM Permalink

Oh, wait - could be because I have C# Express Beta 2 installed on the machine I'm trying to install to. My workstation recognizes ".application" as a known file type.

I'm trying it now on an old Win2K box, and it seems to be working. Neat!

mabster |


Powered by BlogEngine.NET 2.0.0.36
Theme by Dave Burke