Thank you for the video. FYI for the reason why 7.1 and 7.2 are not enabled by default look at a youtube video called "C# 7.1, and 7.2: The releases you didn't know you had - Bill Wagner". In essence though; it's because if a release changes how existing code works it can break a company's programs and so they allow you to opt in on a by project basis as you need.
Thanks for explaining. I didn't realize there were any breaking changes though. Last breaking change I remember was a different behavior fo *foreach*, and that was a while back.
No worries:) To be honest I don't actually know if there's anything breaking, I haven't watched anything on 7.2 yet other than a little bit of the above video. I believe it's more for future proofing, we get used to the pattern now and so if something does happen we're thinking about whether we want to upgrade or not instead of doing it without checking. May not be necessary for a while but just a bit of extra protection for the projects we work on.
![What's New in C# 8 [BETA, INCOMPLETE]](http://i.ytimg.com/vi/nhxpeHhq2To/mqdefault.jpg)
![What's New in C# 8 [BETA, INCOMPLETE]](/img/tr.png)
Thank you for the video. FYI for the reason why 7.1 and 7.2 are not enabled by default look at a youtube video called "C# 7.1, and 7.2: The releases you didn't know you had - Bill Wagner". In essence though; it's because if a release changes how existing code works it can break a company's programs and so they allow you to opt in on a by project basis as you need.
Thanks for explaining. I didn't realize there were any breaking changes though. Last breaking change I remember was a different behavior fo *foreach*, and that was a while back.
No worries:) To be honest I don't actually know if there's anything breaking, I haven't watched anything on 7.2 yet other than a little bit of the above video. I believe it's more for future proofing, we get used to the pattern now and so if something does happen we're thinking about whether we want to upgrade or not instead of doing it without checking. May not be necessary for a while but just a bit of extra protection for the projects we work on.
Very well explained.