Skip to content

ASPNet Blazor Wasm Web3 and Winform Replacement WinUI Monolith #510

@Michi0403

Description

@Michi0403

Project Name

TacosPortalOpen

License

Apache2

Contributor

Michael Fleischer

Existing OSS Project?

Yes

Source Code URL

https://github.com/Michi0403/TacosPortalOpen

Project Homepage URL

No response

Project Transfer Signatories

I will submit it via E-Mail, my github mail is different but I will provide both and explain.

Description

After a lot of experience out there in the Dotnet-Framework ERP "Hood", from Compact Framework 3.5- Dotnet8 now, I reinvented the wheel again.

Based on newer dot8 practices and devexpress components (the part of my code is free), I used the blazor components + the free web api components.

So the code is able to explore via a test version.

Over years I was able to cluster Web3 Blazor WASM + ServerInteractive + API (HTTP Audit Log) + Security System (till Frontend and WASM).
Also I was able to bundle all in WebView2, WinUI as Wrapper.

Beside of that there is the telegram datamodel clean reverse engineerd based on API results and use even of signal R and all kinda technics, self written from the guts (and sometimes with help of ChatGPT but not a lot).

I hope it provides the Dotnet World a new hope and eyes on Blazor that we can kick now every Winforms garbage overboard, this debugs flawlessly.

This concept is the proof that winforms and so on is all replaceable by Blazor and WebAssembly and exactly that's the way how it works.

I provide it as is and won't update it anymore, I lost after years power and redeveloped the whole framework under different scenarios in b2b level.

This is just a show case what a whole Application Framework and Use Case, with all parts, can look like in the windows world.

What are you hoping from the foundation

That the way I use blazor as Winforms replacement (and can host it under Windows and Linux publicly, installable and useable even on iPhone, Android and any Device!), also as frontend and backend monolith could be the future of blazor.
Maybe not this project but I am absolutely sure that promoting this way of architecture could lead Blazor and Dotnet in a other direction.

Name

Michael Fleischer

Email

michael.f.1991@gmx.de

GitHub Profile URL

https://github.com/Michi0403

Committers

https://github.com/Michi0403

Discord Ids

No response

Governance Model

Possibly none at all, I see it as showcase and archive.

CLA

  • If already an OSS project, was a Contribution License Agreement in place for contributions accepted?

How does the project check who has signed one?

I tried to hire people and starved alone.

CLA Notification Alias

michael.f.1991@gmx.de

Select the Project Transfer Agreement model

Assignment

Repository Layout

No response

Eligibility Criteria

  • The project is built on the .NET platform and/or creates value within the .NET ecosystem.
  • The project produces source code for distribution to the public at no charge.
  • The project's code is easily discoverable and publicly accessible (preferably on GitHub).
  • The project contains a build script that can produce deployable artifacts that are identical to the official deployable artifacts, with the exception of code signing (Exception may be granted for strong name keys, though strongly encouraged to be committed. Exception relies on OSS signing being in the build script for public builds).
  • When applicable, project must use reproducible build settings in its toolchain.
  • The project uses Source Link.
  • The project uses either embedded PDBs or publish symbol packages to NuGet (if applicable).
  • The project code signs their artifacts as appropriate.
  • The project organization has 2FA enabled. Requiring 2FA must be done as part of onboarding if not already enabled.
  • Libraries that are mandatory dependencies of the project are offered under a standard, permissive open source license which has been approved by the .NET Foundation (exceptions include a dependency that is required by the target platform where no alternative open source dependency is available such as the .NET Framework or a hardware specific library).
  • Committers are bound by a Contributor License Agreement (CLA) and/or are willing to embrace the .NET Foundation's CLA when the project becomes a Member.
  • The copyright ownership of everything that the project produces is clearly defined and documented.
  • The project has a public issue tracker where the status of any defect can be easily obtained.
  • The project has a published Security Policy.
  • The project has a home page which provides high level information about its status and purpose.
  • The project has a public communication channel where community members can engage with maintainers.
  • The project has a publicly available location where members can review and contribute to documentation.

Describe why you are applying for Project Membership.

It's a show case to show how Blazor should be use and how I replaced any winform applications with it as free example...

Infrastructure Requirements Summary

Crossplattform
Dotnet8 (8.0.24)
Devexpress 24.12.14

Additional Notes

I don't expect anything back for this I just want to help the Dotnet Community and if you need to scrape that applications it's fine to me, because that's just a try to promote Blazor as Winform replacement and general hope in the dotnet world.

Metadata

Metadata

Labels

project applicationproject supportUse this label to request support for an existing .NET Foundation project

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions