Problems with MIME settings at the hosting provider
Hi,
My web hosting company is www.brinkster.com and I have asked them to enable MIME type for ".application". After a short period of time, the extension was not recognized anymore (404 Page not found) so I have asked them to reenable the settings. This is what I have received from their suport:
-
Hello,
I am not sure what has happened now but I have just reset the MIME settings for the ".application" extension. It is possible that this extension name is too long for our server to recognize it. If problems occur in the future, would it be possible to shorten the extension name?(for example to ".app")
--
After a couple of days, again the extension was not working. So I am gonna ask even if I think it's not possible: Is it possible to use a different extension for ".application" ?
I must mention that I have asked them to enable ".xapp" (Avalon Express Applications) and I didn't have any problems with it since it was enabled (a month ago).
Valentin
If you're activating over http, it is possible to use a different extension other than .application for deployment manifest. As long as web server returns Content-Type "application/x-ms-application" for the deployment manifest ClickOnce will work.
For UNC or local machine activation where you're double clicking the deployment manifest it must have .application extension for ClickOnce to work.
-Sameer
The problem is now I have to change the extension of the deployment manifest from .application to .app. Not only that, in the deployment manifest itself I have to change the extension in the element <deploymentProvider codebase="http://<server_name>/<application_name>/<application_name>.application" /> but this invalidate the manifest because it is signed.
So there must be a way to manually build the project for publish so I can specify a different name for the deployment manifest.
I have read about "MSBuild /target:publish" and GenerateDeploymentManifest task but I don't know how to start, maybe somebody can help me by giving an example.
Thank you,
Valentin Iliescu
I have solved the problem by modifying the Microsoft.Common.Targets - these 2 lines
<TargetDeployManifestFileName Condition="'$(TargetDeployManifestFileName)' == ''">$(AssemblyName).application</TargetDeployManifestFileName>
<DeployManifestIdentity>$(ManifestIdentity).application</DeployManifestIdentity>
Valentin,
Where are these lines of code located in your project and how do you modify them?
I am having a similar problem with Brinkster and I can't figure out where these lines would be some I can edit them.
I'd appreciate any help you can provide.
Thanks,
Marc
