Office Development with Visual Studio : Visual Studio 2010

Migrating an Outlook Solution to .NET Framework 4 in Visual Studio 2010 (Norm Estabrook)

VSTO Team — Wed, 16 Dec 2009 22:33:37 GMT

Visual Studio can help migrate your Outlook solutions from .NET Framework 3.5 to the .NET Framework 4. However, you still have to do a few things manually to make it all work.

Beth Massi converts an Outlook Solution that targets the .NET Framework 3.5 to an Outlook Solution that targets the .NET Framework 4 client profile in this very cool and informative blog entry - Migrating an Outlook Client to .NET Framework 4 in Visual Studio 2010.

Office 2010 Beta & SharePoint 2010 Beta Now Available to the Public (Beth Massi)

VSTO Team — Wed, 18 Nov 2009 18:54:34 GMT

Monday Office and SharePoint 2010 Beta were released to MSDN/TechNet subscribers. Today it was announced at PDC that these are available to the rest of the public! Come and get it…

Office 2010 Beta

SharePoint 2010 Beta

These Betas are compatible with Visual Studio 2010 Beta 2 which was released to the public a few weeks ago. We’ve also started a series on Channel 9 on SharePoint development in Visual Studio so check that out starting with:

Overview of SharePoint Development in Visual Studio 2010

Also check out…

Office 2010 resources

SharePoint 2010 Resources

And stay tuned here for more posts on Office Development with Visual Studio 2010!

Enjoy,
-Beth Massi, Visual Studio Community

Visual Studio 2010: Specify advanced publishing options (Saurabh Bhatia)

VSTO Team — Mon, 19 Oct 2009 22:31:12 GMT

I have previously posted how you can specify various properties for a VSTO solution like the Publisher and Product Names by tweaking a few files in Visual Studio 2008.

With Visual Studio 2010 (Beta 2) you can edit these properties directly through the Publish Page. All Office projects in Visual Studio 2010 now have an Options button on the Publish Page, which allows you to spet these properties.

The Publish Options dialog is similar to the ClickOnce publish options dialog for other types of projects, but this dialog only displays the options applicable to Office projects.

Here is what these properties mean:

Publisher Name – The name of the Publisher as displayed in Programs and Features

Product Name – The name of the Solution as it will show up in the Programs and Features (Add Remove Programs Entry)

Support URL – A URL which End Users can visit to get support for this particular solution. The support URL shows up as a clickable link for the product name during the installation trust prompt.

Solution Name – (Friendly Name) This is the name of the Add-In as it is displayed in the Office Add-ins dialog.

Office Application Description – The description of the Office Add-in as displayed in the Office Add-ins dialog.

Add-in Load Behavior – Specifies whether the add-in should load when the Office Application Starts up or whether it should load on demand when the end user tries to interact with it. By default all add-ins are set to load at startup of the Office Application but if you care about Office startup performance and don’t want your add-in to be running all the time then you should consider loading it on demand.

Andrew Whitechapel has a post on how an Office add-in can be demand loaded using different loadbehavior values. Previously you had manually update the ClickOnce manifests with the appropriate load behavior value. With Visual Studio 2010 you can set the option to load the add-in on demand and the loadbehavior will be automatically set to 16 (connect first time) –> Load the add-in on startup for the first time and then load on demand from then on.

Loading an add-in on demand can help improve the startup performance of the Office application. It can also reduce the application’s working set as the add-in is not loaded in memory until the end user interacts with it. Setting the add-in to demand load is a good option if your add-in has UI based triggers, like a Ribbon item that the end user can interact with to load the add-in. However demand loading may not be a good option if your add-in is needs to listen to application events like opening a document etc all the time the application is running. So if your add-in doesn’t have to run all the time, then setting it to Load on Demand is a good option to consider.

Lastly, there is an interesting side note for those of you who may have changed their VS 2008 based project files based on my previous post. If you updated the project file using the same property names as that mentioned in the post, you can migrate that project to VS 2010 and continue using those property values. You no longer need the custom targets file as that functionality is now directly available in the Visual Studio common targets.

For more information, see Publishing Office Solutions.

Have fun with Visual Studio 2010 Beta2 and let us know your feedback!

Saurabh

Channel 9 Interview: John Durant on Developing Managed Applications for Office 2010 in Visual Studio 2010 (Beth Massi)

VSTO Team — Thu, 17 Sep 2009 21:41:19 GMT

Robert Hess posted an interview yesterday on Channel 9 with John Durant on Developing Managed Applications for Office 2010 in Visual Studio 2010. When you have 20 minutes you should check it out.

John provides some highlights as to what he’ll be showing in his PDC sessions, and some of the new features that developers can look forward to in Office and Visual Studio 2010.

Enjoy,
-Beth Massi, Visual Studio Community

BUG: “Old format or invalid type library” error when automating Excel (Christin Boyd)

VSTO Team — Tue, 07 Jul 2009 01:54:33 GMT

A customer recently reported this bug when running their Shared Addin for Excel on French Windows.

Error: 0x80028018 (-2147647512)
Description: Old Format or Invalid Type Library

His solution worked great on English Windows, but gave errors in any other language. This is a known problem in Excel and there are a few workarounds that work depending on the way you’re writing your Excel Addin. Let me take you through the problem, variations on the problem, and different solutions depending on which Visual Studio project template you choose to start your Addin.

The bug was originally documented in a KB 320369 article, which gives detailed repro steps, explanation, and two workarounds with sample code. So why am I writing a blog post if the KB article covers everything? Three reasons.

Because we’re fixing the problem in CLR 4 and I want to encourage you to use one of the recommended workarounds in your current solutions so that you’re ready when your users upgrade to .NET Framework 4.
Also, there are parts of the KB article that are a bit confusing, so I’ll try to add some color commentary to help explain what’s causing the problem.
And third, these problems do not occur if you use VSTO 2005 SE, VSTO 3.0 (which ships with Visual Studio 2008), or Visual Studio 2010. I’ll explain why and how later.

The KB article describes the problem:

Error: 0x80028018 (-2147647512)
Description: Old Format or Invalid Type Library

You receive this error calling an Excel method when the following conditions are true:

The method requires an LCID (locale identifier).

You run an English version of Excel. However, the regional settings for the computer are configured for a non-English language.

If the client computer runs the English version of Excel and the locale for the current user is configured for a language other than English, Excel will try to locate the language pack for the configured language. If the language pack is not found, the error is reported.

The quote from the KB article is accurate, but can be confusing. It is very difficult to determine if the Excel method you want to call requires LCID or not. The Primary Interop Assembly (PIA) does not indicate whether or not the LCID is needed, however VBA does not hide the need for LCID. Part of the reason why Excel hasn’t changed its methods is to maintain back compatibility with all the VBA code in the universe.

Fixed in VSTO

VSTO implemented a fix in VSTO 2005 Second Edition (SE). You can read more about this fix in Eric Carter’s blog post. The fix is also in all subsequent versions of Visual Studio 2008 and will be in Visual Studio 2010. You know you are using “VSTO” when you create a new Project in Visual Studio and select an Excel <version number> Workbook, Excel <version number> Template or Excel <version number> Addin. The fix was not implemented in the Shared Addin template in any version of Visual Studio. If you create a WinForms, WPF, Web or console application that calls Excel, then you will see this bug on non-English Windows.

Workarounds

If you are using the Shared Addin template, a WinForm, WPF, Web or Console application with any version of Visual Studio, then you should use the KB 320369 article to solve the problem.

The workaround is to write explicit calls to set the thread’s culture before calling into Excel. You can then reset the culture back to what it was before after you are finished calling Excel.

Install the Multilingual User Interface Pack for your version of Office.

Execute the Excel method or property by using InvokeMember so that you can specify the CultureInfo for the call. For example, the following code illustrates how you can invoke the Workbooks object Add method with "en-US" as the CultureInfo:

Dim oApp As New Excel.Application()
oApp.Visible = True
oApp.UserControl = True
Dim oBooks As Object = oApp.Workbooks
Dim ci As System.Globalization.CultureInfo = New System.Globalization.CultureInfo("en-US")
oBooks.GetType().InvokeMember("Add", Reflection.BindingFlags.InvokeMethod, Nothing, oBooks, Nothing, ci)

Or, instead of the above bullet and code sample, set the CultureInfo prior to calling the Excel method, and then you can reset it after your Excel call:

Dim oApp As New Excel.Application()
oApp.Visible = True
oApp.UserControl = True
Dim oldCI As System.Globalization.CultureInfo = _
    System.Threading.Thread.CurrentThread.CurrentCulture
System.Threading.Thread.CurrentThread.CurrentCulture = _
    New System.Globalization.CultureInfo("en-US")
oApp.Workbooks.Add()
System.Threading.Thread.CurrentThread.CurrentCulture = oldCI

The .NET Framework 4 will solve this whole culture problem. Excel is not going to change its culture sensitivity because of the need to support backwards compatibility. Starting with CLR 4.0, when managed code calls into a COM component and an LCID is required, then the CLR will pass LCID = 1033. Note that this is how VBA passes LCIDs. This means that Visual Studio 2010 project templates for Excel Addins can stop wrapping all Excel projects with LCID proxy. In the future, when you use VS 2010 and .NET 4 to write your Excel automation programs from a Shared Addin, console, Winforms, WPF, or Web application, you won’t need to wrap your calls either.

-Christin Boyd, Program Manager & Misha Shneerson, Senior Developer

32bit Visual Studio and 64bit Office (Christin Boyd)

VSTO Team — Thu, 11 Jun 2009 22:44:05 GMT

Visual Studio 2010 will ship with a 32bit version, and no 64bit version. My team built a very smart layer into Visual Studio 2010 to enable designers and debuggers that work with 64bit Office 2010 and 64bit SharePoint Server 2010.

For a good explanation of why the Visual Studio team chose to only build a 32bit version for the next release, you can find a blog post by Rico Mariani titled “Visual Studio: Why is there no 64 bit version? (yet)”

SharePoint Server 2010 will be 64-bit only. You can learn more about the requirements of Microsoft SharePoint Server 2010 on the SharePoint Team Blog entry “Announcing SharePoint Server 2010 Preliminary System Requirements” If you plan to build solutions for the next generation of SharePoint Server, then I recommend budgeting to purchase 64bit hardware.

-Christin Boyd, Program Manager, Visual Studio

TechEd Sessions on Office Development

VSTO Team — Fri, 08 May 2009 00:16:02 GMT

If you’re going to TechEd in Los Angeles next week, then don’t miss these four sessions:

DTL03-INT Meet the Microsoft Visual Studio Team
Christin Boyd, Eric Carter, Paul Yuknewicz, Jay Schmelzer, Dustin Campbell, Jonathan Aneja, Luke Hoban, Igor Zinkovsky, Faisal Nasir, Harry Pierson, Lisa Feigenbaum
Mon 5/11 2:45 PM-4:00 PM | Blue Theater 1

OFC325 Building Custom Applications in Microsoft Office Outlook 2007
Ty Anderson, Damon Armstrong
Tue 5/12 2:45 PM-4:00 PM | Room 408A

DTL324 - Microsoft Visual Studio 2010 Overview for the Business Application Developer
Jay Schmelzer
Tue 5/12 4:30 PM-5:45 PM | Room 515B

OFC324
Advanced Microsoft Office Word and Excel 2007 Development in Microsoft Visual Studio 2008 with Visual Studio Tools for Office
Eric Carter
Thursday 5/14 1:00PM-2:15PM | Room 515A

Of course, there are a dozen other sessions that appeal to Office developers and SharePoint developers. These are the four that I highly recommend. Originally I was going to list the 3 not-to-be-missed sessions, but then I couldn’t drop any of these from my list, so we have 4 Must See Sessions!

If you’re not going to TechEd, then please click the links on these speakers’ names to read their blogs where the will eventually post some of their demo code. Expect the posts to happen the Monday after their sessions. In the case of Eric Carter, he would probably love it if you’d buy his book, Visual Studio Tools for Office 2007: VSTO for Excel, Word and Outlook. Or you could just download a zip file with all of the of code from the book here. That should keep you busy for a while. The explanations in the book really do add to the overall value. I should credit the co-author, Eric Lippert. Both men are brilliant and funny, and very modest. At the Holiday Party this year, Eric Carter got up to sing karaoke and astounded us all with a bouncy rendition of “Sesame Street.”

-Christin Boyd, Program Manager, Visual Studio

Developing for Office and SharePoint Server 2010 (Christin Boyd)

VSTO Team — Fri, 01 May 2009 23:08:42 GMT

I get a lot of questions about the future.

When will Office and SharePoint release? First half of 2010.
Is VSTO part of Microsoft’s long term strategy? Yes! The Office tools shipped in VS 2008 and will ship in VS 2010 with lots of cool new improvements. We strongly encourage and support .NET development on the Office and SharePoint platforms.
Will there be better Team Development tools for Office and SharePoint developers? Yes! Future blog posts will tell you more.
Are there any pricing changes? See below note on SharePoint Designer.
Can I get Office 2010 Beta or SharePoint Server 2010 Beta? Yes, eventually. A few thousand enterprises, small businesses, developers, ISVs, Partners, schools and families have been invited to join an early private “technical preview” beta, and the rest of the world will get to test a later public beta. No dates have been announced. Read the Computer World article on the Office Beta.
Should I sanitize my keyboard to prevent the H1N1 flu? Yes, but don’t put it in the dishwasher like my internship roommate did after a cola spill. It was hilarious, and half the keys still worked!

In the coming months you will see a few more blog posts about the future and plenty of blog posts about developing today with Visual Studio 2008. For now, I’d like to review all of the official posts that Microsoft has released about developing SharePoint Server 2010 solutions:

Press Release on SharePoint Server 2010

SharePoint Designer is now FREE

Soma’s blog post “SharePoint tools support in Visual Studio”

Official Visual Studio 2010 home page

PDF of the Official Visual Studio 2010 Product Overview

Channel9 Interview with the Lead Program Manager designing the Office and SharePoint tools in VS 2010

If I’ve forgotten any of the official Microsoft announcements in this post, then please leave a comment with a link. Thanks!

-Christin Boyd, Program Manager