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

Develop csc/vbc override tasks for Microsoft.Net.Compilers NuPkg so that NuGet users of Roslyn can use Analyzers at build time (VS2013, or non-Windows) #43

Closed
theoy opened this issue Jan 20, 2015 · 0 comments
Closed

Develop csc/vbc override tasks for Microsoft.Net.Compilers NuPkg so that NuGet users of Roslyn can use Analyzers at build time (VS2013, or non-Windows) #43

theoy opened this issue Jan 20, 2015 · 0 comments
Labels
Area-Analyzers Area-Compilers Concept-Portability The issue deals with portable code (portable libraries, etc.). Feature Request help wanted The issue is "up for grabs" - add a comment if you are interested in working on it Resolution-Not Applicable The issue is not relevant to code in this repo and is not an external issue.
Milestone
Backlog

Comments

@theoy
Copy link
Contributor

theoy commented Jan 20, 2015

Currently, compiler users (even on VS2013) can easily upgrade to Roslyn by referencing the https://www.nuget.org/packages/Microsoft.Net.Compilers NuPkg. If they are staying on C#5/VB11, then they can even get a reasonably cooperative IDE experience.

However, if Microsoft.Net.Compilers included csc/vbc MSBuild tasks, they could also start using Roslyn analyzers as soon as they got the compiler NuGet.

This may be meaningful for customers who are not yet ready to upgrade to VS2015, or also for some NuGet users on Mono/non-Windows. Though we should check on the xbuild support.
@theoy theoy added help wanted The issue is "up for grabs" - add a comment if you are interested in working on it Area-Analyzers Area-Compilers Feature Request labels Jan 20, 2015
@theoy theoy added this to the Up for Grabs milestone Jan 20, 2015
@theoy theoy modified the milestones: Unknown, Up for Grabs Feb 6, 2015
@gafter gafter added the Concept-Portability The issue deals with portable code (portable libraries, etc.). label Feb 25, 2015
@sharwell sharwell added the Resolution-Not Applicable The issue is not relevant to code in this repo and is not an external issue. label Jan 29, 2020
dibarbet added a commit to dibarbet/roslyn that referenced this issue Mar 1, 2023
@dibarbet
Add basic unit test project that runs on CI (dotnet#43)
e4a5599 
* Add basic test project

* Run tests in CI

* spacing

* feedback
@allisonchou allisonchou mentioned this issue Jun 16, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area-Analyzers Area-Compilers Concept-Portability The issue deals with portable code (portable libraries, etc.). Feature Request help wanted The issue is "up for grabs" - add a comment if you are interested in working on it Resolution-Not Applicable The issue is not relevant to code in this repo and is not an external issue.
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
3 participants
@sharwell @gafter @theoy