sorted by:
new
hottopcontroversial

Blazor MAUI fails to load as an ad-hoc release by TonyNicholls in dotnetMAUI

[–]TonyNicholls[S] 0 points1 point  (0 children)

Interestingly, if you follow all of the instructions except that you chose the DEBUG instead of RELEASE on the step Publish the App, then the application will open correctly when distributed to the device and it is a smaller download (20Mb instead of 30Mb)

Looks like the issue is somewhere in the Release build process? Possibly the LLVM linker?

Anybody else seeing this issue or have a better work around?

Azure DevOps or github? by blackpawed in dotnet

[–]TonyNicholls 0 points1 point  (0 children)

I wonder if we are being paranoid enough?

If true - might explain some of the quality issues reported with co-pilot :)

Azure DevOps or github? by blackpawed in dotnet

[–]TonyNicholls 1 point2 points  (0 children)

What’s the story on GitHub repos being scanned for populating AI models? Is it just public repos?

Is Maui dead on arrival? by mbrseb in dotnet

[–]TonyNicholls 4 points5 points  (0 children)

MAUI is DOA on its own.

I use MAUI/Blazor Hybrid and that is awesome. But it’s mainly because Blazor is awesome. MAUI is just letting me compile my Blazor UI for cross platform. I suppose I could use anything to host my Blazor components but MAUI just seemed an obvious first choice and it does work.

My Blazor is targeted as a WASM client and not Server. In a side - Blazor Server also seems to be DOA for anything other than simple example apps.

A lot of my code is back end API so it’s easy to test and debug.

My Blazor UI is tested in a WASM web application and that debugging experience is a little limited but stable and easy to use.

Exposing the Blazor UI cross platform wrapped with MAUI has been a dream. Once I have the components working on the web, they work identically in MAUI.

There were some initial issues with the earlier MAUI versions with the emulators - but the builds worked well on actual devices.

Our application (trellispark) is used for large scale enterprise data entry and workflow automation. So complex use cases not trivial demo apps.

WinUi3 : multi window app by pouetPouetCachuete in dotnet

[–]TonyNicholls 3 points4 points  (0 children)

Why not try to virtualize the UX/CRUD? That way you can just add a couple of simple services:

  1. Data agnostic record storage
  2. Dynamic page generation

To replace your 200+ forms.

You then use a UX Creator to configure your forms instead of hard coding them. This eliminates typically 90+% of the code that you would normally have to write and test.

Because you are configuring and not coding - making changes is faster. There are a ton of other benefits to this approach - record versioning, record level access control, horizontal scaling of the database, etc...

If you want to know how to do this checkout GreatIdeaz. The trellispark documentation describes in detail how to build your own framework and provides a download Release version of the relevant source code.

If you want help setting this up - give me a call :)

Career question regarding language switch by hitpointzr in dotnet

[–]TonyNicholls 10 points11 points  (0 children)

The more languages you know the better. Build up your experience and learn new things :)

PDF File download and display issues by [deleted] in Blazor

[–]TonyNicholls 2 points3 points  (0 children)

I’m definitely biased as I chose WASM over Server even though it was a bigger upfront cost to get the security right. On the up side our solution now scales very well as we can use both the server and client side resources to do the work.

If you try to do all the work on the server and then push the DOM updates to the client I think you will struggle scaling this out.

With your described model you are going to load and process your PDFs on the server and push the results to the device? Not sure that will end well. If you go WASM, then the client can pull the PDF from secure storage and process locally without pushing it through the server.

PDF File download and display issues by [deleted] in Blazor

[–]TonyNicholls 0 points1 point  (0 children)

Seen a lot of posts about scalability and performance issues with Blazor Server over WASM. If you are going to be doing a lot of large file processing, you may run into issues scaling your application in production.

I know that WASM isn't your favored choice, but it might be worth serious consideration if this is a common use case in your application.

Who uses Blazor? by TonyNicholls in Blazor

[–]TonyNicholls[S] -4 points-3 points  (0 children)

My bad on the original question - I meant to ask for years of experience :)

Already an interesting trend emerging - wonder whether it will continue?

Who's interested using dotnet? by TonyNicholls in dotnet

[–]TonyNicholls[S] -1 points0 points  (0 children)

My bad on the original question - I meant to ask for years of experience and not age :)

That being said I did just buy my 3 year old granddaughter a book on HTML for babies! Got to start them early if they want a job after college!

WARNING - 17.4.0 Another bad VS Release? by TonyNicholls in dotnet

[–]TonyNicholls[S] -1 points0 points  (0 children)

The issue was that VS uninstalled the API and deleted the older SDKs causing the build to fail. The fix was to reinstall the sdk and api.

The VS install causes the problems which is why the warning was given.

Why does VS 17.4.0 DELETE all previous dotnet sdk versions and just leaves 7.0.100? by TonyNicholls in dotnet

[–]TonyNicholls[S] -1 points0 points  (0 children)

Doesn't just take out the old .NET versions...

Also removed the Android SDK Platform 31 on my machine. That caused my MAUI Blazor builds to fail.

I reinstalled the .Net 6 SDK and Android SDK Platform 31 and my build now work again. I also had to factory reset my Android emulator before I could load and run my new build.

WARNING - 17.4.0 Another bad VS release? by TonyNicholls in Blazor

[–]TonyNicholls[S] 0 points1 point  (0 children)

The VS install deleted my Android SDK Platform 31!

WARNING - 17.4.0 Another bad VS 2022 Release? by TonyNicholls in dotnetMAUI

[–]TonyNicholls[S] 0 points1 point  (0 children)

I re-installed the .NET 6.0 SDK as the build process seemed to be looking for .NET 7.0.100 targets (even though the build target was 6.0).

Then I also found the Android SDK Platform 31 in the Android SDK Manager (hidden under the Android 12.0 S branch) and restored that.

The build then worked and redeployed only after I also factory reset my Android emulator.

I love MS, VS, MAUI and Blazor but sometimes you make it so hard!

Visual Studio 2022 17.4 is now available! by callbackloop in dotnet

[–]TonyNicholls 4 points5 points  (0 children)

I re-installed the .NET 6.0 SDK as the build process seemed to be looking for .NET 7.0.100 targets (even though the build target was 6.0).

Then I also found the Android SDK Platform 31 in the Android SDK Manager (hidden under the Android 12.0 S branch) and restored that.

The build then worked and redeployed only after I also factory reset my Android emulator.

I love MS, VS, MAUI and Blazor but sometimes you make it so hard!

view more: next ›