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

Roslyn extensions gotten by PackageReference is not working. #1536

Closed
itn3000 opened this issue Jun 1, 2017 · 3 comments
Closed

Roslyn extensions gotten by PackageReference is not working. #1536

itn3000 opened this issue Jun 1, 2017 · 3 comments

Comments

@itn3000
Copy link

itn3000 commented Jun 1, 2017

Environment data

dotnet --info output:

.NET Command Line Tools (2.0.0-preview1-005977)

Product Information:
 Version:            2.0.0-preview1-005977
 Commit SHA-1 hash:  414cab8a0b

Runtime Environment:
 OS Name:     Windows
 OS Version:  6.3.9600
 OS Platform: Windows
 RID:         win81-x64
 Base Path:   C:\Program Files\dotnet\sdk\2.0.0-preview1-005977\

Microsoft .NET Core Shared Framework Host

  Version  : 2.0.0-preview1-002111-00
  Build    : 1ff021936263d492539399688f46fd3827169983

VS Code version: 1.12.2
C# Extension version: 1.10.0

Steps to reproduce

  1. create console project by dotnet new
  2. add ClrHeapAllocationAnalyzer(https://www.nuget.org/packages/ClrHeapAllocationAnalyzer/) to PackageReference
  3. open the project folder by vscode
  4. Open Program.cs and add object x = 0; in Main method
  5. save it

Expected behavior

following warning is displayed in problems(quoted from dotnet build output).

warning HeapAnalyzerBoxingRule: Value type to reference type conversion causes boxing at call site (here), and unboxing at the callee-site. Consider using generics if applicable 

Actual behavior

no warning displayed in problem.

@DustinCampbell
Copy link
Member

Unfortunately, we don't support analyzers today. This is being tracked by #43.

@itn3000
Copy link
Author

itn3000 commented Jun 2, 2017

Oh, sorry for creating duplicated issue.
I hope it would be supported.

@DustinCampbell
Copy link
Member

It's not a problem at all! We do hope to get to this eventually. Note that analyzers should still run and return errors during build.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants