I'm wondering if internally there have been high level discussions surrounding the future of add-ins with the next incaranation of WHS (I'm talking about 2.0; not PP2).
In particular:
- is 100% compatibility of existing add-ins a priority (ie literally drop-in binary compatibility of an add-in today into WHS 2.0)
- if not, is the goal to simply force a recompilation with potentially minor code changes to a new interface, but thereby requiring add-in developers to potentially maintain two different versions
- if not, will there be wholesale arechitetural changes, for example leveraging System.AddIn namespace (requires .Net 3.5).
The reason is if there has alread been a stake in the ground set as to whether to go the pather of "compatibility trumps new features" versus "features trumps compatibility", it would be great to share it with the development community now, and give us some heads up.
If these discussions have not been had, it may not be a bad idea to have them *with* the community.
Ryan
See my answer in your other post.
