-
Notifications
You must be signed in to change notification settings - Fork 389
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
RoslynDev hive doesn't work as expected after running build.cmd #2463
Comments
@jcouv This must have been broken, let me investigate... |
For the rules to take effect some env vars need to be set. For that - you need to F5 from VS (launchSettings.json sets them) or we need build.cmd to set them. |
@srivatsn Ah, the rules...may be we need a launch that sets it. Having the build set it seems wrong. |
We should create a batch file and update the contribution guide |
Note that the current root suffix is |
I updated the contribution guide instead of adding a command-line batch script. It's just a couple of environment variables. |
@davkean what was the doc change? I have a feeling I'm missing some step to update the extensions my RoslynDev instance is using. I'm on dev16.0 branch with my changes applied to it (some parser and lexer experiments I'm doing). I cleaned my git repo. I removed the RoslynDev folder from AppData. For some reason I'm still using a version of the compiler with SOME of the changes I did. I managed to try out my changes in this experimental instance a week ago but now I can't get the RoslynDev to use the latest version of my binaries. Please help |
@DominikDitoIvosevic This is the project-system, Roslyn's contribution guide is here: https://github.com/dotnet/roslyn/wiki/Contributing-Code. |
From discussion with @panopticoncentral, running
build.cmd
is not sufficient to properly set up project system for testing in hive.This came up in the context of validating the ref assembly change for FUTD check. My setup was incorrect.
The contribution guide should be updated, or
build.cmd
should be fixed:Relates to #2254 (comment)
The text was updated successfully, but these errors were encountered: