You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 11, 2020. It is now read-only.
When i'm trying to run as custom tool the plugin Razor Generator (https://github.com/RazorGenerator/RazorGenerator) in Visual Studio 2017 in a cshtml file, within a .net standard console project, i'm getting the error message "Error to save the edited properties enumerated to continuation. Custom Tool. One or more values are not valid. Internal error."
The text was updated successfully, but these errors were encountered:
Yeah. The best "solution" i found is to install the package RazorGenerator.MsBuild and don't configure the custom tool. The project compile without problems and in compilation time, the cshtml is transpiled to cs. But, in the error window in Visual Studio, appears errors that dont affects compilation. It's all.
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.
I'd recommend logging an issue over at the RazorGenerator repo. Sadly it's not an officially supported project, some team members just developed it in their spare time 😄.
When i'm trying to run as custom tool the plugin Razor Generator (https://github.com/RazorGenerator/RazorGenerator) in Visual Studio 2017 in a cshtml file, within a .net standard console project, i'm getting the error message "Error to save the edited properties enumerated to continuation. Custom Tool. One or more values are not valid. Internal error."
The text was updated successfully, but these errors were encountered: