Skip to content

991761: Replace obsolete Class used in CSP #4642

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Nov 13, 2025
+13 −9
Merged

991761: Replace obsolete Class used in CSP #4642

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
c6b6de8
991761: Replace obsolete Class used in CSP
Athiswaran-SF3980 Nov 10, 2025
8b0c56d
Merge branch 'hotfix/hotfix-v31.2.2' into 991761-Replace-obsoleteHF
Athiswaran-SF3980 Nov 13, 2025
b69411c
991761: Replace obsolete Class used in CSP
Athiswaran-SF3980 Nov 13, 2025
b91dde9
Merge branch '991761-Replace-obsoleteHF' of https://github.com/syncfu…
Athiswaran-SF3980 Nov 13, 2025
1fba9e7
991761: Replace obsolete Class used in CSP
Athiswaran-SF3980 Nov 13, 2025
0b092c6
991761: Replace obsolete Class used in CSP
Athiswaran-SF3980 Nov 13, 2025
464c6d1
00000: Update net 10 related changes
kmuthukumarmkm Nov 13, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions ej2-asp-core-mvc/EJ2_ASP.NETCORE/system-requirements.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,21 +16,24 @@ To get started with ASP.NET Core application, ensure the following software to b

ASP.NET Core Applications can be developed using one of the following IDEs. You can also develop using [.NET CLI](https://docs.microsoft.com/en-us/dotnet/core/tools/) without below IDEs.

* [Visual Studio 2022](https://visualstudio.microsoft.com/vs/)
* [Visual Studio 2026](https://visualstudio.microsoft.com/downloads/#visual-studio-professional-2026)
* [Visual Studio 2022](https://visualstudio.microsoft.com/vs/older-downloads/#visual-studio-2022-and-other-products)
* [Visual Studio 2019](https://visualstudio.microsoft.com/vs/older-downloads/)
* [Visual Studio Code](https://code.visualstudio.com/)

## Framework & SDK

One of the the following .NET SDK is required to develop and run the Syncfusion<sup style="font-size:70%">&reg;</sup> UI controls for ASP.NET Core application.

* [.NET 10.0 SDK](https://dotnet.microsoft.com/en-us/download/dotnet/10.0)
* [.NET 9.0 SDK](https://dotnet.microsoft.com/en-us/download/dotnet/9.0)
* [.NET 8.0 SDK](https://dotnet.microsoft.com/en-us/download/dotnet/8.0)
* [.NET Core SDK 3.1](https://dotnet.microsoft.com/en-us/download/dotnet/3.1)
* [.NET Core SDK 2.0](https://dotnet.microsoft.com/en-us/download/dotnet/2.0)

If you are planning to use Visual Studio to develop ASP.NET Core Applications.
* .NET 10.0 requires Visual Studio 2026 18.0.0 or later.
* .NET 9.0 requires Visual Studio 2022 17.12.0 or later.
* .NET 8.0 requires Visual Studio 2022 17.8.0 or later.
* .NET Core SDK 3.1 requires Visual Studio 2019 16.4 or later.
* .NET Core SDK 2.0 requires Visual Studio 2017 15.7 or later.
* .NET Core SDK 2.0 requires Visual Studio 2017 15.7 or later.
15 changes: 8 additions & 7 deletions ej2-asp-core-mvc/common/EJ2_ASP.NETCORE/content-security-policy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ publishingplatform: ##Platform_Name##
documentation: ug
---

# Content Security Policy
# Content Security Policy in ASP.NET Core

Content Security Policy (CSP) is a security feature implemented by web browsers to protect against attacks such as cross-site scripting (XSS) and data injection. It limits the sources from which content can be loaded on a web page. To enable strict Content Security Policy (CSP), certain browser features are disabled by default. To use Syncfusion<sup style="font-size:70%">&reg;</sup> controls with strict CSP mode, it is essential to include the following directives:

Expand All @@ -29,14 +29,13 @@ using System.Security.Cryptography;
...
app.Use(async (context, next) =>
{
RNGCryptoServiceProvider rng = new RNGCryptoServiceProvider();
byte[] nonceBytes = new byte[32];
rng.GetBytes(nonceBytes);
RandomNumberGenerator.Fill(nonceBytes);
string nonceValue = Convert.ToBase64String(nonceBytes);
context.Items.Add("ScriptNonce", nonceValue);
context.Items.Add("Nonce", nonceValue);
context.Response.Headers.Add("Content-Security-Policy", string.Format(
"script-src 'self' 'nonce-{0}' https://cdn.syncfusion.com;" +
"style-src-elem 'self' 'unsafe-inline' https://cdn.syncfusion.com https://fonts.googleapis.com;" +
"style-src-elem 'self' 'nonce-{0}' https://cdn.syncfusion.com https://fonts.googleapis.com;" +
"font-src 'self' data: https://fonts.gstatic.com;" +
"object-src 'none';", nonceValue));
await next();
Expand All @@ -52,8 +51,10 @@ app.Use(async (context, next) =>
{% highlight c# tabtitle="~/_Layout.cshtml" %}
<head>
...
<!-- Syncfusion ASP.NET Core controls styles -->
<link href="https://cdn.syncfusion.com/ej2/{{ site.ej2version }}/bootstrap5.css" nonce="@Context.Items["Nonce"]" rel="stylesheet" />
<!-- Syncfusion ASP.NET Core controls scripts -->
<script src="https://cdn.syncfusion.com/ej2/{{ site.ej2version }}/dist/ej2.min.js" nonce="@Context.Items["ScriptNonce"]"></script>
<script src="https://cdn.syncfusion.com/ej2/{{ site.ej2version }}/dist/ej2.min.js" nonce="@Context.Items["Nonce"]"></script>
</head>
{% endhighlight %}
{% endtabs %}
Expand All @@ -65,7 +66,7 @@ app.Use(async (context, next) =>
<body>
...
<!-- Syncfusion ASP.NET Core Script Manager -->
<ejs-scripts add-nonce="@Context.Items["ScriptNonce"]"></ejs-scripts>
<ejs-scripts add-nonce="@Context.Items["Nonce"]"></ejs-scripts>
</body>
{% endhighlight %}
{% endtabs %}
Expand Down