TechEd 06: Chalk-talk today, MAF 101

I’m doing a “chalk-talk” today at TechEd — at 3:45 in DEV (Blue area) Theatre 1 in the TLC. The listed subject is Designing Managed Add-ins for Reliability, Security and Versioning, the same subject of the talk Jim and I did at PDC. I’ve refined the talk a lot since then. I’ve been giving this…

0

Categories

Those of you who have been following my blog will note that I have retroactively added some categories. I hadn’t bothered with categories in the past because almost all of my posts have been about MAF. Well, now that MAF is a real thing, we (meaning my team here at MS) are actively building two…

0

Adapters

Geez, did I make you wait long enough!?! I have been remiss, hopefully I will have time to do this more regularly. Those of you with kids know how time can evaporate. Anyway, I’ve promised a post on Adapters for months now, so here it is finally. As my colleague JackG said on my Proxies…

0

Proxies

I’m sure that everyone’s reaction to the contract concept is that it is very strict, that it can get complicated quickly, and that it is important to get it right and keep it right. In other words, you don’t want just anyone partying in the contract space. Furthermore, the programming model presented by contracts is not…

2

Are Arrays OK in Contracts?

I know its been a while, but I’ve been busy coding lately. That code will become public fairly soon, so I’ll talk about it then. I’m still working on the promised Proxies and Adapters post, it will be coming, I promise. But in the meantime, the subject of my last post came up in practical…

1

Reference vs. Value: Types, Passing and Marshalling

The .NET Programming Model makes a clean distinction between Reference and Value on three different levels. These three levels interact directly, and it is important to understand the distinction. This article may be old hat to many of you, but it is confusing enough on a daily basis over here that I decided to write…

6

Contracts and IContract

In my post What is an Addin? I said that a “contract” is just that: “a previously decided upon method of communication with rules and limitations.” Here is where we discuss the rules and limitations for .NET Addin contracts. In my post Addins in .NET I noted that we need to solve issues of versioning,…

1

MAF vs. COM

OK, I know I said my next post would be an in depth treatment of IContract, but I remembered I wanted to fininsh something I started with my earlied post Addins in .NET. I noted there that .NET currently was still analogous to the LoadLibrary\GetProcAddress era of Win32. In other words, it didn’t have the…

2

What is MAF?

As I noted we also unveiled yesterday the Managed Addin Framework (MAF). MAF is necessary realization of the Addin Model architecture. It is included in two assemblies: System.Addin and System.Addin.Contract. These assemblies will ship first with the VSTA product, in the Office 12 timeframe, and then be rolled into the next version of WinFX. So…

4