Uninvited guest 'Csla.Blazor.WebAssembly.dll' is showing up to my Blazor Server Side party

[swegele]

1. Create a new Blazor SS project in VS 2022 (no auth)
2. Reference these two nuget packages (Csla.Blazor and Csla.AspNetCore)
   choose latest version '6.0.0-R22020902'
3. Build the solution
   Notice the "Csla.Blazor.WebAssembly.dll" in the bin directory. Why is it there?

That WebAssembly.dll being there by default is causing Csla to use the Csla.Blazor.WebAssembly.ApplicationContextManager

If I delete that dll, then Csla properly uses the Csla.AspNetCore.ApplicationContextManager. Every code-change/build puts that dll back again.

[swegele]

I see that the Package Csla.Blazor (6.0.0-R22020902) has the following in it's "Compile Time Assemblies":

• Csla.Blazor.dll
• Csla.Blazor.WebAssembly.dll

Tail wagging the dog?

Also, when I delete the Csla.Blazor.WebAssembly.dll so that Csla properly tries to use the Csla.AspNetCore.ApplicationContextManager, I get an error with service registration:
InvalidOperationException: Unable to resolve service for type 'Csla.AspNetCore.Blazor.ActiveCircuitState' while attempting to activate 'Csla.AspNetCore.ApplicationContextManager'.

I have to manually add this to my program.cs to get past that error:
builder.Services.AddScoped<Csla.AspNetCore.Blazor.ActiveCircuitState>();

[rockfordlhotka]

I just looked at the code, and this type is registered, along with the circuit handler type. You need to call the AddAspNetCore method within the AddCsla configuration though.

csla/Source/Csla.AspNetCore/ConfigurationExtensions.cs

Line 39 in abc7d5b

public static CslaOptions AddAspNetCore(this CslaOptions config, Action<AspNetCoreConfigurationOptions> options)

[rockfordlhotka]

You are right - the nuspec file has (had) a bug that included the .WebAssembly files where they aren't wanted.