Blazor Server examples
Reference integration package for teams evaluating RichTextEditor in Blazor Server applications.
Download 2.4.0
dotnet new richtexteditor-blazor -n MyAppDownloads
Download RichTextEditor 2.4.0 and the packages that match your stack.
Start with the core editor package, then pull the example project for Blazor, ASP.NET, PHP, Angular, React, or Vue. Legacy 1.015 builds and a 1.x to 2.4.0 upgrade path are available below.
Package overview
Everything needed for evaluation, legacy maintenance, and rollout.
CurrentVersion 2.4.0Recommended for all new evaluations and production work.
LegacyVersion 1.015Available for existing 1.x implementations that still need the older build.
ExamplesFramework packagesReady-made sample projects for Blazor, ASP.NET, PHP, Angular, React, and Vue.
LicensingPerpetual purchaseMove from evaluation to a one-time license when your team is ready.
Version guide
Choose the right package before you download.
Use the current 2.4.0 packages for new work, keep the 1.015 files for existing deployments that still depend on the older release, and use the upgrade page when you need to move a 1.x license forward.
Start fresh
Use 2.4.0 for new evaluationsThe current release is the right starting point for teams testing the editor today.
Maintain legacy apps
Keep 1.015 where neededOlder builds remain available so existing 1.x applications can stay stable during transition work.
Move forward
Upgrade from 1.x to 2.4.0Existing customers can use the upgrade path instead of repurchasing a full new license.
Fastest start — npm
RichTextEditor
Install straight from npm — the package ships the editor plus React, Vue, Angular, Svelte, headless, and server entry points, and always tracks the current release.
npm install @richscripts/richtexteditornpm create @richscripts/richtexteditor my-app -- --reactFramework examples
Download example projects by framework.
These packages are useful when you want to evaluate RichTextEditor in a realistic app structure instead of starting from a blank page. .NET teams can scaffold instead of downloading: dotnet new install RichTextEditor.Templates, then run the per-framework command shown on each card.
4.7 MB
ASP.NET Core Razor examples
Sample project showing editor setup inside Razor Pages and common ASP.NET Core page flows.
Download 2.4.0
dotnet new richtexteditor-razor -n MyAppASP.NET Core MVC examples
Controller and view-based sample package for MVC applications built on ASP.NET Core.
Download 2.4.0
dotnet new richtexteditor-mvc -n MyAppASP.NET Framework MVC examples
Classic ASP.NET MVC sample package for teams working in the .NET Framework stack.
ASP.NET Web Forms examples
Web Forms sample package for legacy .NET applications that still use the classic page model.
PHP examples
Starter project for evaluating RichTextEditor in PHP applications and admin workflows.
Angular examples
Angular integration package for teams testing component-based setup and editor lifecycle flows.
Download 2.4.0
npm create @richscripts/richtexteditor my-app -- --angularReact examples
React sample package for evaluating editor state management, embeds, and application integration.
Download 2.4.0
npm create @richscripts/richtexteditor my-app -- --reactVue examples
Vue sample package for teams exploring RichTextEditor in modern frontend application workflows.
Download 2.4.0
npm create @richscripts/richtexteditor my-app -- --vueNeed help deciding?
Start with the core package, then add one example project.
Most teams only need the main RichTextEditor package plus one framework example that matches the application they are building. If you are evaluating multiple stacks, download the core package first and then compare framework examples side by side.