This repository has been archived by the owner on Feb 23, 2021. It is now read-only.
Consume first TFM when resolving TagHelperDescriptors. #49
Comments
NTaylorMullen
added a commit
that referenced
this issue
Mar 9, 2016
- This makes RazorTooling consistent with the .cshtml editor. - Added `project.json` tests to validate new behavior of throwing an appropriate error/selecting the first TFM. #49
NTaylorMullen
added a commit
that referenced
this issue
Mar 9, 2016
- This makes RazorTooling consistent with the .cshtml editor. - Added `project.json` tests to validate new behavior of throwing an appropriate error/selecting the first TFM. #49
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Today we have the ability to specify a TFM when resolving
TagHelperDescriptors. The problem with this approach is that the Razor editor does not have this capability. Instead it always picks the first TFM when showcasing C# intellisense.A second part of what we currently do today is if a user has a
project.jsonfile with a TFM such asnetstandardapp1.5theTargetFrameworkidentifier according to the dotnet project model loader is.NETStandardApp. This means we'd either need to query them for a set of names for the associated TFM or hardcode a set of name. Neither is great.Lets do what the .cshtml editor does today for consistency and consume the first TFM present so you don't get any odd artifacts in your cshtml.
The text was updated successfully, but these errors were encountered: