Back-End Frameworks
hurbis.comum
Biblioteca comum para back-end do Hurbis Framework.
hurbis.framework.comum
Biblioteca comum para back-end do Hurbis Framework.
orchardcore.audittrail
Orchard Core CMS is a Web Content Management System (CMS) built on top of the Orchard Core Framework. Provides a log for recording and viewing back-end changes.
jsvaporizer.net.8
Cut down on JavaScript. Write more C#. A minimalistic .NET 8 WebAssembly library that lets you unify front-end and back-end logic without committing to a full framework like Blazor.
felixb.hapil.testing.nunit
Hapil is a dynamic MSIL generation library, which serves a back-end for the following design techniques: - CoI - Convention-over-Implementation - Aspect-Oriented Programming, through decoration - [planned] Subject-Oriented Programming, via mix-ins - [planned] Duck Typing Hapil provides a base test class for unit testing code generators built with Hapil. Hapil.Testing.NUnit adapts the base test class to NUnit testing framework.
stimulsoft.reports.server.connect.api
The Stimulsoft Reports.Server platform provides a full-featured back-end solution for your .NET application. API provides access to the main functions of the system and automates user actions. You can also use this API in conjunction with Stimulsoft Cloud.
badaboomshop
Webshop back-end framework based on the IAM stack
gazel.configuration.mvc
Gazel is a back-end development framework for the .NET framework. This package contains the ASP.NET MVC configuration layer of Gazel and should be used in your host and configuration projects.
hydra.interfaces
Hydra is a app generation tool with resulting source code. Generated front-end support for Ionic/Angular. Restful service layer support for .NET Core. Back-end support for SQL Server. Other supported technologies coming soon as Hydra is highly extensible. Also includes support for mobile capability, Docker, Helm, Azure Devops, and Kubernetes.
gazel.configuration
Gazel is a back-end development framework for the .NET framework. This package contains the configuration layer of Gazel and should be used in your app projects.
gazel
Gazel is a back-end development framework for the .NET framework. This package contains the abstraction layer of Gazel and should be used in your module projects.
gazel.client
Gazel is a back-end development framework for the .NET framework. This package contains the service client layer of Gazel and should be used in your .NET applications that consume your back-end services.
utils.core
Hydra is a app generation tool with resulting source code. Generated front-end support for Ionic/Angular. Restful microservice layer support for .NET Core. Back-end support for SQL Server. Other supported technologies coming soon as Hydra is highly extensible. Also includes support for mobile capability, progressive web apps (PWA), Docker, Helm, Azure Devops, and Kubernetes.
stimulsoft.connect.api
The Stimulsoft BI platform provides a full-featured back-end solution for your .NET application. API provides access to the main functions of the system and automates user actions. You can use this API in conjunction with Stimulsoft Cloud and Stimulsoft Server.
stimulsoft_reports.server_connect_api
The Stimulsoft Reports.Server platform provides a full-featured back-end solution for your .NET application. API provides access to the main functions of the system and automates user actions.
moellontoolkit
Set of ready to use common dialog boxes and components based on the MVVM pattern for WPF/xaml applications. Provide also a basic MVVM framework with a back-end application controller. See the gitHub repository and wiki: https://github.com/yvlawy/MoellonToolkit. See the blog to have more explanations: http://yvlawy.blogspot.fr
azuredistributedservice
The AzureDistributedService library provides a framework for making remote procedure calls (RPC) from front-end clients (WebRoles/WebSites) to back-end VMs (WorkerRoles) using Azure Storage Queues. The system is easy to set-up and the calls look like simple RPC calls. The system internally uses .NET 4.5+ async-await pattern to allow even a pair Extra Small front-end VMs to handle hundreds of simultaneous requests. And because the front-end communicates with the back-end through an Azure Storage Queue, the worker VMs can be auto-scaled trivially using Azure's built in auto-scaling.