http://msmvps.com/blogs/nickwienholt/archive/2006/10/13/VSTO_2F00_-CAS-Deployment-Hell-_2D00_-How-Good-Intentions-Go-Bad.aspxThe Scenario I'm supporting a VSTO application that does a pretty typical Office style thing. CAS policy updates to let the particular .NET assembly run are added to the end-users machine at install time, and the application works fine when the documentenCommunityServer 2008.5 SP2 (Build: 40407.4157)http://msmvps.com/blogs/nickwienholt/archive/2006/10/13/VSTO_2F00_-CAS-Deployment-Hell-_2D00_-How-Good-Intentions-Go-Bad.aspx#244828Sat, 04 Nov 2006 05:45:03 GMTd67277c4-116b-43f1-b688-e9ef184ea916:244828.NET Performance<p>A couple of weeks ago I wrote about the frustrution of VSTO deployment , and the real hole that VSTO</p> <img src="http://msmvps.com/aggbug.aspx?PostID=244828" width="1" height="1">