License confusion (MIT or MS-PL?)

[crud89]

I am a little bit confused how the project is licensed.

• NuGet states it's MIT.
• This file states it's MIT.
• But the top-level license (also used by GitHub) says it's MS-PL.

Not a big deal, since both are pretty similar, however I am not quite sure which one I should include for distribution. I would appreciate a clarification statement.

Thank you and keep up your great work! 😊

[Dirkster99]

Hi, thanks for your feedback. The License is changed to MS-PL for the next version 4.0 (in master but not released to Nuget yet). All previous versions (prior to 4.0) are released under MIT. Both versions are compatible which is why the change itself should not be any problem for anyone using it commercially or non-commercially. I felt that I should use MS-PL here since it is the more accurate thing to do because XCeed's WPFToolkits versions 3.6 and older are also licensed with MS-PL. XCeed's WPFToolkits versions 3.7 and newer use a 'custom community license' I am not interested in implementing.

In version 4.0 we also change the AvalonDock namespace back to the namespace that was used in AvalonDock 2.0 and earlier versions (the versions prior to XCeed's contributions) to make it more obvious that is fork is independent of the XCeed version as we continue to develop it.