Commit bdfd714b authored by Charles Plessy's avatar Charles Plessy

Add media types and extensions to support ClickOnce apps.

Using Third-Party Web Servers

If you are deploying a ClickOnce application from a Web server other than IIS,
you may experience a problem if the server is returning the incorrect content
type for key ClickOnce files, such as the deployment manifest and application
manifest. To resolve this problem, see your Web server's Help documentation
about how to add new content types to the server, and make sure that all the
file name extension mappings listed in the following table are in place.

File name extension	Content type
.application		application/x-ms-application
.manifest		application/x-ms-manifest
.deploy			application/octet-stream
.msu			application/octet-stream
.msp			application/octet-stream
parent 42acae4f
......@@ -88,7 +88,7 @@ application/news-message-id
application/octet-stream bin
application/octet-stream bin deploy msu msp
application/oda oda
application/oebps-package+xml opf
application/ogg ogx
......@@ -469,6 +469,8 @@ application/x-lzx lzx
application/x-maker frm maker frame fm fb book fbdoc
application/x-mif mif
application/x-mpegURL m3u8
application/x-ms-application application
application/x-ms-manifest manifest
application/x-ms-wmd wmd
application/x-ms-wmz wmz
application/x-msdos-program com exe bat dll
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment