-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Support for read only source trees #887
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
Comments
19 tasks
Put a For more info, see #802, #803, #867, and dotnet/msbuild#1603. |
Love it. Thanks! |
mmitche
pushed a commit
to mmitche/sdk
that referenced
this issue
Jun 5, 2020
…0190819.1 (dotnet#887) - Microsoft.AspNetCore.Mvc.Analyzers - 3.0.0-preview9.19419.1 - Microsoft.AspNetCore.Mvc.Api.Analyzers - 3.0.0-preview9.19419.1 - Microsoft.AspNetCore.Analyzers - 3.0.0-preview9.19419.1 - Microsoft.AspNetCore.Components.Analyzers - 3.0.0-preview9.19419.1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The dotnet sdk projects seem to assume the obj directory under a project as the intermediate directory. This is very unpopular for advocates of read only source trees. The ReadOnlySourceTree NuGet package fixes this for VS2015 style projects just by installing the package. But this needs to be revamped for .NET SDK projects, and in fact I wonder if it can even be effective since package restore itself creates the obj directory at the old location, so once the package is restored and diverts the obj directory to another place, the project.assets.json file won't be where it is expected to be.
So what is the plan for supporting read only source trees?
The text was updated successfully, but these errors were encountered: