-
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
Microsoft.Cci.PdbWriter.GetAssemblyReferenceAlias throws Null Reference exception #74872
Comments
Instead of creating a minimal example, you could create a complog and send it to us for investigation. Note that it will contain all inputs, but you can send it privately via VS feedback (just link the ticket here then). |
@jjonescz . here's the VS feedback link |
|
@tmat Could you please advise what import information should be emitted for the scenarios above? Note that |
Interesting corner case. I need to dig deeper into the code that reports the error. |
This happens with VS 2022 ( 17.11.1 version).
I have a solution, that will throw me Null Reference Exception because I'm using Global Usings. Here's the stack trace:
The workaround that I can have is that I stop using global usings. Eg: I remove the GlobalUsings.cs file that contains the following two lines of code
And the problem goes away.
But the problem is that when I try to create a scale down project, I can't reproduce the error. I thought it's a simple case of using extern alias with global using, but I was wrong.
I am pretty sure that this is a bug from Rosyln compiler. Any idea how to reproduce an actionable bug report?
The text was updated successfully, but these errors were encountered: