Ming Yau Lee

Hi! I am aware of the deprecation of manifest V2 in chrome store. I do plan to add support for manifest V3 as soon as I can. There were a...

I will use this issue to track the progress of migrating to manifest v3. Blockers: 1. [Wasm cannot be loaded in manifest v3](https://bugs.chromium.org/p/chromium/issues/detail?id=1173354) - Potential workaround 1: compile to single...

Update: Bug [Wasm cannot be loaded in manifest v3](https://bugs.chromium.org/p/chromium/issues/detail?id=1173354) is fixed and will likely be released in Chrome version 102.

Tested with Chrome Dev channel, manifest v3 can be loaded but Blazor cannot be initialized due to the requirement of 'unsafe-eval' CSP in dotnet runtime, which is resolved and targeted...

Update: Blockers: 1. ~~[Wasm cannot be loaded in manifest v3](https://bugs.chromium.org/p/chromium/issues/detail?id=1173354)~~ - Fixed in Chrome 102, tested in Chrome Dev channel 2. [Dynamic import is not allowed in service workers](https://bugs.chromium.org/p/chromium/issues/detail?id=1198822) -...

@gitlsl .Net 7和Blazor还没有解决CSP的问题。一旦解决了还需要再测试能否用MV3来启动Blazor。

The issue in [dotnet/runtime#68374](https://github.com/dotnet/runtime/issues/68374) is still open. Dotnet runtime still requires `unsafe-eval` CSP directive which is not allowed in MV3.

Good news! Manifest V3 is now supported, with .Net 7 RC1 released. Please read on this in the project README, migration guide is provided. Any problem should be reported as...

Visual Studio requires the build tasks to target net472

I guess to quote from [this page](https://learn.microsoft.com/en-us/visualstudio/msbuild/tutorial-custom-task-code-generation?view=vs-2022#create-the-appsettingstronglytyped-project), > - Full MSBuild: This version of MSBuild usually lives inside Visual Studio. Runs on .NET Framework. Visual Studio uses this when you...