Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fx resolve error? #630

Open
sommmen opened this issue Oct 16, 2024 · 5 comments
Open

Fx resolve error? #630

sommmen opened this issue Oct 16, 2024 · 5 comments

Comments

@sommmen
Copy link

sommmen commented Oct 16, 2024

Hello i'm getting the following warnings in my build output when moving to 5.5.6;

warning NU1701: Package 'MailChimp.Net.V3 5.6.0' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8, .NETFramework,Version=v4.8.1' instead of the project target framework 'net8.0'. This package may not be fully compatible with your project.

@glasssd
Copy link

glasssd commented Oct 16, 2024

Seeing the same things. I can't see where the changes found in 5.6.0 are being pushed from. They aren't in this repo, but the target framework has changed from Standard 2.0 to 4.7.2

@lahma
Copy link

lahma commented Oct 17, 2024

Assembly diff doesn't sound any alarm bells, but boy this feels fishy. NuGet package points to latest repo commit as being source but it isn't. Seems that main addition is ConnectedWebsiteLogic, its interface and models.

@sommmen
Copy link
Author

sommmen commented Oct 17, 2024

Assembly diff doesn't sound any alarm bells, but boy this feels fishy. NuGet package points to latest repo commit as being source but it isn't. Seems that main addition is ConnectedWebsiteLogic, its interface and models.

I had the same feeling and never pushed this to prod. Could be the dev pushed this locally? @brandonseydel where does the latest nugget come from since the code is not on master?

@IT-VBFK
Copy link

IT-VBFK commented Oct 20, 2024

Apart from that I cannot use it (because I use .NET8) this seems like a release by accident to me...

@meriturva
Copy link

I guess it is better to deprecate nuget package 5.5.6 and release a correct one. Right?
Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants