XceedBoucherS
commented
5 months ago Hi,
Sorry for the confusion. v3.8.2 was intended to be the v3.8.1 version with an MS-PL license. You can consider it MS-PL, no matter what its nupkg says about the license. That nupkg was probably forgotten when the License was change from Xceed to MS-PL.
As for the package dlls, they are named v3.8.0 because this is the built version of the product. The thing is that when importing a package to NuGet, it can't have the same version number as another one. So we had to increase the 3rd number to v3.8.1 and 3.8.2. All the v3.8.x versions are the same except for the license which was changed from Xceed to MS-PL between v3.8.1 and v3.8.2.
Thank you
DaveInCaz
zhongruijia
Hello, as noted elsewhere (https://github.com/xceedsoftware/wpftoolkit/issues/1557#issuecomment-1883384700) there was a change in licensing terms around the 3.7, 3.8 releases.
My project was using 3.8.2 (with the MS-PL) license. But after a build in the output folder all the Xceed DLLs have 3.8.0 as their file details. (Example below)
I downloaded the Nuget package and looked inside, and sure enough that is what it has. The 3.8.2 package has 3.8.0 DLLs.
Also, the 3.8.2 nupkg has a license.txt which is not MS-PL, it is "XCEED SOFTWARE, INC. COMMUNITY LICENSE AGREEMENT (for non-commercial use)".
However the internal nuspec file says, "offered under the MS-PL License. v3.8.2 is equivalent to v3.8.1 with an MS-PL license."
The 3.8.1 nupkg also has 3.8.0 DLLs, but the licensing information looks OK.
I guess the main consequence of this is that any software which includes 3.8.0 DLLs with it, it seems impossible to tell which license was actually used by the developer.
Thanks