MissingManifestResourceException when using Portable Class Libraries within WinRT
Our team recently ran into a strange issue. Our Windows Phone application targets Silverlight 8.1 but we have several WinRT 8.1 based background tasks. Recen...
Office Interop API Extensions Now Available!
As announced in Andrew Whitechapel’s post, version 1.0 of the VSTO Power Tools have been released! One of those tools is the Office Interop API Extensions, a set of libraries which extend the Office object model to simplify development on the Office platform. This past week I’ve blogged about the capabilities of these extensions and now you have the chance to try them out yourselves! Please let us know what works, what doesn’t, what could be improved, and what you would like to see in the future.
The VSTO Power Tools v1.0.0.0 is a collection of three packages found here. The Office Interop API Extensions is packaged as VSTO_PTExtLibs.exe Please note that, despite the prerequisites listed on the MSDN download page, the Office Interop API Extensions can be used with both Office 2007 and Office 2003, though .NET 3.5 is required in both cases. Also, these extensions do not have a dependency on VSTO; they can be used within any application which automates Office.
This post was migrated from my MSDN blog, Visual Studio Tools and Anything Else I Can Think Of, and written as a Microsoft employee.
2014
2012
Dynamically Add Content to Windows Azure Application Roles
In a previous post I introduced the concept of Role Content Folders and how they can be used to deploy additional content (e.g. configuration files, runtime ...
Transform Windows Azure Service Model Files During Packaging
The latest versions of the Windows Azure Tools for Visual Studio have the ability to maintain multiple versions of the Service Configuration (.cscfg) file.&n...
Ignore Validation Warnings when Packaging a Windows Azure Application
When a package fails to deploy to Windows Azure (or deploys but its roles fail to start properly) it can be difficult to determine what went wrong. In many c...
Add Files to your Windows Azure Package using Role Content Folders
Windows Azure applications often need to package and deploy additional content. This could be advanced configuration files such as the diagnostics.wadcfg for...
2008
Finding DASL Property Names
The LINQ-to-DASL provider of the Office Interop API Extensions provides a very limited set of mappings between its query types and their associated DASL prop...
Debugging LINQ-to-DASL Queries
When your LINQ-to-DASL queries do not return the results you expect, how do you determine where the problem is? The issue could be that the query simpl...
Filter Outlook Items by Date with LINQ to DASL
I received an email over the weekend asking why the following LINQ to DASL query threw an exception: Outlook.Folder folder = (Outlook.Folder)Application.Se...
LINQ to DASL Walkthrough
Now that the Office Interop API Extensions have been released, I thought I would post a complete walkthrough of a simple LINQ to DASL application. Let's star...
Parameterized Properties and the Office Interop API Extensions
One of the disadvantages of C# compared with VB is its lack of support for parameterized properties. Instead, parameterized properties in C# are exposed as ...
Office Interop API Extensions Now Available!
As announced in Andrew Whitechapel’s post, version 1.0 of the VSTO Power Tools have been released! One of those tools is the Office Interop API Extensions, a...
Extending LINQ to DASL with Custom DASL Properties
In an earlier post I discussed LINQ to DASL, part of the Office Interop API Extensions, which is one of the forthcoming VSTO Power Tools. LINQ to DASL ...
Using LINQ with the Office Object Model
In my last post I talked about LINQ to DASL, a LINQ provider that converts query expressions into their DASL equivalent in order to efficiently filter item c...
Query your Outlook Inbox with LINQ to DASL
Quick, tell me what the following code does:
Banish Missing.Value with the Office Interop API Extensions
I like VSTO. I like C#. What I don’t like is having to write VSTO code in C# like:
2007
VSTO at Portland Code Camp v3.0
Yesterday I gave a presentation on VSTO at the third annual Portland Code Camp. I demonstrated an Outlook 2007 add-in that used Outlook Form Regions, WCF, an...