Browse by Tags

All Tags » proxygen
Showing page 1 of 2 (17 total posts)
  • Re: Compile-time error in generated proxy[.cs]

    Igor,Thanks for checking out VSTA.  The problem is you are generation a proxy for a class which uses an external base class (frmMain : System.Windows.Forms.Form).  When you generated the proxy file the following warning probably came up: ProxyGen.exe Warning: 0 : Warning: Using an external type as a base type will only work if those ...
    Posted to VSTA Tech Discussions (Forum) by Melody on June 24, 2008
  • Re: VSTA 2.0: ProxyGen does not work

    Thorsten, I was able to reproduce this.  The problem is not following the command switch with a colon and not using full paths.  Try using this command with colons and full paths: ProxyGen /v /l:C:\ShapeAppSamples\ShapeAppCSharp\core\base\bin\Debug\ShapeAppCSharp.exe /o:C:\ShapeAppSamples\Proxy_Descriptor.xml Here is the ...
    Posted to VSTA Tech Discussions (Forum) by Melody on June 19, 2008
  • Re: VSTA 2.0: ProxyGen does not work

    Thorsten,             ProxyGen will have an unrecoverable error if there are irresolvable assemblies referenced.  For instance, exposing a the exe from ShapeAppAdvancedCSharp (VSTA v 1 sample) to VSTA v 2 ProxyGen without having VSTA v 1 installed or exposing a VSTA v 2 sample ...
    Posted to VSTA Tech Discussions (Forum) by Melody on June 16, 2008
  • Nested Types in VSTA v 2 Part III: Entry Point Classes

    The sample in this post shows how to support nested types and implicitly declared events in entry point classes (note that the nested type is in the entry point class, but is not an entry point).  For types nested in an entry point class, the workaround in Part I is sufficient, no additional changes to the proxy are required.  For ...
    Posted to Melody's VSTA Blog (Weblog) by Melody on May 30, 2008
  • Nested Types in VSTA v 2 Part I: Types Nested in Non-Entry Point Classes

    ProxyGen does not support nested types; however, with a little manual editing of the descriptor and proxy files nested types can be supported in the Proxy.  There are three kinds of nested types that will be covered in this blog series (non-entry point, entry point, and implicitly declared events) and a sample will be available ...
    Posted to Melody's VSTA Blog (Weblog) by Melody on May 27, 2008
  • Proxy Indentation Fix

    The proxy and host type map provider code files generated by ProxyGen in VSTA v 2 are not indented.  Here's an easy fix.3 ways to fix indentation:1)  Through the menu:  Edit -> Advanced -> Format Document2)  Using short cuts:  Ctrl + K then Ctrl + D3)  In a macro:  DTE.ExecuteCommand(''Edit.FormatDocument'')
    Posted to Melody's VSTA Blog (Weblog) by Melody on February 28, 2008
  • Visual Studio 2005 VSTA v 2 Proxy Fix

     Overview: The VSTA v 2 ProxyGen tool creates proxy files designed to work with the updated C# compiler in Visual Studio 2008.  It is possible to modify this file to compile with Visual Studio 2005 and we offer a Visual Studio macro to automate these changes.   Attached macro: The zip file attached includes all the macro code ...
    Posted to VSTA Samples (FileGallery) by melody on January 30, 2008
  • Re: VSTA With VB.Net / Help Please

    bpreston, No problem- this was one of our first test cases.  There are a couple of things that may have caused this problem.  If you have VSTA v 1 installed you may be bringing up version 1 of ProxyGen or ProjectGen.  If you added the descriptor file to a project and then modified it, you may be running the original ...
    Posted to Discussion (Forum) by Melody on January 15, 2008
  • Using VSTA v 2 with Visual Studio 2005

    Microsoft recommends using Visual Studio 2008 for integrating VSTA v 2. However, if you choose to use Visual Studio 2005 the following will need to be addressed. 1)  The framework VSTA v 2 uses the 3.5 framework. It is very important that references, like System.AddIn, point to the 3.5 versions and not the 2.0 versions.  The .Net 3.5 ...
    Posted to Melody's VSTA Blog (Weblog) by Melody on January 15, 2008
  • Non-proxiable Types: A Deeper Look

    One of the most common questions we see when someone begins an integration is why can't System.Windows.Forms and objects derived from that class be exposed to add-ins.  Our typical answer is that System.Winows.Forms is not serializable and only serializable objects can pass through (or be exposed through) the proxy layer.  The SDK for ...
    Posted to Melody's VSTA Blog (Weblog) by Melody on December 11, 2007
1 2 Next >