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

Support Roslyn analysers (included CodeCracker) #8

Closed
laedit opened this issue Feb 10, 2015 · 1 comment
Closed

Support Roslyn analysers (included CodeCracker) #8

laedit opened this issue Feb 10, 2015 · 1 comment
Milestone

Comments

@laedit
Copy link
Owner

laedit commented Feb 10, 2015

Not possible right now, the tool doesn't produce any xml file.
Final issue in Roslyn: #430

@laedit laedit removed the invalid label Jan 28, 2016
@laedit laedit changed the title Support CodeCracker Support Roslyn analyzers (included CodeCracker) Aug 26, 2016
@laedit laedit changed the title Support Roslyn analyzers (included CodeCracker) Support Roslyn analysers (included CodeCracker) Aug 26, 2016
@laedit
Copy link
Owner Author

laedit commented Aug 26, 2016

Now Roslyn analysers produces SARIF files with the <ErrorLog>report.json</ErrorLog> switch.
How to accomplish common tasks with the SARIF SDK

@laedit laedit added this to the 0.2.0 milestone Aug 30, 2016
@laedit laedit closed this as completed in 124bdf9 Sep 1, 2016
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

1 participant