Research the warning of MQT version 4.3.1 not found #204

Closed
opened 2026-04-09 10:51:41 +00:00 by b24johka · 4 comments
Collaborator

This can be easily resolved by referencing 4.3.1.873 instead, the question is if there is any reason not to.

This can be easily resolved by referencing 4.3.1.873 instead, the question is if there is any reason not to.
b24johka added reference #204-MQT-version-not-found 2026-04-09 12:08:01 +00:00
Collaborator

If we change the existing version in the project to a newer we can run in to some issues, libraries/api's/clients/brokers that only support this current version can cause issues within the project. There are also features in different MQT versions that are not supported between versions. Usually the version number is built as: major version (4), minor version (3), patch (1), build number (187) so it might not have an impact on dependencies.

If we change the existing version in the project to a newer we can run in to some issues, libraries/api's/clients/brokers that only support this current version can cause issues within the project. There are also features in different MQT versions that are not supported between versions. Usually the version number is built as: major version (4), minor version (3), patch (1), build number (187) so it might not have an impact on dependencies.
Collaborator

Should be fine for now since it can be built and run without any errors.

I still don't know why when using dotnet add package MQTTnet --version 4.3.1 it gives the .187 version (maybe it just does that) but if we ever encounter this warning problem again we might need to look into this further. For now we will implement this and see how it goes.

Should be fine for now since it can be built and run without any errors. I still don't know why when using dotnet add package MQTTnet --version 4.3.1 it gives the .187 version (maybe it just does that) but if we ever encounter this warning problem again we might need to look into this further. For now we will implement this and see how it goes.
a24timsv reopened this issue 2026-04-17 11:27:28 +00:00
Collaborator

This seems to have been lost after the weekly merge. We need to reimplement this to get rid of the errors. The customer has also said that this is the best solution.

This seems to have been lost after the weekly merge. We need to reimplement this to get rid of the errors. The customer has also said that this is the best solution.
Collaborator

This issue was resolved in #413. Closing this issue.

This issue was resolved in #413. Closing this issue.
a24timsv 2026-04-20 13:05:03 +00:00
Sign in to join this conversation.
No milestone
No project
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Andras/BoundlessFlowCampus2K#204
No description provided.