I just had an interesting message from a customer who's running my FoxPro Web Connection tool and was trying to get the Visual Studio Add-in to work. When he starts VS.NET 2005 – the Add-in fails to load and pops up a load error.

After a few questions it became clear that the problem is that his My Documents folder from which Add-ins are loaded are stored on a remote machine and mapped to an H:\ drive. The problem is that by doing this the assembly is no longer fully trusted and fails to load because it's missing some neceessary permission. The actual permission that is failing is AspNetHostingPermission, which is odd, because my code certainly isn't referencing anything in System.Web directly. In fact, System.Web isn't referenced by my add-in assembly at all. However it does reference the various VS.NET Add-in namespaces which in turn might pull in the required assemblies in order to host ASP.NET inside of VS.NET.

Long story short is – this seems like a pretty common scenario where somebody has a roaming profile and I don't have a good answer on how to fix it other than giving full trust to the assembly or the remote UNC, which seems a little sketchy as a recommendation.

Anybody have any better ideas?