Home/ Questions/Q 6813465
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T20:34:24+00:00

We have recently moved to a new web server (from IIS6 to IIS7.5) and

  • 0

We have recently moved to a new web server (from IIS6 to IIS7.5) and I’m having some trouble updating our VSTO word addin.

Our app checks for updates manually when logging in and if a newer version has been found updates like this (let me know if there is a better way to do this – I’ve tried ApplicationDeployment.Update() but had no luck with it either!): 

WebBrowser browser = new WebBrowser();
browser.Visible = false;
Uri setupLocation = new Uri("https://updatelocation.com/setup.exe");
browser.Url = setupLocation;

This used to launch the setup and update the app and when the user restarted word they would have the new version installed. Since the server move the update no longer happens. No exceptions are thrown. Browsing to the URL launches the updater as expected. What would I need to change to get this to work?

Note I have the following MIME types setup on the folder in IIS:

.application
application/x-ms-application

.manifest
application/x-ms-manifest

.deploy
application/octet-stream

.msu
application/octet-stream

.msp
application/octet-stream

.exe
application/octet-stream

Edit

OK I’ve had a look in fiddler and its returning a body size of -1:

enter image description here

If I enter the same URL in IE you can see that the setup.exe is launched without problems.

This is what fiddler displays in the raw view when accessing from word: 

HTTP/1.1 200 OK
Content-Type: application/octet-stream
Last-Modified: Tue, 27 Sep 2011 15:07:42 GMT
Accept-Ranges: bytes
ETag: "9bd0c334277dcc1:0"
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Date: Mon, 14 Nov 2011 07:42:18 GMT
Content-Length: 735608

MZ��������������������@������������������������������������������   �!�L�!This program cannot be run in DOS mode. $�������

*** FIDDLER: RawDisplay truncated at 128 characters. Right-click to disable truncation. ***
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Have you tried a tool like (for instance) fiddler2 to see what http traffic is actually created?
    Does the client make a server call? What does the server actually return?

    Then:

    • Make the calls from within word (which isn’t working)
    • Make the calls by hand (which is working)

    Compare both the request and response packages from those calls to spot the differences

    • 0