I have a website and a console application that work together.
The website is published on any of ~ 10 different servers depending on the publication profile. For production, this MSDeploy, but for Dev / Test / UAT / etc ... is a simple copy of the UNC file path.
I would like to be able to publish CLIs just as easily (at least on "local" servers). I want to click "Publish", select "Profile / Server" and compile it and copy the output to the bin folder on \\Server\ApplicationName
I know that I could complete the โCopy as post-buildโ step, but I donโt always want to make a copy and I definitely donโt always want it to be in the same place.
The publishing options that exist for Console / WinForms applications seem to be centered around a 1-click publication, which is not what I need (I don't want the application to call home, looking for new versions every time, I want to explicitly click on a specific version to a specific server).
I know that if the application is running while trying to publish, there will be problems.
Is this achievable?
Basic source share