aspnet / RazorTooling

Razor tooling for Visual Studio 2015

aspnet/RazorTooling Issues

IRazorViewEngine does not pick updated cshtml
Closed 6 years ago6
how can i use taghelper IntelliSense for a aspnet core library project?
Closed 7 years ago5
Non-string taghelper attribute value containing @@ is not recognized as code
Closed 7 years ago3
Intellisense from output folder
Closed 7 years ago5
Add tests that target the latest version of Razor.Runtime
Closed 7 years ago1
Remove ViewComponent tag helper workaround when VS packages are updated
Closed 7 years ago6
Razor Tag Intellisense disappears
Closed 7 years ago4
Upgrade to VS 2017
Closed 7 years ago3
Add DotnetCliTool package type.
Closed 7 years ago1
Views names are Case-Sensitive when precompiled but not at development time.
Closed 7 years ago1
Question: Can I View Generated Source From Precompiled Views?
Closed 7 years ago1
Bundle deps.json to future proof RazorTooling
Closed 7 years ago5
internal methods are not detected as internal and end up as runtime compile errors
Closed 7 years ago4
Msbuildify tools
Closed 8 years ago1
Depend on 1.0.0-* version of Razor.Runtime instead of 1.1.0-*
Closed 8 years ago1
*.cshtml files do not update without building project
Closed 8 years ago19
Restore fails on CI test
Closed 8 years ago4
Create end-to-end functional test to validate dotnet-razor-tooling functionality.
Closed 8 years ago3
TagHelper with no end tag: parsing issues
Closed 8 years ago3
Separate inside man functionality into its own package.
Closed 8 years ago2
CreateLoadContext doesn't accept command line configuration value.
Closed 8 years ago1
Incorrect colorization and stalled parsing after line movement.
Closed 8 years ago5
Clean up package metadata and pre-Core references
Closed 8 years ago1
Enable RazorTooling to resolve TagHelpers for non-desktop, package assemblies.
Closed 8 years ago4
dotnet-razor-tooling.exe cannot be invoked with 32bit dotnet.exe
Closed 8 years ago1
Dispatch does not handle multiple assembly name arguments.
Closed 8 years ago1
Support .NET Framework-only projects
Closed 8 years ago2
Change RazorTooling to target netcoreapp1.0
Closed 8 years ago1
Add ability to specify if TagHelperDescriptors should be resolved in design time or runtime.
Closed 8 years ago3
Add ability to specify output path when looking for TagHelper assemblies.
Closed 8 years ago2
Pasting bad code over bad code crashes VS
Closed 8 years ago4
Consume first TFM when resolving TagHelperDescriptors.
Closed 8 years ago1
Transition to new Dotnet CLI tooling format.
Closed 8 years ago1
Change to build to use dotnet
Closed 8 years ago
Move from using `IAssemblyLoadContext` => `AssemblyLoadContext`
Closed 8 years ago3
Refactor code to enable testing on CoreCLR
Closed 8 years ago2
Change TagHelperDescriptor resolution to be invoked via a Program.Main.
Closed 8 years ago2
TagHelpers documentation is not loaded if project is a part of a solution
Closed 8 years ago2
resolve-taghelper performance issue
Closed 8 years ago4
Cannot determine TagHelperDescriptors for dnx46 projects.
Closed 9 years ago2
Remove `-protocol` command line argument.
Closed 9 years ago3
Add VisualStudio Compatibility test to validate serialization/deserialization of data doesn't break.
Closed 9 years ago1
When opening a solution, TagHelpers are not lit up for cshtml files previously opened.
Closed 9 years ago4
TagHelper tooling does not work with pre-compilation enabled.
Closed 9 years ago5
Cannot resolve TagHelperDescriptors for CoreCLR only projects.
Closed 9 years ago1
Notify editor when TagHelper assemblies have changed.
Closed 9 years ago1
Transition test projects to use Razor test source comparers.
Closed 9 years ago1
Double double-quote is added when adding quotes to a non-quoted bound item at the end of a line
Closed 9 years ago3
VS2015 RTM insta-crash in Razor editor while using custom tag helper
Closed 9 years ago11
Add Protocol
Closed 9 years ago1