Closed RehanSaeed closed 6 years ago
To report new issues, use the Report a Problem tool. The GitHub Issue Tracker for the aspnet/Tooling repo is now deprecated in favor of the Report a Problem tool.
If you encounter a problem with Visual Studio, we want to know about it so that we can diagnose and fix it. By using the Report a Problem tool, you can collect detailed information about the problem, and send it to Microsoft with just a few button clicks. See here for more details.
Adding @BillHiebert, @abpiskunov and @balachir as FYI.
Posted to the 'Report a Problem' tool with the same title as this issue.
@RehanSaeed to address your question in the previous thread:
Is there a way to make the working directory more generic? Having to hard code a path in there is sub-optimal.
You can use "workingDirectory": "$(ProjectDir)",
I used to be able to use
dotnet watch
in Visual Studio by adding the following section tolaunchSettings.json
and starting the project without debugging using CTRL + F5.This used to work in ASP.NET Core 1.1 but no longer does. According to https://github.com/aspnet/DotNetTools/issues/404 the new format for ASP.NET Core 2.0 is:
The problem with this is the hard coded
executablePath
which is Windows specific and theworkingDirectory
which is specific to wherever I did a Git clone on my local machine.