Blogs

.NET 4 and VSTA redistribution

With the advent of .NET 4 and related questions about VSTA's compatibility, we tested to confirm the following: Redistribution of VSTA 2.0 (with your application) requires .Net 3.5 SP1 to be installed on the target machine. Starting with a clean Windows...

Posted to Gary Depue's VSTA Blog by Gary on 10-22-2010

Filed under: .NET 4.0, redistribution, deployment

Supporting the “new” Operator in VSTA Add-Ins

It is possible to support the “new” operator in VSTA add-ins. Integration styles which do not use a full proxy, such as NoRuntime and ProxyShim, can easily support this feature. All that is required is public constructor methods in the host...

Posted to Melody's VSTA Blog by Melody on 10-20-2010

Filed under: vsta, add-in, Proxy, NoRuntime, ProxyShim, new operator

ShapeAppDynamicProgrammingModelCSharp_ProxyShim Sample

Summit now offers the he ShapeAppDynamicProgrammingModelCSharp_ProxyShim sample which is based both the VSTA 2.0 SDK sample ShapeAppDyanmicProgrammingModelCSharp and the Microsoft endorsed ShapeAppMacroRecordingCSharp-NoRuntime sample. This sample references...

Posted to Melody's VSTA Blog by Melody on 10-19-2010

Filed under: vsta, add-in, DynamicProgrammingModel, ProxyShim, new operator

Integration Styles and the Benefits: SDK, NoRuntime, and ProxyShim

For VSTA integrations, there are a variety of ways in which the host can load and interact with add-ins. Three styles of interest are SDK, NoRuntime, and ProxyShim. Each style of integration has many pros and cons to consider before deciding on which...

Posted to Melody's VSTA Blog by Melody on 10-14-2010

Filed under: vsta, addin, add-in, DPM, NoRuntime, ProxyShim

Is VSTA 2.0 supported under Windows 7 and Visual Studio 2010?

I’ll preface my answers about support for VSTA in Windows 7 and Visual Studio 2010 with a quick synopsis of VSTA 2.0 platform-related elements. VSTA 2.0 is based on VS2008 and .NET 3.5 SP1. It supports 32-bit and 64-bit platforms. · The VSTA...

Posted to Gary Depue's VSTA Blog by Gary on 10-07-2010

Filed under: VS2010, Windows 7, .NET 4.0

Referencing Host Items in a DPM Project from the Host Item Container

In Dynamic Programming Model (DPM) style integrations there are three levels of correspondence between a DPM add-in and the host: 1) “Host Item Container” : This is the entry point type which contains the host items and has its own code file...

Posted to Melody's VSTA Blog by Melody on 09-30-2010

DPM Code Files for Renamed Host Items

For Dynamic Programming Model (DPM) style integrations, when a host item is renamed the corresponding code file in the DPM add-in project maintains its original file name and displays the updated host item name in parentheses next to the file name (see...

Posted to Melody's VSTA Blog by Melody on 09-28-2010

Filed under: vsta, DynamicProgrammingModel, DPM, Host Item, Rename

DPM Add-in Project Host Item Code File Names

For DyanmicProgrammingModel (DPM) add-in projects, the file name of the host item code file generally matches the name of the host item. For example: in the SDK sample ShapeAppDynamicProgrammingModelCSharp the host item “Drawing1” would have...

Posted to Melody's VSTA Blog by Melody on 09-23-2010

Filed under: vsta, DynamicProgrammingModel

Keeping a DPM Add-in Project in Sync with its Associated Document

When working with a Dynamic Programming Model (DPM) style integration, it is important to keep the DPM add-in project in sync with the associated host document. There are two items which must be kept in sync: the DPM add-in project host item code files...

Posted to Melody's VSTA Blog by Melody on 09-20-2010

Filed under: vsta, DynamicProgrammingModel

Add-in Management Options

There are many different ways to manage add-ins. Below are some common add-in management styles which can be used alone, combined, or used side by side. 1) Basic: all interactions between the host and add-ins are executed in the Startup and Shutdown methods...

Posted to Melody's VSTA Blog by Melody on 08-24-2010

Filed under: vsta, add-in, Proxy, ShapeAppCSharp

Using a Registry Entry to Specify the DebugInfoExeName

When a VSTA add-in is run or debugged from a stand alone or destructive scenario, the life of the host application is tied to the debugging or running session. In order to start the host application the VSTA add-in must know the location of the exe to...

Posted to Melody's VSTA Blog by Melody on 07-29-2010

Filed under: vsta, projectgen, Project Template

Binding Redirects

As mentioned in Gary's blog Dependent Assembly Binding Redirect (by version) , it is possible to use a configuration file to change which version of an assembly to use. This can be very helpful in "tight versioning" scenarios (see blog Proxy...

Posted to Melody's VSTA Blog by Melody on 07-27-2010

Filed under: vsta, Proxy, Binding Redirect

File Name and Path Length Limits

Windows imposes limits on the lengths of path and file names maxing out around 260 characters. For all Visual Studio projects, including VSTA projects, these limits are further reduced to accommodate for the entire file structure of the project. For instance...

Posted to Melody's VSTA Blog by Melody on 07-15-2010

Alternatives to Invoking to Run a Method in an Add-in

In scenarios where a method or macro within an add-in needs to be run several times in a short time span, for example 60 times a second, invoking the method may not be the best option. The invoke call, as seen in the ShapeAppMacroRecordingCSharp sample...

Posted to Melody's VSTA Blog by Melody on 05-14-2010

Microsoft releases Security Bulletin MS10-031 - Critical

Microsoft has released Security Bulletin MS10-031 which resolves a privately reported vulnerability in Microsoft Visual Basic for Applications (VBA). The complete Security Bulletin can be found here Summit has made the updated version of the Visual Basic...

Posted to Dave's Blog by dschneid on 05-11-2010

Filed under: Microsoft Security Bulletin MS10-031, VBA

Tags

Blogs