re-linq Frontend: A foundation for parsing LINQ expression trees and generating queries in SQL or other languages. Key features: - Transforms expression trees into abstract syntax trees resemblying LINQ query expressions (from ... select syntax) - Simplifies many aspects of this tree (sub queries, transparent identifieres, pre-evaluation ...) - Provides basic infrastructure for backend development (e.g. SQL generation) - Provides a framework for user-defined query extensions and transformations
BotDetect CAPTCHA Generator protects ASP.NET/Core forms from spam. The Captcha protection is available on .NET/Core for jQuery, Angular & React frontends and ASP.NET MVCCore, MVC1-5, WebForms & WebPages backends. It works in China; doesn't stalk; nor does it slurp your form-data -- think: GDPR & LGPD! BotDetect uses many different image and sound algorithms for the generation of Captcha codes. While each Captcha algorithm is easily comprehensible to human users, generating Captcha codes by random algorithm makes the Captcha challenge extremely difficult to pass automatically. BotDetect provides an audio Captcha alternative to keep ASP.NET web applications accessible to the blind and other people for whom reading the Captcha code could be a problem, enabling you to make WCAG and Section 508 compliant websites. BotDetect is a self-hosted .NET Captcha Component -- no 3rd-party servers are involved in the generation, displaying, and validation of Captcha challenges. Therefore, BotDetect neither identify nor stalk your users and visitors -- nor does it slurp logins, passwords, and other data they fill in your forms. This allows for the GDPR, LGPD, and CCPA compliant sites -- and also does miracles for the forms on any of the national security-sensitive ones. FEATURES: -------------------- * Out-of-the-box integrations with Angular, AngularJS, jQuery, and React frontend frameworks * Produces XHTML 1.1 Strict, Section 508 and WCAG AAA compliant markup * Fully compatible with ASP.NET Core 1.x and 2.x * Fully compatible with legacy .NET 2.0 and onwards, .NET Core 1.x and .NET Core 2.x * Fully compatible with ASP.NET MVC 1-5 and ASP.NET Core MVC (MVC 6) * Fully compatible with ASP.NET WebForms * Fully compatible with ASP.NET Web Pages * Fully compatible with ASP.NET Ajax and jQuery Ajax validation * Fully compatible with SharePoint Server / Foundation * Visual Studio .NET 2017, 2015, 2013, 2012, 2010, 2008, 2005 and 2003 Designer support * Medium trust environment support for shared servers * Tested in Chrome, Firefox, Safari, IE, Edge and Opera browsers * Full support for all Android & iOS devices * Localized Captcha generation, using various Unicode character sets and downloadable multi-language sound pronunciations * Custom Captcha image size, format, color scheme... * Custom Captcha code length, style, character set, timeouts, generated code filtering... * Many other randomization & customization options * 60 secure & readable Captcha image styles * 20 secure & accessible audio Captcha sound styles * It works in China * It does not identify and stalk your users and visitors * It does not slurp your form data * It allows for the GDPR, LGPD, and CCPA compliant sites * Licensable source code What nuget to use? -------------------- Please note that from the version 4.2 onward we have two BotDetect CAPTCHA nugets on the nuget.org. * Use THIS nuget for ASP.NET applications running on the legacy .NET (non-Core) Frameworks * Use THIS nuget for ASP.NET Core applications running on the .NET Core Frameworks However, there is one special case that required the separate nuget. * Use our NEW helper nuget INSTEAD OF this one for the special case of ASP.NET Core applications running on the legacy .NET (non-Core) Frameworks. The new helper nuget name is CAPTCHA.asp.net.core.on.legacy.net.frameworks and it is available at https://www.nuget.org/packages/CAPTCHA.asp.net.core.on.legacy.net.frameworks/
Orchard Core CMS is a Web Content Management System (CMS) built on top of the Orchard Core Framework. The Themes modules allows you to specify the Frontend and the Admin theme.
Xwt is a cross-platform UI toolkit for creating desktop applications with .NET and Mono that run on multiple platforms from the same codebase. Xwt works by exposing one unified API across all environments that is mapped to a set of native controls on each platform. The framework consists of the frontend (Xwt core) and platform specific backends. Additionally to this core Xwt package you need to add an Xwt toolkit package (Xwt.*) for every platform you want your application to target.
Orchard Core CMS is a Web Content Management System (CMS) built on top of the Orchard Core Framework. Creates a frontend search that can be used with multiple search providers.
Generates frontend Vue.js metadata, models, api clients, and view models for Coalesce projects. Learn more at https://coalesce.intellitect.com/stacks/vue/overview.html
FrontEnd Framework For Dynamic Loading Of Views, Standard and custom Event Broadcast and Propagation After Install, Point your browser to http://[YOUR ROOT]/viewbindersample, e.g http://localhost:51163/viewbindersample
Contains templates for generating an entire codebase which uses EF6, CQRS, and Aurelia. This set of templates generates: - database entities and repositories (C#) - service models, mappings, interfaces, clients, and controllers (C#) - frontend models and services (TS) All generated code is dependency-injected (includes generated DI registration via SimpleInjector) and includes database entity to model mapping via AutoMapper.
re-linq SQL Backend: A framework for generating SQL based on the re-linq Frontend.
GoldenEye is a Full Stack framework written in .NET Core. The main goal of GoldenEye is to speed up your development process. It gathers most widely used frameworks in .NET world and pack them into a simple bootstrap Nuget packages. It also provide set of base classes, helpers, extensions that will help you with your daily work.
Asp .Net entity framework module of the aspor project. Aspor is a comprehensive web stack for building fast, modern and reliable web applications (SPA / PWA). The concept is based on a decoupled architecture with an independent OData interface running on an Asp .net service that is consumed by the React frontend application. Backend services are seperated with a Microservice architecture and connected together with Aspor streaming.
Semantic is a development framework that helps create beautiful, responsive layouts using human-friendly HTML.
CakeStack is an innovative Blazor library designed for seamless use with the Bulma CSS framework. It offers a comprehensive suite of UI components that enhance Blazor applications with Bulma's aesthetic and responsive design principles. Ideal for developers looking to expedite their front-end development, CakeUI provides intuitive, scalable, and visually appealing components that are easy to integrate into any project.
Backend for frontend for Blazor WebAssembly: cookie session, token handling and API forwarding.
Semantic is a development framework that helps create beautiful, responsive layouts using human-friendly HTML.
Heimdall browser runtime, frontend plugin SDK, shared attribute aliases, and optional hd attribute shortcuts as Razor Class Library assets.
Universal authentication framework with StandardApiController for any frontend, zero-config CORS, and unified API responses. Eliminates integration complexity with React, Vue, Angular support. Includes Google, Facebook, Apple, Azure B2C OAuth providers.
Contains supporting code for .NET WPF applications using the Prism framework from Microsoft.
Complete Universal Integration System for EasyAuth framework with StandardApiController, zero-config frontend support, and comprehensive extensions. Works with React, Vue, Angular, and any frontend framework. Includes all authentication providers and ASP.NET Core extensions.
The Windows shell of Shenora, the hybrid app framework for .NET + React: application bootstrapper with global exception handling, DPI-correct window-state persistence, one instance per install, a later launch handing the running app its arguments, secondary windows on their own STA threads, tray icon, frameless-chrome form, the main form's system animations on or off, a native launcher's startup screen closed once the main form shows, and the Windows implementations of the Shenora shell contracts (STA file dialogs, clipboard, UI-thread dispatcher). Hosts WebView2: environment prewarm, dev-server vs packaged-frontend loading, navigation/new-window/download/permission/process-failure handling, a page of the app's own for a page load that finds nothing, drag-drop zones, the app's colour scheme set on the profile of each WebView given it, and the postMessage IPC bridge with batched event push. Hosts Chromium the same way, through Shenora.Chromium: a ChromiumView control, with UseChromiumEngine running CEF beside the WinForms loop; reference Shenora.Chromium from the app itself, since CEF arrives only through that package's build. Hosts the auxiliary browser sessions (Shenora.Core.Sessions) in WebView2: WebView2SessionHost makes their off-screen browsers and an interactive session's modal window.
Semantic is a development framework that helps create beautiful, responsive layouts using human-friendly HTML.
Zero Framework is .NET based framework for rapid development of thick client applications using agile methodologies. It uses EF Code First, Caliburn.Micro, custom message-based comunication running over WCF and MEF for dependency resolution.
The adaptation of the "Yamato Daiwa Frontend" toolkit for the Blazor framework
Shenora: the hybrid app framework for .NET + React, portable across Windows, macOS, Linux, Android and iOS — reference ONE shell package and it brings this one: Shenora.Windows, Shenora.Android, Shenora.iOS, or Shenora.Chromium, the kit's own Chromium shell, which is how it reaches macOS and Linux. Three layers: Core is the contract (the typed IPC stack with its middleware dispatcher and scoped router, the event bus, the webview interception and file-serving pipeline with the app's frontend served from a folder or embedded in its assembly, and the platform-neutral shell contracts — the IUiDispatcher UI-thread seam plus file dialogs, clipboard, URL launching, UI blocking, holding the window at an orientation, the app's colour scheme, a window's system animations and a native launcher's startup screen, so application logic compiles with no Windows reference — and what both desktop shells share: the single-instance guard that hands a later launch's arguments to the running app, window-state persistence, revealing files and launching processes, naming who holds a file open, and the unhandled-exception report). Core also holds the auxiliary browser sessions, written once over the browsers each shell makes: a bounded pool of off-screen sessions, an interactive session over an isolated persistent profile, and streaming sessions (screencast out, synthetic input in); mechanisms only, the kit ships no workflow. Engine is the brain (the mission scheduler with claims, lanes and durable queues; journalled safe file mutation with path locks; staged self-update with safe archive extraction; versioned resource packs whose boot decision cannot skip the packaged-vs-fetched version comparison). Modules bridge .NET to the web (media probing, planning, remuxing, streamed range delivery and platform codec conversion, plus the shell's own PICTURE SURFACE — on a phone a film the webview refuses is drawn by the platform's player under a transparent region the page leaves, with no transcode and the page keeping every control; native file dialogs; Live Activities and playback sessions; request tracking; the system back gesture offered to the page per press, foreground transitions carrying how long the app was away, and holding the window portrait or landscape — which a page cannot do for itself, since its own screen.orientation.lock() works only in fullscreen). The outbound notification path reports what it accepted, filtered, dropped and delivered, so "my page receives no events" is answerable without guessing. Application host and builder via ShenoraApplication.CreateBuilder. Depends on Microsoft.Extensions DI (implementation) + logging abstractions.
Code-first admin panel and CRUD framework for .NET — define entity models with attributes, get a full admin UI with zero frontend code.
SpecIFicator frontend framework with plugin support.
GoodieBBUI is an innovative Blazor library designed for seamless use with the Bulma CSS framework. It offers a comprehensive suite of UI components that enhance Blazor applications with Bulma's aesthetic and responsive design principles. Ideal for developers looking to expedite their front-end development, GoodieBBUI provides intuitive, scalable, and visually appealing components that are easy to integrate into any project.
The adaptation of the "Yamato Daiwa Frontend" toolkit for the Blazor framework
Backends for Frontends for Modulus: one edge per client type (web SPA, mobile app, partner), each with its own authentication, token handling, CSRF, rate limits, response aggregation and YARP passthrough to the API host or to individual microservices.
A .NET 10 Backend-for-Frontend using YARP, standard OpenID Connect and Redis. Framework Data Protection encrypts server sessions and rotates data keys. Supports signed back-channel logout, coordinated refresh across replicas and host-owned OpenTelemetry. Compatible with OpenIddict.
Xwt is a cross-platform UI toolkit for creating desktop applications with .NET and Mono that run on multiple platforms from the same codebase. Xwt works by exposing one unified API across all environments that is mapped to a set of native controls on each platform. The framework consists of the frontend (Xwt core) and platform specific backends. Additionally to this core Xwt package you need to add an Xwt toolkit package (Xwt.*) for every platform you want your application to target.
NuFlexiArch-JSVapor is an experimental, lightweight framework for building interactive web applications using C# and WebAssembly, without relying on higher-level abstractions like Blazor.
Shenora WebView2 hosting: environment prewarm and creation, dev-server vs packaged-frontend loading (embedded resources or virtual host), navigation/new-window/download/permission/process-failure handling, runtime presence check, and the postMessage bridge with batched event push.