Pranav K

:watch: for your thoughts

Pulling up random GitHub search for `InstallationTarget`, it seems like listing multiple is the way to go: https://github.com/OlegPanagushin/NFX.HtmlEditor/blob/76a3b93568cc53a012a1a3ffeff654c327f7cad5/NFX.Markup/source.extension.vsixmanifest#L9-L14 That said, I haven't had issues installing it on copy of VS...

Nope. ASP.NET Core support for build time compilation out of the box, which is primarily what this project aims to do.

@aggaton - I'm not sure I fully understand what your issues is here. The output that we produce should be identical to what Razor without precompilation produces.

Do the breakpoints work for regular views? We did some messing around with the paths we produced a long time ago, and I thought that addressed these.

Removing it at this point would be a breaking change and we wouldn't consider it. However, we would be open to moving everything but the reference in to `RazorGenerator.Mvc.Core` that...

Yup, something along those lines.

👋🏽 @davidebbo * The Razor language assemblies target netstandard2.0, so they should be loadable inside VS 2019 which requires .NET 4.8. * .NET Core ships a build-time experience for Razor...

You might have to switch around a bunch of code that assumes that the parser is a CSharp parser (for instance (https://github.com/RazorGenerator/RazorGenerator/blob/master/RazorGenerator.Core.v1/ExportedTransformers/MvcViewTransformer.cs#L71). Also places like these might require switching based...

Feel free to ignore those. The `RazorGenerator.MsBuild` project includes a build task that needs to load these binaries - it's not meant to be references.