Closed stuarthillary closed 1 year ago
Yup that's unfortunate it. I wrote it for .NET7 as at the time as I wasn't planning on building a dotnet tool like this, and the other installations are self-contained.
Could you not simply install the .NET7 SDK or runtime? That will not stop you building for .NET6.
Ordinarily, I would just install the .NET 7 SDK. I am working on a CI server where we are working with .NET 6 SDK (which is LTS) rather than .NET 7 (which is STS). There is a workaround though, which is to use the RPM package for PupNet installation.
I guess if I sound reluctant it is because I wouldn't want to have to release two versions: one for .NET6 and one for 7, with .NET8 just around the corner.
It isn't clear to me with a .NET6 app will run on an .NET7 runtime. However, I guess we can try it.
I think, in principle an app compiled with the .NET 6 SDK should run on the .NET 7 runtime. However, there may be some breaking changes that affect things
https://learn.microsoft.com/en-us/dotnet/core/compatibility/7.0
Done: https://github.com/kuiperzone/PupNet-Deploy/releases/tag/v1.2.2
Will address RPM issues separately.
I tried to install PupNet as a global dotnet tool on a Redhat instance that has version 6.0.109 of the .NET SDK installed.
Would it be possible to widen the .NET version compatibility of PupNet when installing as a global tool?