Why should I use MSBuild instead of Visual Studio Solution files?
We’re using TeamCity for continuous integration and it’s building our releases via the solution file (.sln). I’ve used Makefiles in the past for various systems but never msbuild (which I’ve heard is sorta like Makefiles + XML mashup). I’ve seen many posts on how to use msbuild directly instead of the solution files but I don’t see a very clear answer on why to do it.
Handling generated files in a Visual Studio Project
I have a Visual Studio Project that is using a MSBuild task to generate some code files. (The basis are xml files, and the generated code is quite lengthy, but noting special, just a lot of boilerplate.)
MSBuild Net 8 property for build as single file
I am using Azure DevOps Server (on Prem) and am trying to build a solution (windows service, C#) for Net 8.0.204.
MSBuild is not deploying to an internal server from a GitHub self-hosted runner
I’m trying to get a self-hosted runner which I installed on one of our internal servers and configured with the repository we have in our GitHub organization, to deploy to another internal server. The code base is an old ASP.NET app currently using .NET Framework 4.5.2. For that reason, I’m using MSBuild in the GitHub workflow. I’ve been following a GitHub Gist I found that describes using MSBuild in the YAML file, specifically this section. However, that section uses placeholders, so I’ve been looking elsewhere to try and see how to specify parameters such as MSDeployServiceURL. I found this SO post with an answer that discussed that. However, the GitHub workflow still doesn’t publish to the other server. And there’s no errors, so I don’t know what’s wrong. Here’s some code snippet from the YAML file: