search

aspnet / Tooling

Issue tracker and info on Visual Studio tooling for ASP.NET
Other
256 stars 124 forks source link

No validation/assistance provided when adding new External Web Tools path #281

Open scottaddie opened 8 years ago

scottaddie commented 8 years ago

When adding a new external tools location via the Tools --> Options --> Projects and Solutions --> External Web Tools interface, there is no validity checking. In the attached screenshot, I was able to add a folder path which does not exist. I would expect some sort of validation to occur. At the very least, I would expect validation on the variables being used here. In the screenshot, I referenced something called $(ThisDoesNotExist), which should not be allowed.

external_web_tools

One way to mitigate this problem may be to provide a Macros button similar to that provided in the Build Events dialog:

build_event_dialog

BillHiebert commented 8 years ago

@madskristensen @jodavis

sayedihashimi commented 8 years ago

TFS: 168932 I've added this to our internal TFS, we will reply back here soon.

webtools-bot commented 7 years ago

The GitHub Issue Tracker for the aspnet/Tooling repo is being deprecated in favor of Visual Studio's Report a Problem tool.

If this issue is still a problem with the RTW release of Visual Studio 2017, please report a new issue using the Report a Problem tool. While you can still use .NET Core and ASP.NET Preview tools with Visual Studio 2015, Visual Studio 2017 is now the officially supported tool for developing .NET Core and ASP.NET Core projects.

By using the Report a Problem tool (available in both VS 2017 and VS 2015), you can collect detailed information about the problem, and send it to Microsoft with just a few button clicks. See Visual Studio's Talk to Us page for more details.

Please use the discussion topic here for feedback and questions on the deprecation of this issue tracker. Thanks!