.Net Core 6 requirement for ncrunch for rider

We are not allowed to install that version of .net core. is there a version that runs on 8 for example?

sammosampson wrote:We are not allowed to install that version of .net core. is there a version that runs on 8 for example?

No, sorry. We already need to cross compile the application for 4 different versions of .NET, it isn't really practical to go beyond that.

It's a bit unusual that you can't install NET6? It's a requirement for quite a lot these days.

.net core 6 is out of support now, so that is our security policy. I also have ncrucnh in VS and that works, so are they on different versions?

sammosampson wrote:.net core 6 is out of support now, so that is our security policy. I also have ncrucnh in VS and that works, so are they on different versions?

Yes. Under VS we're running on .NET Framework, version is dependent on VS itself. The latest should be .NET Framework 4.8.

is it possible to force NCrunch in rider to use the net8 runtime using the roll forward compatibility? or is there a reason it needs to rely on the net6 runtime specifically?

samholder wrote:is it possible to force NCrunch in rider to use the net8 runtime using the roll forward compatibility? or is there a reason it needs to rely on the net6 runtime specifically?

Not currently.

Likely it will eventually need to roll forward, as we'll need to host in newer versions of .NET when the next VS is released.

It is presently locked to net6 because it wasn't expected that customers would be unable to install this.

Sorry it's not an easy thing to change. If you can't install net6, I recommend sticking with VS for now.

So I managed to get .net6 again on my machine, but it is officially not supported by MS anymore so the powers that be are not happy. NCrunch now running in rider.
Next problem I have is that the rider ncrunch process periodically and randomly steals all available memory and grinds machine to a halt. Any idea what I can do about that?

I also occasionally see this memory issue with the VS version but not as frequently

Could you hook Rider's dotMemory onto the process and see where the memory is going? Something must be getting hungrier than it should.

Its hard to do anything at that point as it steals all the memory and freezes machine, takes all the effort to kill the process

Will try if i catch it early enough