Inconsistencies in the nuget packages
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Compare the 3.8.1 and 3.8.2 NuGet packages, including the DLL file details, license.txt, and internal nuspec file mentioned in the report. Trace how these package artifacts are produced and verify that the package version, DLL metadata, and license information agree before republishing or correcting the affected package.
Written by the indexing model from the issue text.
Description
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
- Dominant language
- C#
- Stars
- 4.2k
- Forks
- 912
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from xceedsoftware/wpftoolkit
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
xceedsoftware/wpftoolkit#1808 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
xceedsoftware/wpftoolkit#1807 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
xceedsoftware/wpftoolkit#1806 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 45/100
xceedsoftware/wpftoolkit#1804 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
xceedsoftware/wpftoolkit#1802 · 3 comments ·
All issues in xceedsoftware/wpftoolkit
Similar issues
-
effort:S P3 refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
nightscout/nocturne#1532 ·
-
core dependencies
Difficulty 1/5 Under an hour Newbie friendliness 80/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
C#/.NET Roslyn LSP Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
DotNetNext/SqlSugar#1458 ·