Cloud: How to configure the <environment include="Development"></environment> for .NET Core Renderer? - Progress Community

Loading

Skip to Main Content

Cloud: How to configure the <environment include="Development"></environment> for .NET Core Renderer?

This article provides information about how to configure the <environment include="Development"></environment> for .NET Core Renderer in Sitefinity Cloud.

Aug 8, 2025
Knowledge

Title

Cloud: How to configure the <environment include="Development"></environment> for .NET Core Renderer?

URL Name

how-to-configure-the-environment-include-development-environment

Article Number

000288329

Environment

Product: Sitefinity Cloud Product: Sitefinity .NET Core Renderer Version: 14.4, 15.0, 15.1, 15.2, 15.3

Question/Problem Description

Could you help us understand how to configure our staging and production environments to use different styles/scripts based on the environment?

Steps to Reproduce

Clarifying Information

The way to load scripts on a Layout file, for example, in the .NET Core Renderer in Sitefinity Cloud, is based on the environment.

Error Message

Defect Number

Enhancement Number

Cause

Resolution

Here is an example of how to use it on a local project:

<environment include="Development">
<script src="Scripts/form-all.js" defer section-name="Bottom" assembly-ref="Progress.Sitefinity.AspNetCore.FormWidgets"></script>
</environment>
<environment exclude="Development">
<script src="Scripts/form-all.min.js" defer section-name="Bottom" assembly-ref="Progress.Sitefinity.AspNetCore.FormWidgets"></script>
</environment>

The principle here is like "If / Else":

If the environment is set as Development >> Load this script in the Include tag.

If the environment is NOT set as Development >> Load the script in the Exclude tag

You can change the value on the Staging environment ASPNETCORE_ENVIRONMENT to be: Staging. This way, in the Layout files, the code must be changed to something like this:

<environment include="Development">
<script src="Scripts/form-all.js" defer section-name="Bottom" assembly-ref="Progress.Sitefinity.AspNetCore.FormWidgets"></script>
</environment>
<environment include="Staging">
<script src="Scripts/form-all.js" defer section-name="Bottom" assembly-ref="Progress.Sitefinity.AspNetCore.FormWidgets"></script>
</environment>
<environment include="Production">
<script src="Scripts/form-all.min.js" defer section-name="Bottom" assembly-ref="Progress.Sitefinity.AspNetCore.FormWidgets"></script>
</environment>

This way, based on the variable, the code will execute a different script.

Development for Local

Staging for Cloud Staging

Production for Cloud Production.

Note: The default value of the ASPNETCORE_ENVIRONMENT variable is Production.

More information in this Microsoft documentation: https://learn.microsoft.com/en-us/aspnet/core/fundamentals/environments?view=aspnetcore-9.0

Workaround

Notes

Keyword Phrase

Last Modified Date

8/8/2025 11:45 AM

Sitefinity Bugs & IssuesSitefinity CloudSitefinity General DiscussionsSitefinity UpgradingSitefinity Front & Back-End Development

Drop Files

Upload FilesOr drop files

Disclaimer

The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.

Loading

Cloud: How to configure the <environment include="Development"></environment> for .NET Core Renderer? - Progress Community