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

Upgrade MQTTNet to latest version, add support for .NET 5 #163

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

duizendnegen
Copy link

We are running .NET 5 with our Azure Functions; this PR updates this project to support that.

@duizendnegen
Copy link
Author

Some WIP on our side: we're still testing it with a live MQTT queue, so not 100% ready to merge yet.

@pseabury
Copy link

@keesschollaart81 can this be merged and possibly updated for NET6 and latest MQTTNet package?

@keesschollaart81
Copy link
Owner

Will look into this next weekend. LGTM!

@duizendnegen
Copy link
Author

Sorry to say that we didn't get this working on our end; I would recommend against merging as-is. Skipping .NET 5 and going straight to .NET 6 will most likely give you a much better experience for upgrading.

@keesschollaart81
Copy link
Owner

Good that you're report this! What was the issue / should I look out for?

@duizendnegen
Copy link
Author

Honestly; actually receiving a message from a test queue. I don't remember exactly because it's been too long ago. The different modes of running it isolated / non-isolated ended up biting us in the rear as far as I remember.

@pseabury
Copy link

@duizendnegen I'm most interested in running NET6 Isolated - actually about to try it - as Microsoft claims it's the future of Functions. Do you recall if isolated was the problem?

@pseabury
Copy link

I tried to start porting to NET6/Isolated but as you probably know configuration & bindings are way different. I wasn't able to complete a working version of this library yet.

@duizendnegen
Copy link
Author

I had a similar issue; configurations / bindings being way different.

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

Successfully merging this pull request may close these issues.

4 participants