(FRONT) FRONT (2025)

I try to summarize all workable ASP.NET technologies to one repository.

I try to summarize all my workable MS technologies, all my workable ASP.NET skills to one repository (except ASP technology, maybe I will add ASP later) - https://github.com/Alex-1367/AllAspNet.

To be honest, I prefer more advanced programming language - VB.NET, but because VB.NET so fanny, easy to understanding and not support Microsoft global goal - increase price of software, increase Microsoft stock volume, increase the total value of Microsoft shares and pay dividends on Microsoft shares (Why Microsoft vilified Visual Basic ?), Microsoft finally decide to destroy all investments of companies and programmers and finally decide refuse to support own proprietary language VB.NET. Therefore I'm also forced to destroy my highest skills and go down to stupid C# programming. And therefore I made this project on LOL language C#. Why LOL? Because ";" was invented in 18th century and today it looks like trash and an anachronism. Because using ":" to two opposite OOP conception - Inheritance interfaces and Implement existing interfaces with code body, because using the same chars "+" as concatenate string values, accumulate digital values and even adding events to class is more than idiotic trash. Because behind the scenes it performs many forbidden transformations, such as double to integer and back, boxing-unboxing in demand and so on. Because C# can not converted to any other 1-st class languages with strong conception like VB.NET. And plus million other reason.

But increase complexity and price of software is goal of fucking Microsoft company and I'm forced to step back and prepared this repository in less productive and more stupid language - C#.


This project included:

PostgreSQL database, DTO, Repository, Backend API and backend test project.

  1. Full process of PostgreSQL configuring process.



  2. Domain project contains one POCO class what define product records with autogenerated ProductID in PostgreSQL level. Plus This project contains all DTO classes. Because project domain made in NET CORE 8 I can just refer to NET CORE project to that POCO class, but for NET FRAMEWORK class I made duplicate code with the same DTO and Domain classes.

  3. Infrastructure project based on Npgsql PostgreSQL provider and EF Code First approach require Dapper package. Project contains 4 CRUD operation (plus list of all products). But usually I prefer avoid Dapper or other parasitic packages and made CRUD operation directly over DB Providers, for example https://github.com/Alex-1367/MySqlGenericRepository. And usually I prefer combine POCO class and DB repository operations to one "DB Access" layer. But now AI helper said me that split POCO class and operations with their is modern way to organize DB layer.

  4. Project with full testing the CRUD operation, but this only basic CRUD operation tests. My more advanced tests I placed to directory My TDD approach in ASP.NET Core - testing services, testing controllers, testing endpoints, testing DI container, complex test.. However this test also interesting. I this project I made one API-testing algorithm and try to pass the same test with two different API (based on ordinary ASP.NET backend and based on FastAPI approach).

  5. Project contains two backend API implementation: 4 project based on modern FastEndpoint approach (what looking for me as trash) and classic backend approach.


  6. For all other parts of projects I used clear ASP.NET API:



  7. Orchestrator project. Initially I want to use new Aspire Orchestrator from MS, but understand that its not workable project. And decide to return to normal Orchestrator way - start a number of console application simultaneously and use embedded to Visual Studio project Orchestrator.

  8. So, this is my liked way project Orchestrator way:


My workable B2B web service technologies

B2B webServices contains 3 my most liked workable technologies from NET FRAMEWORK (Asxh-Hndler, Asmx-service, Wcd service) and one new B2B service project from NET CORE - GRPC-service.


My workable Microsort ASP.NET frontend technologies (NET FRAMEWORK)


My workable Microsort ASP.NET frontend technologies (NET CORE)

Full replacement any Microsoft frontend technologies.



Microsoft context:



AspNetClassic context:



AspNetMvc context:



NetCoreBackend context:



WebApiServer context:



WebServiceClient context:



Blazor context:



Front context:



EfCodeFirst context:



Testing context:



ES6 context:



Angular context:



Comments ( )
Link to this page: http://www.vb-net.com/AllAspNet/Index.htm
< THANKS ME>