ASP.NET Core in .NET 11

 As of the latest .NET 11 Preview releases (March 2026), ASP.NET Core and Blazor have introduced several features focused on developer productivity, cleaner code, and better performance.

Summary of the most significant changes:

Blazor Improvements

New Components

DisplayName Component: A new built-in component that renders property names directly from metadata attributes like [Display] or [DisplayName]. This brings feature parity with MVC’s @Html.DisplayNameFor().

Label Component: Specifically for forms, this component renders accessible <label> elements and automatically extracts the display name from your model attributes.

EnvironmentBoundary: Allows you to conditionally render content based on the hosting environment (e.g., Development vs. Production) consistently across both Blazor Server and WebAssembly.

BasePath: Automatically renders the <base href="..."> tag, which is particularly helpful for apps hosted under subpaths (e.g., /dashboard/).

Navigation & Interaction

Relative Navigation: NavigationManager.NavigateTo and the NavLink component now support a RelativeToCurrentUri parameter. This allows you to navigate relative to the current page path rather than the app's root.

QuickGrid OnRowClick: The QuickGrid component now has a native OnRowClick event. When used, it automatically applies a pointer cursor to rows and handles the click callback.

Startup & Configuration

Unified Startup Format: The Blazor.start() options object format introduced for Blazor Web Apps in .NET 8 is now supported for standalone Blazor Server and Blazor WebAssembly scripts.

IHostedService in Wasm: Blazor WebAssembly now supports IHostedService, allowing you to run background services directly in the browser.

ASP.NET Core Core Framework

Performance & Observability

Native OpenTelemetry Tracing: ASP.NET Core now builds OpenTelemetry semantic attributes directly into HTTP server activities. You no longer need a separate instrumentation package to collect standard trace data.

Kestrel Hardening: The HTTP/1.1 parser has been reworked to handle malformed requests more gracefully, resulting in a 20–40% throughput improvement in high-invalid-traffic scenarios (like port scanning).

APIs & Tools

OpenAPI 3.2.0: Support has been updated to the latest specification, though this includes some breaking changes for client generators.

Web Worker Template: A new dotnet new webworker project template allows Blazor Wasm apps to easily offload heavy computations to a background Web Worker.

Metrics & Tracing: New built-in metrics have been added for Blazor WebAssembly to track component render times and performance.

Runtime & SDK

Runtime-Native Async: .NET 11 introduces "Runtime Async," which makes asynchronous calls a first-class citizen at the runtime level, leading to cleaner stack traces and lower overhead.

CoreCLR on WebAssembly: Significant progress has been made in migrating Blazor WebAssembly from the Mono runtime to CoreCLR, promising better performance and JIT support in the future.

SQL Server 2025 Regular expressions functions

 

Core Regex Functions

The system provides several functions to search, modify, and analyze strings using patterns:

Function	Purpose
REGEXP_LIKE	Returns True if the text matches the pattern.
REGEXP_REPLACE	Modifies a string by replacing matches with a new value.
REGEXP_SUBSTR	Extracts a specific occurrence of a matching substring.
REGEXP_INSTR	Returns the position (start or end) of a match.
REGEXP_COUNT	Counts how many times a pattern appears.
REGEXP_MATCHES	Returns a table of all captured substrings.
REGEXP_SPLIT_TO_TABLE	Splits a string into a table using the pattern as a delimiter.

Syntax and Construction

Regex patterns are built using literal characters (which match themselves) and metacharacters (which have special logic).

• Escaping: To match a literal metacharacter (like * or ?), you must use a backslash (\*).

• Concatenation & Alternation: * e1 e2 matches "e1" followed by "e2".

  • e1 | e2 matches either "e1" or "e2".

• Repetition Operators:

  • *: Zero or more matches.

  • +: One or more matches.

  • ?: Zero or one match.

• Precedence: Operators follow a specific order of strength: Repetition (strongest) > Concatenation > Alternation (weakest). Parentheses () can be used to override this order.

let's assume we are working with a string representing a standard product code: Item_#1234-Blue.

 Examples

• REGEXP_LIKE (The Filter)

  • Goal: Check if a string contains a 4-digit number.

  • Pattern: \d{4}

  • Result: True (since 1234 matches).

• REGEXP_SUBSTR (The Extractor)

  • Goal: Pull the color name from the end of the string.

  • Pattern: [^-]+$ (Matches characters after the last hyphen).

  • Result: Blue

• REGEXP_REPLACE (The Cleaner)

  • Goal: Remove the hash symbol (#).

  • Pattern: #

  • Replacement: '' (Empty string).

  • Result: Item_1234-Blue

• REGEXP_COUNT (The Auditor)

• Goal: Count how many times a hyphen appears.

• Pattern: -

• Result: 1

Cheers

Samitha

GitHub Copilot in SQL Server (Preview)

GitHub Copilot for SQL Server Management Studio (SSMS) integrates AI directly into your database environment to streamline T-SQL development. Here is a summary of how it works and what it offers:

How it Works

The integration connects your GitHub Copilot account to SSMS. When you submit a prompt, SSMS sends it to the selected AI model along with contextual metadata—such as your SQL version and database schema—to ensure the generated code is accurate and relevant to your specific environment.

Key Features

• Interactive Chat: Use a dedicated chat window or an inline chat view to ask questions using natural language.

• T-SQL Assistance: Generate, fix, or optimize SQL queries on the fly.

• Slash Commands: Use quick shortcuts for specific tasks:

  • /doc: Automatically document your code.

  • Explain: Get a breakdown of complex queries.

  • Fix/Optimize: Improve query performance or resolve errors.

Note: This feature is currently in Preview. You will need an active GitHub Copilot subscription and the latest SSMS preview installation to use it. 

Cheers,

Samitha

npm run build does not work

If you are experiencing building js files for production follow these steps

•  Make sure you have the correct node version

          execute node -v in PowerShell / Command Prompt / VS Code terminal

• Delete node_modules 
• Delete package-lock.json
• Install correct node version
• Restart the Terminal (This step is required on Windows so PATH updates correctly)
• execute npm install in PowerShell / Command Prompt / VS Code terminal
• execute npm run dev in PowerShell / Command Prompt / VS Code terminal

Cheers

Samitha

SQL Server 2025 fuzzy string matching(preview)

 Fuzzy (approximate) string matching compares two strings Chto determine how similar they are and to measure their differences. It is used to identify strings that may vary due to character corruption, such as spelling mistakes, transposed or missing characters, or the use of abbreviations. This technique relies on algorithms that detect similarity based on character patterns or phonetic likeness, enabling the matching of strings that sound alike or are nearly identical despite minor variations.

Check here for samples

Samitha

SQL Server LAG() Function

 The SQL LAG() function is a window function used to access a column’s value from a previous row within a defined partition and order. Unlike aggregate functions, it does not reduce the number of rows; instead, it returns a corresponding value for each row. By specifying a partition (e.g., by organisation) and an order (e.g., by year), LAG() enables row-by-row comparisons, such as comparing current values with prior-period values

E.g

SELECT 

    Department,

    Employee,

    SalaryMonth,

    Salary,

    LAG(Salary, 1, 0) 

        OVER (PARTITION BY Department ORDER BY SalaryMonth) AS PrevMonthSalary

FROM EmployeeSalary

ORDER BY Department, SalaryMonth

Result

Department	Employee	SalaryMonth	Salary	PrevMonthSalary
IT	John	2024-01	120000	0
IT	John	2024-02	125000	120000
IT	John	2024-03	130000	125000
HR	Mary	2024-01	90000	0
HR	Mary	2024-02	92000	90000
HR	Mary	2024-03	95000	92000

SQL Server OUTER APPLY

 OUTER APPLY is a powerful operator used to join each row from an outer table to the results of a table-valued function or subquery. It behaves like a LEFT JOIN, but works with correlated subqueries that return multiple columns.

OUTER APPLY:

• Evaluates the right-hand subquery for each row of the left table.

• Returns all rows from the left table.

• Returns matching rows from the APPLYed subquery — or NULLs when the subquery returns nothing.

It’s similar to:

Operator                      BehaviorCROSS APPLY         Like INNER JOINOUTER APPLY         Like LEFT JOIN

E.g

SELECT 

    c.CustomerID,

    c.Name,

    o.OrderID,

    o.OrderDate

FROM Customers c

OUTER APPLY (

    SELECT TOP(1) *

    FROM Orders o

    WHERE o.CustomerID = c.CustomerID

    ORDER BY o.OrderDate DESC

) o;

Cheers

Samitha