Just got the latest vs 2005 and testing clickonce deploy. Everything works fine when pulishing to my localhost. When I publish to a remote web site and click Install on the publish.htm page the browser opens the .application file.
If I navigate to the virtual dir with Windows Explorer and run the publish.htm - it works. Any suggestions.
Thanks
Browser opening the .application file
Hot Topic
- Microsoft Agent in WinForm
- "multiple rows" If select all checked true ~ insert old data with updated dates appended to database for logging Mgr decision
- Get current Window handle count for current process
- How do I simultaneously display a container and its child controls?
- How to insert, update, delete using DataGrid ?
- Getting focus to a dialog box
- calling function in form
- Help me designer has Bugs bugs bugs
- Datgridview / C# problem
- Datagrid
Windows Forms
- How to get DataGridViewComboBoxColumn's selected value for validation?
- Can't update new row in child table of relationship
- PrintPreview of Chlid from MdiParent
- Flickering Problem with Windows Form containing DataGridView
- Visual Basic users needed for Usability Study
- Windows Media Player ActiveX control
- Splash Screen
- Adding Scroll bar in MDI Parent Windows
- how to make gridview to change datasource
- BUG: ContextMenu Shortcut (Accelerator) Problem
Browser opening the .application file
DarrenSQLIS
.manifest -> application/x-ms-manifest
ClickOnce mime filter on client is invoked when IE gets response with ContentType = application/x-ms-application. And since .application file is the top level activatable entity it's the only one that should really have this mime association.
If you associate .manifest with application/x-ms-application and happen to click on it the ClickOnce engine will get invoked on client and will throw an error since it expects to see a deployment manifest.
Server config information for ClickOnce is available at http://msdn2.microsoft.com/en-us/library/ms228998.aspx.
Regards,
Sameer
bezael
I promise - I really did look through the forum before posting, but must have overlooked this. Here is the solution from earlier post:
You need to add some custom mime types for clickonce to work...
.application application/x-ms-application
.deploy application/octet-stream
.manifest application/x-ms-application