Reputation: 2683
Unwanted dll's after publish in Visual Studio 2017 RC
When I publish .net core application in Visual Studio 2017 RC, it creates 2 unwanted dll's, which are as follows:
Microsoft.DiaSymReader.Native.amd64.dll
Microsoft.DiaSymReader.Native.x86.dll
It happens only in Visual Studio 2017 RC and not in Visual Studio Express 2015.
I have found following link on github, but fix mentioned over there only removes ref folder from publish output.
https://github.com/aspnet/websdk/issues/123
Is there any way, by which I can get rid of these 2 heavy dll's as they size around 2MB in total?
Upvotes: 0
Views: 267
Answers (1)
Reputation: 2456
This was caused by a bug in Microsoft.NETCore.App version=1.1.0. When you reference that version, implicitly (the default), or explicitly, you will get those two assemblies in your publish directory.
The fix is to either upgrade to Visual Studio 2017 RTM, which implicitly references the version with the fix (1.1.1), or to explicitly reference 1.1.1 by adding <RuntimeFrameworkVersion>1.1.1</RuntimeFrameworkVersion> to your .csproj.
Upvotes: 3
Related Questions
- asp.net core 2.0 publish generating lots of DLL's
- Asp.net core publish creates all dll files in publish folder in visual studio 2017
- .net core visual studio publish is including runtimes
- Why is .Net Core 2.2 now publishing a ton of other dlls
- .NET core build output contains a lot of DLL files
- ASP.NET Core publish produces lots of DLLs in the published folder, why?
- Visual Studio 2017 - Potentially unneeded dlls in release folder
- Project`s dlls missing after publish asp .net web project
- dotnet publish failing using .NET Core 1.1 and new VS 2017 project format
- Missing DLL's when publishing ASP.NET Core web app