-
Notifications
You must be signed in to change notification settings - Fork 74
Dotnet watch doesn't run with certain references #136
Comments
Can you |
Jup, that's the odd bit. See logs:
|
What dotnet version do you use? ( |
1.0.0-preview2-003121 |
Dank je wel :) The project and everything looks fine. I'll try to reproduce here with your project later today. I'll keep you updated. |
Alsjeblieft 😉 Just a thought, it could be related to the fact that running dotnet restore doesn't work on command line ( Just for your info, the restore.dg file which also shows the folder/csproj structure:
|
Ohhhh that might explain a lot. I don't think there was a lot of testing with xproj -> csproj reference and |
I got it replicated. Locally this commit shows exactly the same behavior as above. |
Indeed, it seems to be a problem with csproj files. We'll fix it |
Pushed a PR to fix this. Unfortunately, |
@victorhurdugaci super, thanks! Is the not-monitoring csprojs going to change when .net core moves back to csproj? And is this going to land in the August release (https://blogs.msdn.microsoft.com/dotnet/2016/07/15/net-core-roadmap/)? On a slightly different note, do tools like this (by the asp.net team) actually follow the normal release schedule, or could a release be cut whenever the tool itself is on a next version, according to the maintainers? |
Hi, just wanted to check in. Does .csproj still not support dotnet watch? I'm running into trouble like @janpieterz above. dotnet run works fine but for the life of me i can't get dotnet watch run to go. It just died with |
We have a preview available. Install 1.0.0-msbuild3-final. <ItemGroup>
<DotNetCliToolReference Include="Microsoft.DotNet.Watcher.Tools" Version="1.0.0-msbuild3-final" />
</ItemGroup> FYI any version labeled "preview" is a project.json-only version. We realize this is goofy, but it's temporary. When we release the 1.0.0 version in March along with VS 2017, it won't support project.json. |
I have been unable to pinpoint exactly which is erroring, but it seems to be related to certain project references.
dotnet run
works fine, and I have tried all kinds of things with the references projects, lock files, restores and what not. Reason I'm thinking this is a referencing issue is because in other projects it works fine that have less or different references (local project references). It fails reliably every time ;)Error given:
Project.Json:
The text was updated successfully, but these errors were encountered: