Please consider changing license to MS-PL

Sep 6, 2008 at 8:05 AM
Any particular reasoning behind selecting MS-LPL?
We develop cross-platform software, and the "Windows Only" part of the MS-LPL is a show-stopper for us. Unity (www.codeplex.com/Unity) for example, is using the MS-PL license, which does not have this limitation.

We are currently using Unity for our extensibility-needs, but Unity can hardly be called an Addin framework... We have been looking at Mono.Addins (http://www.mono-project.com/Mono.Addins) to enable more easy configuration since it's easy to configure and uses the MIT X11 license, but if MEF were MS-PL licensed, it would most certainly be an option for us.
Sep 7, 2008 at 2:02 PM
Edited Sep 8, 2008 at 6:08 PM

Hi Steinar

MEF ships in a future version of the .NET framework, which is only supported on windows. Mono supports linux et al, but it is an implementation of the .NET Framework, but it does not use the .NET Framework itself.

Thanks

Glenn

Sep 7, 2008 at 6:44 PM
Edited Sep 7, 2008 at 7:09 PM
> MEF ships in the next version of the .NET framework
Realy!? GREAT! Any blogs's or other articles that elaborate on this?

By next version I assume you mean .NET 4?  - Also, since you are releasing code - will this be backwards compatible with the current .NET version?

BTW: Mono.Addins is by no means limited to the Mono runtime. It's simply solving problems related to discovery, extension-dependencies and more to make it easy to extend applications. To have this functionality included in the runtime is- well - great. :-)

Keep up the good work, its exciting times!