Use a path that resolves anywhere your VSTO solution could be deployed (Christin Boyd)

Published 04 June 09 01:29 PM

One of the VSTO MVPs pointed out that in some cases his customers were unable to resolve UNC paths consistently.  When he investigated further, he found that some branch offices of an enterprise were unable to resolve the UNC path (\\myserver\myvstoapps\installpath\) because of the way they setup their network infrastructure.  The only workaround he could find was to use a fully qualified web URL instead of a UNC path.  The resolution was to create a web server internal to the corporation which is still accessible by people in the branch office.  The other option would be to negotiate with the IT staff to change the way the branch office resolves server names, but apparently that was not an option.

We looked at the situation and agree with his conclusion about the workaround.  If the network just won’t give you the correct path using UNC, then HTTP is a reliable solution.

-Christin Boyd, Program Manager

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

# Use a path that resolves anywhere your VSTO solution could be deployed (Christin Boyd) | OfficeDeveloper.NET said on June 17, 2009 1:33 AM:

PingBack from http://officedeveloper.net/use-a-path-that-resolves-anywhere-your-vsto-solution-could-be-deployed-christin-boyd/

Leave a Comment

(required) 
(optional)
(required) 

  
Enter Code Here: Required

About VSTO Team

This login represents the Visual Studio Tools for Office team. Many members of the team us this account for publishing technical blog posts.

This Blog

Syndication

Page view tracker