Skip to content
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

[From VSTS] Preview 4 will crash if loading F# and C# .NET Core projects where the F# project references a C# project #3373

Closed
cartermp opened this issue Jul 24, 2017 · 4 comments
Labels
Impact-High (Internal MS Team use only) Describes an issue with extreme impact on existing code.
Milestone

Comments

@cartermp
Copy link
Contributor

cartermp commented Jul 24, 2017

  1. Download this repro solution: 9140-crashproblemsimplesolution.zip
  2. Open it in VS 2017 Update 3 preview 4

Expected: No crash.
Actual: VS will crash.

Workaround: There is none.

Note: the above C# projects do set IOperation to true and use the preview FXCop analyzer. That does seem unrelated, as commenting out either will still cause a crash.

@cartermp cartermp added the Impact-High (Internal MS Team use only) Describes an issue with extreme impact on existing code. label Jul 24, 2017
@cartermp cartermp added this to the VS 2017 Updates milestone Jul 24, 2017
@cartermp cartermp changed the title Preview 4 will crash if loading F# and C# .NET Core projects where a C# project depends on Microsoft.CodeAnalysis.FxCopAnalyzers Preview 4 will crash if loading F# and C# .NET Core projects where the F# project references a C# project Jul 24, 2017
@cartermp cartermp changed the title Preview 4 will crash if loading F# and C# .NET Core projects where the F# project references a C# project [From VSTS] Preview 4 will crash if loading F# and C# .NET Core projects where the F# project references a C# project Jul 24, 2017
@cartermp
Copy link
Contributor Author

Not sure if this is related to the root cause of #3260 or not.

@Pilchie
Copy link
Member

Pilchie commented Jul 24, 2017

@jasonmalinowski just fixed this. See dotnet/roslyn#21035 and dotnet/roslyn#21023

@Pilchie
Copy link
Member

Pilchie commented Jul 24, 2017

Not the root cause of #3260.

@cartermp
Copy link
Contributor Author

Awesome. Thanks!

@cartermp cartermp modified the milestones: VS 2017 Updates, 15.3 Jun 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Impact-High (Internal MS Team use only) Describes an issue with extreme impact on existing code.
Projects
None yet
Development

No branches or pull requests

2 participants