For a maui class library, use a fixed maui version or $(MauiVersion)

[AndreasReitberger]

I'm building a Maui class library. Since now I always installed the latest available version of maui with the nuget browser.
But, would it be better to just use $(MauiVersion) instead of a fixed version?
What`s the right approach?

<PackageReference Include="Microsoft.Maui.Controls" Version="10.0.50" />
<!-- or --->
<PackageReference Include="Microsoft.Maui.Controls" Version="[10.0.50,)" />
<!-- or --->
<PackageReference Include="Microsoft.Maui.Controls" Version="$(MauiVersion)" />

@jfversluis maybe you can bring some light into this. Thanks a lot for all your work and content so far :)

[jfversluis]

As with anything (in software development): it depends.

If this is a library that is shared with the public, you probably want to be as compatible as possible, which means: the dependency on MAUI should be as low as possible. Additionally, you probably don't want that to version to change when the workload updates, especially if you are using hosted build agents that are outside of your control. And that is exactly what $(MauiVersion) does.

So assuming all these things:

• You're using a hosted build agent and may or may not pin the workload version
• This library is something that the public will use
• You don't depend on any specific added API/fix in a specific MAUI version

Keep the dependency at the lowest version possible. That way consumers of your library will not be forced to update their MAUI version to use your library when they aren't ready to do that. And unless a MAUI version goes out of support or a MAUI version adds a specific fix or API that your library depends on, only then bump the version.

Does that make sense?

[AndreasReitberger]

Thanks @jfversluis for this detailed answer, solves it for me yes :)