《Visual Studio Tools for Office: Using C# with Excel, Word, Outlook, and InfoPath 》——By Eric Carter, Eric Lippert
Foreword
2005 May 23, Monday
I face challenges, wrote a foreword of the book has some panic. Let's see: the name on the cover of this book provoked some awe. Know a person, then we will introduce a person considered to be a specific topic of pioneering work, and I believe I believe this will achieve these lofty goals. When accepting the invitation to forgive the forefront of this book, my first response is to want to know what I can add, they may not find some of Microsoft's masterpiece to introduce this book? However, it seems that outside sounds to add some confidence in the proceedings, so dear readers, I said softly, then in the great presence.
First, a little about me (this is what I want to enter this video last chance): I've been lurking, various ideas program office, more than a decade. I write a lot about the plight of miracles and office development, and survived the Office of the glory days of 2000, when the Office may seem finally to become a successful integrated development platform. In around 2001, it is clear that, whatever I want and like-minded people to develop a standard Office became a respected, it will not become the VBA programming language.
With the release of Visual Studio Tools for Office 2003, and finally it looks like we've made some progress, not to give up to the 1990s, Office and .NET developers can embrace all the advantages of using managed code, code access security , xcopy deployment , as well as all the rest of the .NET provides. I like this product, but it does not really reach critical mass and the developer community. Most likely, you can only use COM-based document control, as well as the fact that the products do not provide design-time experience makes it a slow starter.
During that time, I remember very clearly sitting in some of the activities of Microsoft, and met with Eric Carter.I really do not know who he is (of course he did not understand me), but he seems pretty good, we talked for hours about the development of the office, as well as on the specific circumstances of VSTO. Only later we learned that he was at a high level in the development of the product. (I spent a few hours chatting worry I'm really stupid, I hope not). We started a long communication, which I often do not understand that I have a lot of things you can learn how .NET and Office to interact. I spent several hours learning from Eric's blog, while Eric Lippert's blog is the same. If you are spending time doing Office development, make sure that you do the following:
http://blogs.msdn.com/ericlippert/
http://blogs.msdn.com/eric_carter/
I spent some measurable time read a copy of the book, and trying to find this in chapter