Codeer.LowCode.Blazor 1.3.2

There is a newer version of this package available.
See the version list below for details.
dotnet add package Codeer.LowCode.Blazor --version 1.3.2
                    
NuGet\Install-Package Codeer.LowCode.Blazor -Version 1.3.2
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Codeer.LowCode.Blazor" Version="1.3.2" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="Codeer.LowCode.Blazor" Version="1.3.2" />
                    
Directory.Packages.props
<PackageReference Include="Codeer.LowCode.Blazor" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add Codeer.LowCode.Blazor --version 1.3.2
                    
#r "nuget: Codeer.LowCode.Blazor, 1.3.2"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package Codeer.LowCode.Blazor@1.3.2
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=Codeer.LowCode.Blazor&version=1.3.2
                    
Install as a Cake Addin
#tool nuget:?package=Codeer.LowCode.Blazor&version=1.3.2
                    
Install as a Cake Tool

Codeer.LowCode.Blazor

Codeer.LowCode.Blazor is a library designed to integrate execution engine-type low-code features into your Blazor app. It allows for the rapid creation of most functionalities using no-code/low-code, while specialized features can be crafted with the same level of detail as full-scratch professional coding. As a result, it is possible to develop satisfactory applications quickly and at a low cost. Users can customize the application themselves after its release.

Codeer.LowCode.Blazor.Templates

  • Want to save on cost and time
  • Want to effectively utilize RDB
  • Want to leverage existing data and systems
  • Have specific features in mind
  • Desire customization after release

Create Screens with Ease

Create screens freely with a combination of canvas layout and grid layout and flow layout. It's possible to create not just regular screens but also dialogs. Interaction between UI components can be achieved with no-code or minimal scripting. Essential elements like sidebar, header, and footer are provided, and those with specific preferences can customize with pro-code.

Seamless RDB Integration

Associate forms and DB tables for input and output of data. Linking multiple forms allows representation of Join or 1N relationships. Forms can also be linked to Views, enabling easy implementation of BI functions. Common database operations such as logical deletion, optimistic locking, and tracking of creation/update information are included. Change history can also be maintained.

More Freedom with Scripts

Write in syntax nearly identical to C#. The API design allows for implementation of features with minimal coding. Code completion makes implementation easy, and customized functions can be called with pro-code. Execution is primarily on the client-side, but server-side execution is also supported.

  • General computational operations
  • Screen controls
  • Execution of WebAPI
  • Editing Excel/PDF creation

Excel Integration Support

Supports not only general data input/output but also allows for creating templates in Excel and modifying them for report generation. Conversion to PDF is also possible.

Authentication & Authorization

Provide generic cookie authentication or default authentication using Azure Active Directory in your template code. Other authentication methods can also be customized. Authorization allows for access control at the application, screen, and data levels.

Implement Specific Features with Pro-Code

In some cases, special screens/features are necessary. As Codeer.LowCode.Blazor is a Blazor library, .NET code can be added for such implementations. Moreover, creating components allows for their use in various places.

Product Compatible and additional computed target framework versions.
.NET net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed.  net9.0 was computed.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  net10.0 was computed.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (9)

Showing the top 5 NuGet packages that depend on Codeer.LowCode.Blazor:

Package Downloads
Codeer.LowCode.Blazor.Designer

This is a library that adds LowCode functionality to Blazor apps.

Codeer.LowCode.Bindings.Blazor-ApexCharts

You can use Blazor-ApexCharts with Codeer.LowCode.Blazor.

Codeer.LowCode.Bindings.Blazor-ApexCharts.Designer

You can use Blazor-ApexCharts with Codeer.LowCode.Blazor.

Codeer.LowCode.Blazor.Extras

Extra field components for Codeer.LowCode.Blazor. Includes Calendar, Gantt Chart, Task Board (Kanban), Rich Text Editor, Color Picker, Marker List, and Password Hash fields.

Codeer.LowCode.Bindings.Fluent.Blazor

You can use FluentUI with Codeer.LowCode.Blazor.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
1.3.3 54 6/12/2026
1.3.2 77 6/11/2026
1.3.1 106 6/4/2026
1.3.0 99 6/4/2026
1.2.65 122 5/26/2026
1.2.64 118 5/15/2026
1.2.63 116 5/12/2026
1.2.62 107 5/7/2026
1.2.61 213 5/6/2026
1.2.60 104 5/5/2026
1.2.59 97 5/5/2026
1.2.58 357 4/27/2026
1.2.57 104 4/21/2026
1.2.56 174 4/16/2026
1.2.55 223 4/10/2026
1.2.54 123 4/2/2026
1.2.53 219 3/31/2026
1.2.52 123 3/24/2026
1.2.51 151 3/16/2026
1.2.50 164 3/9/2026
Loading failed

Improved the design-time checks for scripts. Code that will always fail at runtime is now reported at design time.
     - Detects method, user-defined function, and constructor (new) calls whose argument types do not match any overload.
     - Detects if / while / for / conditional (?:) conditions whose type cannot be treated as a boolean (such as a module or a list).
     - Detects foreach over a type that is not enumerable (such as a number).
     - Detects indexing with [] on a type that is neither an array nor has an indexer.
     - Detects binary/unary operators used with incompatible types (e.g. arithmetic or comparison on a string or list, negating a non-boolean value).
     - Fixed false positives: assignments that the runtime converts at execution time (e.g. assigning a number or bool to a string variable, or a string to a number variable) are no longer reported as errors.
     Note: To avoid false positives, cases whose result depends on the actual value (e.g. converting a string to a number) and cases that cannot be determined statically (e.g. var or field values) are intentionally not reported.

     Removed an unused SQL parameter that was bound when generating "is null" / "is not null" search conditions. This is an internal cleanup with no change in behavior.

     Enabled indexing into string values in scripts (e.g. text[0] returns the character at that position).

     Added support for string interpolation ($"...") in scripts, including format (:fmt) and alignment (,N) specifiers (e.g. $"{name}: {price:N0}").

     Added support for implicit array creation (new[]{...}) in scripts. The element type is inferred from the values: all the same type uses that type, mixed numeric types use decimal[], and arrays containing null or mixed types use object[].

     Added filtering, limiting, and paging methods to ModuleSearcher used in scripts.
     - AddNotEqual(field, value): adds a "not equal" condition (passing null generates "is not null").
     - Limit(count): sets the maximum number of rows to fetch. Without it, all matching rows are fetched, so set it when searching tables that may contain many rows.
     - ExecutePage(pageIndex) / ExecuteRawPage(pageIndex): fetch the specified page (0-based) together with the total matching count in a single query, returned as ModulePageResult / ModuleDataPageResult (Items and TotalCount). Use them with Limit for pagers.
     - ExecuteFirstOrDefault(): returns the first matching module, or null when there is no match (handy for master/lookup references).
     - BatchModuleSearchResponse.GetBy(searcher): retrieves a batch result by the ModuleSearcher you passed to Execute, so you no longer need to track result indexes (passing a searcher not in the batch throws).

     Names that occupy the "type" namespace are now validated by the design check. A module or page-frame name that duplicates another such name (another module / page-frame, a ProCode component / module / list-element class name, or a framework type name; compared case-insensitively), or that is not a valid C# identifier, is now reported as a design error. This prevents name collisions that break type resolution in scripts.