Automation Add-Ins [Jesse Kaplan]

Interesting Finds: April 14, 2007

Jason Haley — Sat, 14 Apr 2007 19:05:27 GMT

re: Automation Add-Ins [Jesse Kaplan]

Tom Guinther — Sat, 14 Apr 2007 19:38:45 GMT

I think the stuff you guys are doing is great and I am looking forward to using it. Having developed an advanced plug-in architecture that seems similar to what you guys are doing (we are solving the same problems), I am disappointed that it is a 4GB+ download (and a host of other Orcas headaches as well) when it could clearly be implemented on the 2.0 framework. Eventually this wont be an issue and everyone will have .NET 3.5 etc.

Why not provide the same basic functionality for 2.0/3.0 in a 100kb download?

Tom

re: Automation Add-Ins [Jesse Kaplan]

CLR Add-In Team — Mon, 16 Apr 2007 07:51:50 GMT

I'm glad you're interested in what we're working on and all I can tell you about the deployment issues is to just hang in there. As we get into the beta phase and onwards towards release we (not the add-in team specifically but the .net framework team in general) will be working to make deployment of our beta and final bits easier.

In the end deployment of the 3.5 framework should be relatively easy as it will end up being just a bunch of new managed assemblies that depend on the latest SP of 2.0/3.0.

System.Addin is still evolving

DotNetKicks.com — Thu, 19 Apr 2007 19:34:04 GMT

You've been kicked (a good thing) - Trackback from DotNetKicks.com

What is ContractHandle and what happened to LifetimeTokenHandle?

noslenytram — Wed, 02 May 2007 00:29:06 GMT

In your sample you are using System.AddIn.Pipeline.ContractHandle which does not appear in C:\WINDOWS\Microsoft.NET\Framework\v3.5.20209.

It looks like you had some GAC references to C:\WINDOWS\assembly\GAC_MSIL\System.AddIn\3.5.0.0__b77a5c561934e089\System.AddIn.dll - but I don't think that should matter here? I repointed mine to the above path.

re: Automation Add-Ins [Jesse Kaplan]

CLR Add-In Team — Wed, 02 May 2007 02:11:05 GMT

I'm sorry about ContractHandle showing up in this sample. This is the peril of building samples on a dev box. Post-beta 1 we renamed LifetimeTokenHandle to ContractHandle, replacing ContractHandle with LifetimeTokenHandle in the code should fix everything up.

re: Automation Add-Ins [Jesse Kaplan]

Boris Yurovsky — Wed, 10 Oct 2007 18:36:25 GMT

This is great! This new Add-In architecture can help my company to solve the problems we're facing developing our framework. I was wondering if there is a way for a Add-In to pass UI objects through the pipeline to the host side. ExtensibleCalculator sample shows how to do it with WPF control using INativeContractHandle interface. How about Window.Forms controls? Is it the same interface to be used for it as well?

Boris.

re: Automation Add-Ins [Jesse Kaplan]

Marlun — Sat, 03 Nov 2007 03:23:24 GMT

I'm also wondering about the same thing as Boris Yurovsky.

re: Automation Add-Ins [Jesse Kaplan]

Claus Brod — Thu, 29 Nov 2007 19:10:04 GMT

Hi Jesse,

thanks for the sample code! Do you happen to have matching host/addin code for this as well? I think being able to step through calls between host and addin would make it much easier for me to understand what's going on.

Also, is there a sample out there which demonstrates a simple host object model without events? Maybe that would make it easier to grasp the basic concepts, too.

Thanks!

System.AddIn: Eventing zwischen Host und AddIn

Dariusz quatscht — Thu, 06 Dec 2007 19:05:15 GMT

Zum System.AddIn Namespace habe ich bereits das ein oder andere geschrieben. Das Beispiel das ich benutze

re: Automation Add-Ins [Jesse Kaplan]

Zq3 — Thu, 13 Dec 2007 19:10:44 GMT

Hi, I have a question for you regarding the Automation Add-Ins sample (http://blogs.msdn.com/clraddins/archive/2007/04/13/automation-add-ins-jesse-kaplan.aspx).

I implemented a host app and simple add-in to see the sample working, but I don't understand something.

I subscribe to the HostObject event (DocumentLoad) into the HostApplication, and then when in the add-in I receive the HostObject (in the Initialize method) the event is null, it's that right?

I was thinking that in the add-in I can raise the HostObject event and the host application will be called. Is that the normal behavior or the normal behavior is to subscribe also to the HostObject event in the add-in and then when in the host the event is raised this will call the add-in event?

Thanks

Extensibility; Clients and Services calling each other

Jack Gudenkauf (JackG) WebLog — Mon, 10 Mar 2008 23:30:15 GMT

In this post I will be showing sample code (also found on our CodePlex site ) as well as an execution