Earlier Support for .Net 5.0
Currently, NCrunch supports up to .Net Core 3.1
.Net 5 is on "5.0.0-preview.7" (2020-07-21) now and will be released for 1st November.
My leading role leads me to develop often en preview and it has a burden to switch OFF NCrunch for those projets (when preview .Net Core 3 was the same burden).
My question is when the support is planned to be? And Can, principally can you change your workflow to have "Earlier support" for the new versions?
Christian P. Gyssels
Implemented and released as part of NCrunch v4.5.
Thanks for the new version Remco. Works like a charm for me :)
Thank you for the prompt update Remco. Looking forward to the build :)
The final planned RC has been released. It would be great if we could get some idea of when NCrunch will support it since NCrunch is so vital to my workflow that I simply will not work without it if I can avoid it. Thus my planning for future work is very much dependent on when NCrunch delivers support for .Net 5.
I'm not asking you to "hurry up". Just trying to make it clear why it is important to some of your customers to be informed about these things in advance if possible.
Edit: Making preview builds available in these situations would also be very much appreciated. Even if somewhat limited or unstable it may be good enough for some customers to get started with development on the the framework.
Although I appreciate the need for many people to be able to use preview platforms with NCrunch, we have a general policy of only introducing support for platforms and toolsets when they have reached RTM or are in their final RC stages.
The reason for this is that supporting integration with preview software is very expensive for the following reasons:
1. The software is often undergoing heavy changes while in preview state. These changes can result in large amounts of work landing in the bin when they happen (for example, we lost 5 months of work to the DNX u-turn)
2. There is usually little to no documentation or information about the workings or features of the software, so we usually need to proceed with guesswork and ILSpy.
3. While in a preview state, the software often has major functional problems that are not widely disclosed. This can result in us spending days chasing problems that aren't ours. When users post about issues, it's hard for us to provide support because we don't know if the issue they're posting about is actually in the platform rather than NCrunch.
4. It destabilises our own infrastructure. Preview toolsets do not always have well tested installation structures. Installing them can break things in a complex dev environment. Consider that we support all versions of VS released over the last 12 years, and we need them all to be able to compile projects without issues. It's possible to waste lots of time when a preview toolset breaks the dev machine and leaves it broken when uninstalled.
5. It's terrible for morale. People are less productive when they can't stabilise code or reach a state of satisfactory completion for the above reasons.
We've tried to integrate with things in a preview state many times in the past, and we've been burned again and again. Sorry, we're not going to do that any more. We'll add support for .NET 5 when it's release ready.