aspnetcore

Go to file

N. Taylor Mullen 96475e488d Render more TagHelper code at design time. - This is a pre-requisite to properly warnings users about TagHelpers in code blocks. With this change VS indicates that there's an asynchronous operation happening in a code block but because the code is auto-generated it happens behind the scenes and therefore always gets logged as a line 1 error (unusable). Therefore, to fix this issue there will be a partner PR that will go out in AspNetCore that adds analyzer errors for cases where `__tagHelperRunner.RunAsync` exists in code blocks that do not return `Task` and are not marked with `async` properly. - Updated test files to reflect the new TagHelper codegen at design time. - Note: This doesn't solve the `~/` case that will be in a follow up PR. aspnet/AspNetCoredotnet/aspnetcore-tooling#8630 \n\nCommit migrated from `17af3efccd`	2019-05-17 12:59:32 -07:00
src	Render more TagHelper code at design time.	2019-05-17 12:59:32 -07:00

N. Taylor Mullen 96475e488d Render more TagHelper code at design time.

- This is a pre-requisite to properly warnings users about TagHelpers in code blocks. With this change VS indicates that there's an asynchronous operation happening in a code block but because the code is auto-generated it happens behind the scenes and therefore always gets logged as a line 1 error (unusable). Therefore, to fix this issue there will be a partner PR that will go out in AspNetCore that adds analyzer errors for cases where `__tagHelperRunner.RunAsync` exists in code blocks that do not return `Task` and are not marked with `async` properly.
- Updated test files to reflect the new TagHelper codegen at design time.
- Note: This doesn't solve the `~/` case that will be in a follow up PR.

aspnet/AspNetCoredotnet/aspnetcore-tooling#8630
\n\nCommit migrated from 17af3efccd

2019-05-17 12:59:32 -07:00

src Render more TagHelper code at design time. 2019-05-17 12:59:32 -07:00