Extensibility (Add-In) Guidance


I have been asked on several occasions to articulate type versioning and isolation (and ensuring types do not leak) semantics.  I worked with the CLR Add-In team to define and document these semantics relative to the System.AddIn model but you can certainly apply this knowledge to your .Net development.  The document is written as a list of constraints allowed in a System.AddIn Contract.  Here is the link to the Restrictions on Contracts.

Comments (3)
  1. This posting is in response to a F.A.Q. (Frequently Asked Question) I receive regarding the Add-In model

  2. RSS It All says:

    This posting is in response to a F.A.Q. (Frequently Asked Question) I receive regarding the Add-In model

  3. We have gone through some naming changes with WinFX and .Net . And we have gone through a few on the

Comments are closed.

Skip to main content