Blazor SS and ApplicationContext DI weirdness and feedback #2760
-
|
@rockfordlhotka @TheCakeMonster It might help me test if you could spare a few minutes to put out one more pre-release of CSLA 6. That would help me rule out any errors in my creation of local nuget packages. I will gladly test against that and report back what I find. It seems I might be one of the few testing a Blazor SS (only) project, but it's turning up interesting things. I'm testing your latest changes. The project has no reference to Here is the relevant line in program.cs: I did the following:
When I hit the following line "Portal = ..." : public class BetaInfoListFactory : DemoReadOnlyListBaseFactory<BetaInfoList, BetaInfo>
{
public BetaInfoListFactory(Csla.IDataPortalFactory dpFactory, ApplicationContext applicationContext)
{
Portal = dpFactory.GetPortal<BetaInfoList>();
...I get this error: Issue/Question 1: Issue/Question 2: Issue/Question 3: Minor Issue 4:
Suggestion 5: |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 7 replies
-
|
For server-side Blazor you will be required to reference the As I'm updating the Blazor sample app I'm fixing some bugs in the configuration API. Possibly regressions, but still, bugs. Good idea about a server-side Blazor example to go with the existing Blazor wasm one. I will push another prerelease once I have at least a couple of the sample apps running. No sense pushing it now, as I know there are bugs that I'm actively fixing. |
Beta Was this translation helpful? Give feedback.
-
|
I'm pretty sure this is the cause of one of your issues 😳 |
Beta Was this translation helpful? Give feedback.
-
|
Looking at your Blazor sample, I saw the |
Beta Was this translation helpful? Give feedback.
-
|
DUHHH I see it now...I should have expanded the |
Beta Was this translation helpful? Give feedback.
-
|
I can't help but keep thinking there is a design issue here that is causing friction (maybe just a fact of life). If user is building Blazor WASM then all is well...the packages match and support what is expected (Csla.Blazor.WebAssembly package is dependent on Csla.Blazor) But if user is doing Blazor.Server, they must have insider knowledge that Csla.AspNetCore is needed. Almost seems like we are missing a Csla.Blazor.Server and a Common. So? While I'm offering arm-chair-quarterback free advice... Csla.Blazor.Server Csla.Blazor.WebAssembly No need to respond...this is either totally dumb or the best idea ever and I trust you to recognize which :-) |
Beta Was this translation helpful? Give feedback.
-
|
The way I think about it is:
This generally follows the model Microsoft has provided for these technologies. |
Beta Was this translation helpful? Give feedback.
-
|
Totally agree functionally (now that I’ve learned about how it all works).
Indeed a true Blazor SS app STILL has .cshtml pages _Host and _Layout etc
for initial hookup at least.
Just was trying to think of a way to get the naming to be easiest to
understand and for the prerequisites to automatically match while avoiding
the reference issues that currently stop Cala.AspNetCore from being a
prerequisite of Cala.Server. Maybe it was just me but the way it is now
was not intuitive for me and I had the impression that adding
Csla.AspNetCore was adding unnecessary stuff.
But perhaps clear documentation and the BSS only sample would sufficiently
help those that come later over the years.
…On Thu, Feb 10, 2022 at 12:11 PM Rockford Lhotka ***@***.***> wrote:
The way I think about it is:
1. If you are running in aspnetcore (for any reason), then you need
the Csla.AspNetCore package
2. If you are building a Blazor app (of any sort), then you need the
Csla.Blazor package
3. If you are building a Blazor wasm app, then you need the
Csla.Blazor.WebAssembly package
This generally follows the model Microsoft has provided for these
technologies.
—
Reply to this email directly, view it on GitHub
<#2760 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABUM5P6FR2Q7AHTES6K3ZEDU2QEWXANCNFSM5N55BPIQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
For server-side Blazor you will be required to reference the
Csla.AspNetCoreandCsla.Blazorpackages. I had to put the authorization types intoCsla.AspNetCorebecause they rely on types that aren't referenced byCsla.Blazor(and can't be, because it is also used in Blazor wasm).As I'm updating the Blazor sample app I'm fixing some bugs in the configuration API. Possibly regressions, but still, bugs.
Good idea about a server-side Blazor example to go with the existing Blazor wasm one.
I will push another prerelease once I have at least a couple of the sample apps running. No sense pushing it now, as I know there are bugs that I'm actively fixing.