TFS 2017 Deploy ASP .NET Core
We are on TFS 2017 initial release (on premise install). I am looking to see how I can build ASP .NET Core 2.0 apps using TFS 2017 Build / Release. Right now our standard builds uses Visual Studio builds and we have visual studio 2015 installed on our build server.
When I am attempting to build ASP .NET core 2 MVC app, using Visual Studio build, the build is failing with an error message :
Trunk\xxxxxx.csproj (1, 1) Trunk\xxxxxx.csproj(1,1): Error MSB4041: The default XML namespace of the project must be the MSBuild XML namespace. If the project is authored in the MSBuild 2003 format, please add xmlns="http://schemas.microsoft.com/developer/msbuild/2003" to the element. If the project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format.
Can I ask what is the recommended approach to building / deploying .NET core 2.0 projects using TFS 2017?
Install VS 2017 on the build server? We already have VS 2015 installed on the build server. Can VS 2015 and VS2017 live side by side on the build server and will the VS build step pick up 2017? Visual Studio Builld
Or should we be installing .NET core 2.0 SDK on the build server and then use command line utility as a part of the build step.
Or should we switiching to MSBUILD instead of VS studio build and installing just the MSBuild for VS 2017 on the builld server.
1.You could install VS2017 on the build server. VS2017 and VS2015 could live side by side on either a build server or a develop machine. You just need to select which version you will use in visual studio version picklist. However VS2017 option is not support on the build-in Visual Studio Build task on TFS2017. It's not related to VS2017 installed on the build server or not.
2.You need to install .NET CORE 2.0 SDK on the build server, otherwise will get a similar error as below:
error : The version of Microsoft.NET.Sdk used by this project is insufficient to support references to libraries targeting .NET Standard 1.5 or higher. Please install version 2.0 or higher of the .NET Core SDK.
Highly recommend you to keep the build server environment as same as local develop machine, this will narrow down the build issue on TFS.
3.No you don't have to. Just follow the process in this tutorial-- Build your ASP.NET Core app
Suggest you update your TFS 2017 initial release to the latest version TFS2017 update2. This will include VS2017 in the picklist of vs version. And since .NetCore 2.0 released in May 2017 which is later then the initial TFS2017(November 2016), not sure if it's supported or have any other issues. However, one thing is certain: you could build .NET Core 2.0 apps in TFS2017update2 successfully. Moreover, there are many new features released with update2 version, there is no reason to stay on the initial TFS2017.
- Enabling a container to communicate with SQL Server in a separate container
- SignedCms, sign an existing hash?
- Cannot access a disposed object. A common cause of this error is disposing a context
- How to fix "No .NET SDKs were found." error--VSCode
- Why IEquatable implementation does not work when applied to an abstract base class?
- Migration of ASP.NET 4.6 Help Pages to .NET 6 (.net core)
- .NET Core Web API optional query parameter is still not null
- Does Microsoft have a recommended way to handle secrets in headers in HttpClient?
- System.InvalidOperationException: 'Invalid operation. The connection is closed.'
- How i can add shared css between two Blazor Project?
- MS Entity Framework Core 8.0 keeps throwing "System.Globalization.CultureNotFoundException"
- When a client needs to upgrade it's Dotnet version (Minor version)?
- EntityFramework Include method is not working
- Setup RabbitMQ consumer in ASP.NET Core application
- How to update all of my dotnet global tool by one command
- Blazor best practice for Non-nullable warnings
- Azure DevOps agent pool: How do I demand a specific net framework SDK capability?
- How to exclude a property from being serialized in System.Text.Json.JsonSerializer.Serialize() using a JsonConverter
- Log event datetime with.Net Core Console logger
- How do I get .NET Core projects to copy NuGet references to the build output?
- Net Core / Angular CORS error on some Api calls but not others
- Unable to query NTLM-protected APIs from within a Docker Container
- HttpClient PostAsync not working but can post request by Postman
- Restoring nuget packages of a solution in .net Rider IDE: Failed to download package `x` The HTTP request to GET `x` has timedout after 100000ms
- Prevent .NET BackgroundService running as Windows Service from being stopped
- The entity type 'EntityQueryable<Entrys>' was not found. Ensure that the entity type has been added to the model
- When TwoFactorEnabled is activated, I get an error during login (implementation with Identity)
- An assembly specified in the application dependencies manifest (...) was not found
- How to configure JSON deserialization options in .NET minimal API project
- Blazor: Implementing 404 not found page