You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I use /watch, ASP.NET doesn't generate CSS files from *.razor.css files. This also happens when I don't use /watch, but it's occasional.
During a regular electronize start, it seems to happen very randomly. Sometimes when I add a random line of code, it suddenly fixes itself.
First scenario. When i use electronize start /watch
Start Electron Desktop Application...
Arguments:
watch =
node_modules missing in: /tmp/b/obj/Host/node_modules
Start npm install...
npm install
npm WARN deprecated [email protected]: TSLint has been deprecated in favor of ESLint. Please see https://github.com/palantir/tslint/issues/4534 for more information.
added 159 packages, and audited 160 packages in 4s
26 packages are looking for funding
run `npm fund` for details
1 moderate severity vulnerability
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details.
ElectronHostHook handling started...
Invoke electron - in dir: /tmp/b/obj/Host/node_modules/.bin
./electron "../../main.js" --watch=true
Electron Socket IO Port: 8000
Electron Socket started on port 8000 at ::1
ASP.NET Core Watch Port: 8001
stdout: dotnet watch 🔥 Hot reload enabled. For a list of supported edits, see https://aka.ms/dotnet/hot-reload.
💡 Press "Ctrl + R" to restart.
stdout: dotnet watch 🔧 Building...
stdout: Determining projects to restore...
stdout: Restored /tmp/b/b.csproj (in 326 ms).
stdout: b -> /tmp/b/bin/Debug/net8.0/b.dll
stdout: dotnet watch 🚀 Started
stdout: Use Electron Port: 8000
stdout: info: Microsoft.Hosting.Lifetime[14]
Now listening on: http://localhost:8001
stdout: ASP.NET Core host has fully started.
stdout: info: Microsoft.Hosting.Lifetime[0]
Application started. Press Ctrl+C to shut down.
stdout: info: Microsoft.Hosting.Lifetime[0]
Hosting environment: Production
info: Microsoft.Hosting.Lifetime[0]
Content root path: /tmp/b
ASP.NET Core Application connected... global.electronsocket Y7WWNO_O4GcYde1mAAAC 2024-04-18T23:05:00.263Z
stdout: BridgeConnector connected!
stdout: Called Event BrowserWindowCreated - data 1
[82604:0419/010501.271869:ERROR:cert_verify_proc_builtin.cc(677)] CertVerifyProcBuiltin for localhost failed:
----- Certificate i=0 (CN=localhost) -----
ERROR: No matching issuer found
[82639:0419/010501.272261:ERROR:ssl_client_socket_impl.cc(985)] handshake failed; returned -1, SSL error code 1, net_error -202
Second scenario. When i create new / move razor file.
It's very difficult to reproduce this on a new project because it happens 'randomly'. I've simulated how it looks in my main project. Basically, ASP.NET seems to not recognize the .css file when I run electronize start. However, if I open the project using dotnet run, the CSS is loaded.
If I gather more information about the second issue, I will edit it immediately.
Steps to Reproduce first scenario:
Create new Blazor project dotnet new blazor
Electronize it
Run electronize start /watch
The text was updated successfully, but these errors were encountered:
When I use /watch, ASP.NET doesn't generate CSS files from *.razor.css files. This also happens when I don't use /watch, but it's occasional.
During a regular electronize start, it seems to happen very randomly. Sometimes when I add a random line of code, it suddenly fixes itself.
First scenario. When i use
electronize start /watch
Second scenario. When i create new / move razor file.
It's very difficult to reproduce this on a new project because it happens 'randomly'. I've simulated how it looks in my main project. Basically, ASP.NET seems to not recognize the .css file when I run electronize start. However, if I open the project using dotnet run, the CSS is loaded.
If I gather more information about the second issue, I will edit it immediately.
Steps to Reproduce first scenario:
dotnet new blazor
electronize start /watch
The text was updated successfully, but these errors were encountered: