January 20, 2005
Are you using Visual Studio Tools for Office?Posted 3377 days ago on January 20, 2005
Today I got the chance to talk to KD Hallman, Microsoft's General Manager for Visual Studio Tools for Office. Interesting stuff, especially what's coming in Visual Studio 2005. Perhaps the most remarkable feature (though not necessarily the most important) is the ability to treat a Word or Excel document like a Windows Form, and put .NET controls like buttons and listboxes directly onto it. Event-handling code goes into a code-behind assembly, somewhat like the ASP.NET model.
This is very cool, but I have some concerns. Office is unmanaged code and makes heavy use of COM, so the .NET integration uses COM interop. Office is huge and complex, so my main worry is that the resulting solution would be resource-hungry and fragile. I've instinctively shied away from the current VSTO for this reason; adding embedded Winform controls sounds even more risky. However KD assures me that this isn't so :-).
I'd be interested in hearing from anyone who's created a full VSTO solution. Is it robust? Does it perform OK? Was deployment tolerably straightforward? Please comment here or send me an email: tim(at)itwriting.com.
No comments, be the first!
Comments are closed
Recent postsUsers plead with Borland to give up .NET
IE7 to be released 18th October,...
If Microsoft doesn't use UAC, why...
Google's unsettling lack of direction
Vista security: now prove it