It would be super practical and would simplify the documentation for every new project in a dotnet environment if at least the minimal libraries required to build a program would be published on NuGet. This would allow to, at least, be able to compile the project on another computer, or in CI, by referencing that package, and not be required to go set a reference to a specific file set at one location during the installation of "mccdaq.exe". NuGet packages have been standard at least for .NET projects for a while.
Furthermore, if it was possible, it would be even better if the package could target any modern supported dotnet versions, like .Net 6 or 7. Even if nothing is ported at all for newer .NET version, having it published on NuGet would help a lot with project compatibility with newer .NET versions.
.NET Framework 2.0 has been out of support since 2011, almost 12 years ago. However, if I understand the ULHelp.chm document correctly, if the UL for .NET is essentially a wrapper for the C library (without uncommon .net APIs that could be missing in .NET core or later .NET 5, 6, r 7), multitargeting that project to additionally include one of the .NET standard TFMs should be possible easily, and be able to release soon.
Question
echoix
It would be super practical and would simplify the documentation for every new project in a dotnet environment if at least the minimal libraries required to build a program would be published on NuGet. This would allow to, at least, be able to compile the project on another computer, or in CI, by referencing that package, and not be required to go set a reference to a specific file set at one location during the installation of "mccdaq.exe". NuGet packages have been standard at least for .NET projects for a while.
Furthermore, if it was possible, it would be even better if the package could target any modern supported dotnet versions, like .Net 6 or 7. Even if nothing is ported at all for newer .NET version, having it published on NuGet would help a lot with project compatibility with newer .NET versions.
.NET Framework 2.0 has been out of support since 2011, almost 12 years ago. However, if I understand the ULHelp.chm document correctly, if the UL for .NET is essentially a wrapper for the C library (without uncommon .net APIs that could be missing in .NET core or later .NET 5, 6, r 7), multitargeting that project to additionally include one of the .NET standard TFMs should be possible easily, and be able to release soon.
Link to comment
Share on other sites
1 answer to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now