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.

Sign up for GitHub

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

Jump to bottom

Use of IntermediateOutputPath for NativeRuntimeEventSource.cs inhibits VS experience with Corelib #13231

Closed
stephentoub opened this issue Aug 8, 2019 · 0 comments · Fixed by dotnet/coreclr#26076
Closed

Use of IntermediateOutputPath for NativeRuntimeEventSource.cs inhibits VS experience with Corelib #13231

stephentoub opened this issue Aug 8, 2019 · 0 comments · Fixed by dotnet/coreclr#26076
Labels
area-Diagnostics-coreclr

Comments

@stephentoub
Copy link
Member

The use of:

<Compile Include="$(IntermediateOutputPath)../Eventing/NativeRuntimeEventSource.cs" Condition="'$(FeaturePerfTracing)' == 'true'" />

in System.Private.CoreLib.csproj breaks the VS experience for working with Corelib. VS can't compile the assembly, as that file doesn't exist, and thus many experiences, like analyzers that run during a build, don't work.
@msftgits msftgits transferred this issue from dotnet/coreclr Jan 31, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Dec 12, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area-Diagnostics-coreclr
Projects
None yet
Milestone
No milestone
1 participant
@stephentoub