Office Development with Visual Studio : MSDN

MSDN Code Gallery launches Localized Hotfix Pages

VSTO Team — Tue, 08 Jul 2008 22:03:07 GMT

All of the Visual Studio and .NET Framework hotfixes that are publicly available on MSDN Code Gallery are now localized in the following languages: French, Spanish, Italian, German, Traditional and Simplified Chinese, Japanese, Korean, Russian, and Brazilian Portuguese. You can browse the list of Hotfixes on MSDN CodeGallery here: http://code.msdn.microsoft.com/Project/ProjectDirectory.aspx?TagName=Hotfix. MSDN Code Gallery allows the community to provide feedback on our hotfixes and they can stay informed when a new hotfix is released by subscribing to the following RSS feed: http://code.msdn.microsoft.com/rss.ashx?behavior=bytag&TagName=Hotfix. You can customize your RSS feed by adding additional tags, such as “Visual Studio 2008.” The Hotfixes will not necessarily be tagged with “VSTO” if they pertain to Office development because that is not part of the Hotfix taxonomy of tags. The Hotfixes are usually just tagged with the version of Visual Studio or the version of the .NET Framework, and often not tagged with the sub-part of the feature within VS.

Below, we’ve highlighted how the translation options appear in each hotfix resource page. When a community member selects a language, it will take them to a resource page where they can read the localized KB article content and details for the hotfix they’ve selected. The full description of the Hotfix is documented in a Knowledge Base (KB) article on the Help and Support site. The KB article and the Hotfix download pages are cross referenced and circled in red.

Below you can see the same page in Simplified Chinese, with the link to the KB article circled in red:

-Christin Boyd, Program Manager, Visual Studio

Do you have an opinion about Visual Studio and .NET Framework developer Help content? (Kemp Brown)

VSTO Team — Thu, 22 May 2008 02:23:00 GMT

Our Help content architect, Kathleen McGrath, has created a short, anonymous survey (15 questions/10 mins.) to gather input on how and when the Visual Studio and .NET Framework developer Help content is used, how satisfied you are with it, and about areas that need improvement:

Link to the Visual Studio and .NET Framework Developer Documentation Survey

(Kathleen will also be taking this survey with her to TechEd in June.)

The focus of this survey is content improvement. We want to learn more about the types of applications you're creating, the tools/technologies you're using, and how we can improve our content and code examples to help you achieve your goals.

Thanks in advance for participating!

- Kemp Brown, programming writer

Aggregating blogs in a blog (Mary Lee)

VSTO Team — Fri, 22 Feb 2008 18:59:00 GMT

There are many resources to learn about Visual Studio Tools for Office, and they are scattered through blogdom and even the MSDN Library. In my one year on this team, I've collected various helpful links that I share here.

The Visual Studio Tools for the Office System (3.0) whitepapers written by subjet matter expert like MVPs in the Microsoft Office Development section of the MSDN Library. These complement the Visual Studio Tools for Office documentation.

Several VSTO team members share their expertise on their own blogs. Misha discusses how to use an unofficial feature of Microsoft Office to deploy to alll users in Deploying your VSTO Add-In to All Users (Part I) and Deploying your VSTO Add-In to All Users (Part II). Andrew explains Why is VS development is not supported with multiple versions of Office? TQ details Why there is a separate VSTO runtime apart from the .NET Framework and Microsoft Office. Kris compares the VS2005 and VS2008 VSTO security models in The passphrase is "Install already": A new look at VSTO Security.

- Mary Lee, programming writer.