-
Notifications
You must be signed in to change notification settings - Fork 223
Update to use the latest Roslyn version and add support for C# 7 #1046
Comments
Two main things to do:
|
Related issue w/ tuple syntax in generics: #1070 |
Went through the features and they all parse correctly (yay!). The work for this issue is then:
|
FYI checking this in is blocked right now on us having the right versions for our tooling to consume. |
- Added C# 7 test to validate questionable features work end-to-end. - Had to add several explicit package references to let our VS specific packages work as expected. #1046
- Added C# 7 test to validate questionable features work end-to-end. - Had to add several explicit package references to let our VS specific packages work as expected. #1046
- Added C# 7 test to validate questionable features work end-to-end. - Had to add several explicit package references to let our VS specific packages work as expected. #1046
- Added C# 7 test to validate questionable features work end-to-end. - Had to add several explicit package references to let our VS specific packages work as expected. #1046
Do we need to add |
Yes, you need to set |
@Eilon @NTaylorMullen @ryanbrandenburg Just a heads-up: we plan to release C# 7.1 along with Visual Studio 2017 version 15.3 (and C# 7.2 with version 15.5). My understanding is that ASP.NET Core and Razor don't need official updates for users to adopt those new versions of the compiler. I have instructions from Damian which I collected here. Also, just to confirm, since I saw a discussion of LangVersion "latest" above: "latest" means latest minor version (7.0, 7.1, 7.2, 8.0, etc), whereas "default" means latest major (7.0, 8.0, etc). Most Visual Studio templates use "default" and we let people opt-into "latest". That avoids problems if different people on a team use different versions of Visual Studio 2017. What language version does ASP.NET Core project teamplates use? I'd recommend either specific version that gets ramped up, or "default". |
There was a recent email thread about this - I've added you to that. We ship a dependency on Roslyn which we use for runtime compilation. We will need to adopt your candidate (non-build number stamped) packages when they are available from myget, and sim-ship with you when we go to nuget.org. It sounds like the right folks are looped in on your side. Regarding the templates, I believe ours are For Razor, it's our desire that runtime compilation should behave similarly to the rest of your project, so we want to get that information from the project compilation settings, and not hardcode anything. |
Sounds good. Just to clarify, I think "default" is good. I don't recommend changing to "latest". |
No description provided.
The text was updated successfully, but these errors were encountered: