Скачать или смотреть How to Exclude Unwanted Language Directories When Publishing ASP.Net Core Apps

Learn how to publish your ASP.Net Core application with only the English language resources, excluding all other international directories.
---
This video is based on the question https://stackoverflow.com/q/60330650/ asked by the user 'kofifus' ( https://stackoverflow.com/u/460084/ ) and on the answer https://stackoverflow.com/a/65049252/ provided by the user 'RenanStr' ( https://stackoverflow.com/u/1203003/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: ASP.Net Core exclude published language directories other than english

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Excluding Published Language Directories in ASP.Net Core

When working with ASP.Net Core, developers often encounter the issue of having numerous language directories cluttering their published output. If you're publishing an ASP.Net Core application but only need the English version, this guide will help you streamline your deployment by excluding unwanted language resources.

The Problem

Imagine you're deploying your ASP.Net Core 3.1 application using the following command:

[[See Video to Reveal this Text or Code Snippet]]

However, upon checking the output folder, c:\MyServer, you find multiple international language directories, including cs, de, es, fr, and zh-hans, among others. This not only makes the directory messy but can also increase the size of your published output unnecessarily.

The Challenge

You attempted to use the ExcludeFoldersFromDeployment property in your project file (.csproj), adding lines for all the language folders you wanted to exclude. While this seemed like a valid solution, it unfortunately didn’t work as expected.

The Solution

To successfully publish your ASP.Net Core application with only the English language resources, follow these steps:

Step 1: Edit Your .csproj File

Open your project file, which has the .csproj extension.

Locate the <PropertyGroup> section.

Add the following line:

[[See Video to Reveal this Text or Code Snippet]]

Example .csproj Snippet

Your .csproj file should look something like this after the modification:

[[See Video to Reveal this Text or Code Snippet]]

Step 2: Publish Your Application Again

Now that you've edited your .csproj file, run the publish command again:

[[See Video to Reveal this Text or Code Snippet]]

What to Expect

After this modification and republishing, you should find that your output directory now only contains the English language resource folder, effectively excluding all others. This will make your deployment cleaner and more efficient.

Conclusion

By specifying the SatelliteResourceLanguages property in your project file, you can easily exclude unwanted language directories from your ASP.Net Core application's published output. This simple adjustment will help you maintain a streamlined deployment process, minimizing clutter and optimizing performance.

If you have any further questions or run into issues, feel free to ask!