Closed Tony20221 closed 5 months ago
The samples are published using the standard dotnet publish
command. The publish output will contain a directory named browserextension
, which is where you can load the extension into Chrome.
I have not tried publishing using VS, but I suspect that it will be calling to the same command for publishing new .Net projects, so the output should be the same.
The dotnet publish command worked. It seems publishing within VS works differently.
How did the sample extensions get published to the browserextension folders?
If I publish in Visual Studio where the destination is ../dist\, VS creates a wwwroot folder under the dist folder with subfolder names _content & _framework and Chrome refuses to load an extension from folders that start with an underscore.