From caaadbc370138ff676e95defb3b02381bbc9aae7 Mon Sep 17 00:00:00 2001 From: rndthoughts Date: Tue, 17 Jan 2017 14:42:01 +0000 Subject: [PATCH] Workaround for ASP.NET core app publish Publishing can be fixed by altering the targets file in the manner specified. --- known-issues-vs2017.md | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/known-issues-vs2017.md b/known-issues-vs2017.md index a33e166..30a22ac 100644 --- a/known-issues-vs2017.md +++ b/known-issues-vs2017.md @@ -152,7 +152,7 @@ To invoke bundling and minification, publish the project. For example, publish Cannot apply migrations during publish of ASP.NET Core project * #### Issue: -Ability to provide a destination connection string and apply migrations are not available in the Publish Settings for an ASP.NET Core project +Ability to provide a destination connection string and apply migrations are not available in the Publish Settings for an ASP.NET Core projectxml * #### Workaround: You need to manually apply migrations on the destination database server @@ -164,7 +164,17 @@ Unable to publish ASP.NET Core Web Application (.NET Framework) If you try to publish an ASP.NET Core Web Application (.NET Framework), you will run into the following error: "DestinationFiles" refers to 1 item(s), and "SourceFiles" refers to 2 item(s). They must have the same number of items * #### Workaround: -None available +Modify "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Sdks\Microsoft.NET.Sdk\build\Microsoft.NET.Publish.targets" and replace the Copy attribute on line 128 with the following: + +```xml + +``` ### Publish crashes Publish crashes on locales that do not use '.' as a decimal separator