Eric Carter is the development manager for the Visual Studio Tools for Office (VSTO) team at Microsoft. He helped invent, design, and implement many of the features that are in VSTO today. Previously at Microsoft he worked on Visual Studio for Applications, the Visual Studio Macros IDE, and Visual Basic for Applications for Office 2000 and Office 2003. For more information about VSTO, visit Eric?s blog at http://blogs.msdn.com/eric_carter/default.aspx.
Consider the following portion of an all-too-common server scenario. An
authenticated user, perhaps a salesperson, requests a Word document from a
server. The document is an expense report, and the server is an ASP, ASP.NET,
or SharePoint Server. The server code looks up some information about the
user from a database, Active Directory, or Web service. For example, perhaps
the server has a list of recent corporate credit card activity that it will
prepopulate into the expense list. The server starts up Word but keeps it
"invisible" because there is no interactive user on the server. It then uses
the Word object model to insert the data into a table, saves the result, and
serves up the resulting file to the user.
This is a very suboptimal document life cycle for two reasons. First, it is
completely unsupported and strongly recommended against by Microsoft. Word
and ... (more)
Eric Carter is the development manager for the Visual Studio Tools for Office (VSTO) team at Microsoft. He helped invent, design, and implement many of the features that are in VSTO today. Previously at Microsoft he worked on Visual Studio for Applications, the Visual Studio Macros IDE, and Visual Basic for Applications for Office 2000 and Office 2003. For more information about VSTO, visit Eric?s blog at http://blogs.msdn.com/eric_carter/default.aspx.
Scott Sellers
Anthony Franco
Daniel Morris
Wayne Walls
Niki Acosta
Jereme Hancock
Oren Michels
Marvin Wheeler
Douglas Kim
Ken Guiberson
