Skip to content

When looking up the async entry point also look for "<Main>$"#29625

Merged
javiercn merged 1 commit intodotnet:mainfrom
lewing:wasm-entrypoint
Jan 26, 2021
Merged

When looking up the async entry point also look for "<Main>$"#29625
javiercn merged 1 commit intodotnet:mainfrom
lewing:wasm-entrypoint

Conversation

@lewing
Copy link
Member

@lewing lewing commented Jan 26, 2021

Look for top level style "<Main>$" in addition to "Main" when looking for an async entry point.

Fixes dotnet/runtime#47404 for blazor

/cc @javiercn

@lewing lewing requested a review from a team as a code owner January 26, 2021 15:07
@ghost ghost added the area-blazor Includes: Blazor, Razor Components label Jan 26, 2021
@lewing lewing requested a review from javiercn January 26, 2021 15:08
@lewing
Copy link
Member Author

lewing commented Jan 26, 2021

Longer term I'd like to have a discussion about going back to sharing more of the startup code but until then this should fix the blazor entry point lookup for toplevel code.

@javiercn
Copy link
Member

@lewing I see know, I'm not very familiar with this part of the code base.

Thanks for the PR!

Yes, sharing code will be ideal. The more we can make Blazor work with the standard/stock runtime initialization code the better.

@javiercn javiercn added the feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly label Jan 26, 2021
Copy link
Member

@javiercn javiercn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area-blazor Includes: Blazor, Razor Components feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Blazor Async Main and Top-Level Statements Seems to Have Issues

2 participants