|
Having some trouble getting ClickOnce publishing to work on Beta 2? Yeah, me too. On several of my VPCs and on a recent client's laptop machine, the Beta 2 install appeared to share the same problem. When publishing a smart client application through the Visual Studio IDE, the following error appeared:
Publishing files...
Error: Failed to copy file
'C:\SmartClientDemos\ClientApp\ClientApp\publish\setup.exe' to 'http://localhost/ClientApp/setup.exe'. Unable to add 'setup.exe' to the Web. Unable to add file 'setup.exe'. The system cannot find the file specified.
Publish failed.
Well, a little birdie named Ahti told me to create a mime mapping in IIS for the .application extension, that maps to application/x-ms-application. The link where the problem is described is here:
http://msdn2.microsoft.com/library/ms165433(en-us,vs.80).aspx
It worked like a charm for me.
Now, the real question: why isn't this set up when ASP.NET is installed on the machine, through the IIS configuration step? Furthermore, why do we need this mapping to publish the application? I would think that the error related to mime mapping should not occur until someone actually tries to click on the published application link, which downloads the setup.exe file, which in turn will try to access the .application manifest. I would expect to be able to publish without this error, regardless of any mime mapping.
|