After Upgrading to to 0.23: WebAssembly error - Unhandled exception rendering component: Cannot read properties of null (reading 'insertBefore') about bolero HOT 15 CLOSED

Thanks for the report! Just to make sure: are you using v0.23.43? The earlier v0.23.41 is known to be faulty.

from bolero.

To verify the error report, I did

dotnet new update
dotnet new bolero-app -o Bolero
dotnet build

and got

MSBuild version 17.5.1+f6fdcf537 for .NET
  Determining projects to restore...
D:\fsharp\projects\div\Bolero\src\Bolero.Server\Bolero.Server.fsproj : error NU1108: Cycle detected.  [D:\fsharp\projects\div\Bolero\Bolero.sln]
D:\fsharp\projects\div\Bolero\src\Bolero.Server\Bolero.Server.fsproj : error NU1108:   Bolero.Server -> Bolero.Server (>= 0.0.0). [D:\fsharp\projects\div\B
olero\Bolero.sln]
  Failed to restore D:\fsharp\projects\div\Bolero\src\Bolero.Server\Bolero.Server.fsproj (in 1.23 sec).
  Restored D:\fsharp\projects\div\Bolero\src\Bolero.Client\Bolero.Client.fsproj (in 1.23 sec).

I am not sure if that is in any way related to the above. I should also mention I have .net 8 installed.

from bolero.

It also seems that -s=false is no longer respected.

Running dotnet new bolero-app --server=false -o Bolero -v diag actually shows a line [2023-11-03 09:58:49.670] [Debug] [Template Engine] => [Execute] => [Template content generation]: [JoinMacro]: Variable 'server{-VALUE-FORMS-}identity' was assigned to value 'False'. but then creates the server files.

from bolero.

Ah, I think I know why this second issue happens -- I probably forgot to apply the fix for fsbolero/Template#41 in the template definition file. I'll fix it quickly.

Edit: reported here: fsbolero/Template#43

from bolero.

To verify the error report, I did

dotnet new update
dotnet new bolero-app -o Bolero
dotnet build

and got

MSBuild version 17.5.1+f6fdcf537 for .NET
  Determining projects to restore...
D:\fsharp\projects\div\Bolero\src\Bolero.Server\Bolero.Server.fsproj : error NU1108: Cycle detected.  [D:\fsharp\projects\div\Bolero\Bolero.sln]
D:\fsharp\projects\div\Bolero\src\Bolero.Server\Bolero.Server.fsproj : error NU1108:   Bolero.Server -> Bolero.Server (>= 0.0.0). [D:\fsharp\projects\div\B
olero\Bolero.sln]
  Failed to restore D:\fsharp\projects\div\Bolero\src\Bolero.Server\Bolero.Server.fsproj (in 1.23 sec).
  Restored D:\fsharp\projects\div\Bolero\src\Bolero.Client\Bolero.Client.fsproj (in 1.23 sec).

I am not sure if that is in any way related to the above. I should also mention I have .net 8 installed.

Ah, and actually I think the problem here is that since you named your project "Bolero", the server-side project is named "Bolero.Server", which is the same as the NuGet package. So there is an ambiguity. If you name your project something else, this specific issue should not happen.

from bolero.

Regarding your initial issue, can you clean your project (delete obj and bin directories) and try again? I think I've seen this error with projects that were mixing different versions of dependencies due to old files remaining.

from bolero.

Oh I see that you actually get this from a new project. Which .NET SDK version are you using?

from bolero.

Thanks for the responses. Client-only projects now run fine (with the new template and a new name).
For client+server I get rendering issues similar to those that @kgday posted initially in this thread.

crit: Microsoft.AspNetCore.Components.WebAssembly.Rendering.WebAssemblyRenderer[100]
      Unhandled exception rendering component: t.parentNode is null
      x@http://localhost:5000/_framework/blazor.webassembly.js:1:17112
      insertElement@http://localhost:5000/_framework
...

I have the 8.0.100-rc.1.23463.5 SDK.

from bolero.

I just recreated and tested the project with RC2, same result.
Also tested with global.json .net7, same result.

from bolero.

Just started seeing this issue also. Happens on a basic template-generated client/server project (created a month or so ago).

Deleted the bin and obj dirs and it still happens

Using: Windows / .net7 / Edge

Setting the versions to 0.22.* for Bolero fixes this issue

Note: Client only project seems to be ok

from bolero.

Thanks everyone, I can reproduce the issue. It seems specific to hosted webassembly projects; client-only works, as mentioned, and server mode (AddBoleroHost(server = true)) works too.

from bolero.

I just published Bolero 0.23.44 which should fix this issue. Can you confirm?

from bolero.

Yes, works fine now. Thanks!

from bolero.

Confirmed it works. Thank you very much for your hard efforts.

from bolero.

+1 - thanks

from bolero.