-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix building on 15.3 #19331
Fix building on 15.3 #19331
Conversation
@@ -10,6 +10,7 @@ | |||
<AssemblyName>Microsoft.CodeAnalysis.VisualBasic.CodeStyle</AssemblyName> | |||
<TargetFramework>netstandard1.3</TargetFramework> | |||
<PackageTargetFallback>portable-net45+win8;dotnet</PackageTargetFallback> | |||
<NoWarn>$(NoWarn);40057</NoWarn> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM as far as the nowarn change goes |
merging as these contain no changes to code behavior |
Changes to the compiler code base require explicit compiler sign off. This change does not have this. Also where is the ask mode approval for this bug? |
This is due to a bug in the SDK. They are unconditionally disabling option strict in the VB targets file that is included with the current 15.3 builds. The proper fix is not to make a code change. It is to re-enable Option Strict in the props files to work around the issue. Please open a bug to undo this change and put the proper fix into the code base. |
dogfooding 15.3 I ran into a lot of instances of BC40057 being offered due to default namespace imports of assemblies that don't exist (introduced [here](this dotnet/sdk#1127)). These seem safe to ignore.
BasicCodeAnalysis.vbproj
has a few new implicit conversion warning under 15.3 due to overload resolution on Interlocked.CompareExchange which I have fixed but I would like @dotnet/roslyn-compiler to review these changes.BasicScriptingTest.vbproj
also has implicit conversion errors that needed to be fixed up. I am not too concerned about these fixes in the test project but would like @dotnet/roslyn-interactive to take a look all the same.