I've been using #JetBrainsRider off and on for the past few days. I am starting to figure out where everything is, and I see why people like it.
Clean, spare UI that appears to support all the project types used in #cslanet (which is nearly all of them), with lots of dev productivity helpers (some of which I'm finding annoying, but will probably appreciate over time).
Is there any way to create/maintain a unique user id value for #blazor that goes across server-static and server-interactive pages? Other than a cookie, because that's too broad - I want something that is more per-tab than per-browser.
Why is it that almost 100% of the time when I go to create or use a #dotnet#dotnetmaui project in #visualstudio that it just fails to build for random reasons - like being unable to find the right #nuget packages or some other obscure b.s. that requires lengthy searching and trial-and-error to maybe fix?
Basically, my experience with #dotnetmaui almost always sucks.
@rockylhotka this is going to be tricky, .NET 6 MAUI is out of support so I don’t know how you could build 6 and 8 together, you can only target 7 and 8 in a supported fashion. The general issue sounds like .NET workloads though…
@jonathanpeppers@rockylhotka the latest SDK is supposed to be backwards compatible so you can try setting global.json to 8 and reinstalling the workloads from that same directory (that will use the latest SDK and install the workloads into that band)
My phone is glitching so I’m truly using my iPad for the first time ever. I need to say that it isn’t fantastic.very inconsistent experiences between apps and other apps. And #safari! Omg it sucks! Especially with #pwa apps, but generally quite poor compared to anything chromium based.
I now have a #dotnet#blazor app that is able to maintain per-user state across server-rendered, server-interactive, and wasm-interactive pages in a single app. It still needs some refinement, but at least the concept is proven to work!
I put together a rough solution to flowing per-user state between pages using the different #blazor render modes in #dotnet 8. It isn't perfect, and maybe folks can provide better answers, but I wanted to at least provide a straw man solution.
One of the hardest parts of putting together a decent sample for #cslanet is talking to a database (or remote service endpoint). It isn't like someone can just download the repo, load the project, and run. They have to set up a bunch of infrastructure (server, db server, db itself).
This #devcontainer idea seems like the solution. Provide a pre-built container with all the infra set up so someone can just run the container and see everything in action with no effort.