Visual Studio 2017 Localization Publish Settings

Question

This should be simple, but I haven't found a way to make this stop happening. Visual Studio publishes a lot of localized DLLs - It appears there is German localization, Spanish localization, Italian localization, french localization, Japanese localization, Russian localization and Korean localization. I have an ASP.NET Web API ODATA application, and when I publish the project using Visual Studio 2017, I have these localized dll's taking up unnecessary space in the bin folder. My application only needs to support En-US. How can I make this change? Screenshot of published bin folder:

Do you use any external dlls that are localized to these languages? — Haytam, Feb 20 '18 at 20:14
Does this answer your question? [Why is Microsoft.CodeAnalysis published with ASP.NET Core website?](https://stackoverflow.com/questions/58291135/why-is-microsoft-codeanalysis-published-with-asp-net-core-website) — mrmowji, Jan 12 '20 at 11:04

score 10 · Accepted Answer · answered Feb 20 '18 at 20:51

10

Here is what worked for me:

Open your csproj file with your favorite editor
Under the heading <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' "> add the line:

<ExcludeFoldersFromDeployment>bin\ar;bin\cs;bin\de;bin\es;bin\fr;bin\he;bin\hi;bin\it;bin\ja;bin\ko;bin\nl;bin\pl;bin\pt;bin\ru;bin\tr-TR;bin\zh-Hans;bin\zh-Hant</ExcludeFoldersFromDeployment>

Republish your solution

answered Feb 20 '18 at 20:51

Jordan

2,992
2
20
29

3

I do not think this is for .net core – Daniel Williams Dec 22 '19 at 04:31
@DanielWilliams did you find any solution for .Net Core ? – Mlle 116 Mar 02 '20 at 10:15
Yes though I don’t like it. In the post build just have it delete each of those folders. – Daniel Williams Mar 03 '20 at 13:57

score 0 · Answer 2 · answered Mar 03 '20 at 10:28

I faced the same problem for my .NET core 2.0 web API. It appeared when I moved the solution from a machine to another where a new version of .NET Core was installed: .NET Core 2.1 ; That's why, on publishing all files of .NET core 2.0 where generated. To resolve this issue, I decided to migrate to version 2.1 which solved the issue and the published files were generated smoothly :)

score -4 · Answer 3 · answered Jul 04 '19 at 14:23

-4

In my case i just remove below item from csproj file

<PackageReference Include="Microsoft.CodeAnalysis.CSharp.Workspaces" Version="3.1.0" />

Best Regurds

answered Jul 04 '19 at 14:23

D.L.MAN

990
12
18

I don't see this line in the csproj file in the my .NET Core 3.1 project. – thd Dec 29 '19 at 16:11

Visual Studio 2017 Localization Publish Settings

3 Answers3

Linked