Consider updating the shipped roslyn files?

[AraHaan]

Is it possible to update roslyn 4.1.0 that gets packaged into this to a much more updated version that ships with the .NET SDK / Visual Studio 2022 itself?

[AraHaan]

Edit: looks like there is roslyn 4.7 and roslyn 4.8 as well.

[MattBussing]

I love the idea of updating to latest! Do you have reasons you need the 4.8 version over the 4.1 version, other than you want to stay up date? Listing the reasons could help the developers choose to prioritize this work.

[AraHaan]

To be able to use the latest bug fixes in the compiler, as well as being able to use things like C# 12 on .NET Framework cshtml files for my web applications. Also would help for future migration to core to be not as painful as well as it would mean updating all of the cshtml files anyways to the newer language versions of C#. Also because I made a version of this that also includes a few performance fixes as well and everything seems to work so far without issues anyways.

[MattBussing]

Great reasons!

[StephenMolloy]

As you've noticed, we don't tend to refresh this package for every release of Roslyn. Our team doesn't really have the resources to do so unless we're also shipping fixes in our package at the same time.

But you're not locked into using only the version of Roslyn that is shipped with this package. If you would like to include a different version at build time, you can use the RoslynToolPath setting. If you instead want to point your already-compiled project to an updated Roslyn build at runtime, there are three ways to configure this provider with a new Roslyn location that exists in your runtime environment.

Of course, we do update to the current Roslyn whenever we do ship new fixes and features in provider code. I'll try to get a refresh out the door shortly.