I have a question described in the title.In more details: I'm working on a set of Blazor Components. It has many projects each packaged and published as Nuget packages. But of course all projects depends on some AspNetCore
Nuget packages. Currently using .NET 5 Version="5.0.0" packages. But recently Microsoft released Version="5.0.3".
<PackageReference Include="Microsoft.AspNetCore.Components.Web" Version="5.0.0" /><PackageReference Include="Microsoft.AspNetCore.SignalR.Client" Version="5.0.0" />
So the question is what is the recommended way to develop and distribute my (3rd) party Blazor Nuget packages?
- a). Keep the dependent MS framework packages version as low as possible? So it works with projects which targets lower versions and might work/or not work with projects which using the latest official MS
AspNetCore
packages, - b). Or always update to the latest
AspNetCore
packages to get all bug and security fixes? But in this case who wants to use my packages probably need to update their projects to the latest version as well? Which they might don't want to do.
I think the question can be relevant not just in case of Blazor Nuget packages. But all 3rd party Nuget package which uses other Microsoft Nuget packages