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

.NET Framework support dropped from v5.0 #2084

Open
wazzamatazz opened this issue Sep 24, 2024 · 7 comments
Open

.NET Framework support dropped from v5.0 #2084

wazzamatazz opened this issue Sep 24, 2024 · 7 comments
Labels
question It is a question regarding the project

Comments

@wazzamatazz
Copy link
Contributor

Describe your question

I note that support for all frameworks except for net8.0 is being dropped from MQTTnet 5.0. In the upgrade guide it mentions that one of the reasons for dropping support is to make use of types such as Memory<T> and Span<T>. However, these types are already available on earlier versions of .NET and .NET Framework via the System.Memory package.

I understand the desire to drop support for older frameworks but .NET Framework is still supported by Microsoft with no support end date currently scheduled for .NET Framework 4.7 and above (see here). With this in mind it would be great if the MQTTnet client could continue to support .NET Framework in some way even if server support was going to end.

Which project is your question related to?

  • Client
  • ManagedClient
@wazzamatazz wazzamatazz added the question It is a question regarding the project label Sep 24, 2024
@TimMakins
Copy link

Yes, PLEASE include support for .NET Framework 4.7 and above. This is very important for me, too.

@rido-min
Copy link
Member

@wazzamatazz @TimMakins you can continue using v4, as it "will receive hotfixes but no new features."

Span<T> was only one example, there are other areas such Certificate Management that are only available in .NET7+, and there are also many C# features not available for older target frameworks.

just for curiosity: What's the reason to keep using .NET Framework 4.7.2 in a client-side application?

@wazzamatazz
Copy link
Contributor Author

In my case, it's because of some upstream dependencies that mean that we can't move off of .NET Framework entirely.

We integrate with a lot of industrial process systems and in some cases (particularly with older systems) the vendor SDKs explicitly only support .NET Framework because they make extensive use of features like AppDomains.

@TimMakins
Copy link

In my case, it is because I use Visual Basic.Net to create Windows Forms Desktop applications, using .NET Framework 4.8. To move over to Net 8.0 would mean converting everything to C# and re-writing tens of thousands of lines of code, plus coping with the many significant changes that .NET Framework 4.8 > Net 8.0 involves.

@ArcadePlayer1999
Copy link

My use-case is a visual studio extension, it requires using 4.7.2.

@chkr1011
Copy link
Collaborator

Version 4 will still be around and receive bug fixes and probably some features.

@ArcadePlayer1999
Copy link

Great, good to know it will still get bug fixes, etc.

I apologize if this is stated somewhere - is it possible to use the 4.x client with a 5+ server?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question It is a question regarding the project
Projects
None yet
Development

No branches or pull requests

5 participants