question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Breaking Change Disscussion: .NET 4.5 Support

See original GitHub issue

Currently ExtendedXmlSerializer supports .NET Framework 4.5.

This is not ideal as it essentially forces two builds for every release: .NET 4.5 and everything else.

I wanted to start a discussion around this if anyone is still using .NET 4.5 and if this is used in any capacity with ExtendedXmlSerializer.

The idea is that we could bump the ExtendedXmlSerializer package to 2.2.x and make ExtendedXmlSerializer a strictly .NET Standard 2.0 library, which would support 4.6.1 as a minimum baseline.

If you absolutely require 4.5, you would have to force your dependency to the last version of ExtendedXmlSerializer 2.1.x (and pray you don’t run into any bugs).

I am open to discussion around this and welcome any comments. Speak now or forever hold your peace. 😆

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:13 (12 by maintainers)

github_iconTop GitHub Comments

0reactions
Mike-E-angelocommented, Jul 6, 2021

Dang, a better memory than I @MagicAndre1981! So essentially we become a .NETStandard-only library at this time, I would take it. I’m OK with this as it would greatly simplify our test suite. Still feels a little wrong chopping it all away, though.

I guess technically that’s a non-issue. Conceivably, we would bump the major version (4.0.0), so those who still need to use .NET Framework can still use the 3.x found on nuget.

In any case, please do feel free to open a new issue around that time and we can take it from there. 👍

Read more comments on GitHub >

github_iconTop Results From Across the Web

Breaking Changes Planned for .NET 4.5 - InfoQ
NET 4.0 assemblies. Much to the chagrin of developers, Microsoft will be updating core assemblies “in-place”. Aside from making much harder to ...
Read more >
Compatibility of .NET Framework 4.5
We review potential breaking changes, and help teams understand and assess the compatibility impact of new features and bug fixes. For .NET ......
Read more >
Will I have any issues if I upgrade from .NET 4.0 to 4.5
Are there any breaking changes in 4.5 that are likely to throw my 4.0 app offline; If things go bad, can I backout...
Read more >
Is updating to a new .NET-version a major or minor version ...
A technology change from .Net Fw 4.8 to 5.0 will definitely cause a breaking change for libraries based on that technology. – Doc...
Read more >
Risk of updating the .NET Framework : r/dotnet
I'm working in operations and we want to update the .NET Framework 4.5 and 4.5.1 to 4.7.2 as those old versions are unsupported...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found