Contents tagged with VSTO
I’ve taken over the completion, deployment, and maintenance of an ASP.NET Web site that generates Office documents using VSTO. VSTO’s a decent concept and works fine for small-scale scenarios like a desktop app or small intranet. However, with multiple simultaneous requests via ASP.NET, we found the Web server performance suffered badly.
The Ribbon interface in Office 2007 is okay, but when I'm under the gun to get something done, I don't want to spend time figuring out the new way.
Update Nov. 14: Double Arrgghh! I discovered I had the Office PDF converter add-on on the machine. No idea why, since I hadn't installed the Office 2007 beta. The component's name didn't start with "Microsoft" like other entries, so watch out. Also, turn on Show Updates to catch everything. Thanks to everyone for suggestions!
Wow! Don't you just love it when new developer tools hit all at once like an avalanche?
I was excited about the possibilities of generating custom Word 2003 documents on the fly using the ServerDocument object in Visual Studio Tools for Office 2005. My goal was to show how you could fill out a form on an ASP.NET 2.0 Web page, click a button, and download a custom document or have it emailed.
After investigating the error "System.Security.SecurityException: That assembly does not allow partially trusted callers", I discovered a severe limitation in the technology: it's almost impossible to use on public Internet sites because of the security model.
My ISP, ServerIntellect, runs ASP.NET pages with less than Full Trust, which makes sense. They kindly installed the VSTO 2005 runtime components. However, VSTO 2005 requires Full Trust permissions even when in the GAC.
According to MS Support, the "solution" is to create a Full Trust wrapper around VSTO's stuff, and tag the wrapper with AllowPartiallyTrustedCallersAttribute to allow it to run under partial trust. Trouble is, my wrapper would have to go into the GAC and an ISP would be understandably reticent about allowing that on a shared server.
The upshot is that unless you have direct control of the Web server, you'll have a rough time getting this to work. I'd love to be told I'm wrong about all this because it's really disappointing to limit this fine capability to corporate sites and intranets.