publish-profiles

We have an ASP.NET Core site running on our test server that we would like to auto-deploy by XCopy to our IIS web server as we do our current apps, where I already have the site running. I've added a publish profile that packages the site to a "publish-local" directory within the solution. Whenever I try to copy over the existing site, all DLLs are being used by another process, presumably Kestrel, so I am forced to deploy to a sibling directory and re-map IIS to look at the sibling. How does one update a running ASP.NET Core site without having to manually intervene and stop either the

I have the following setup in a Visual Studio 2013 ASP.NET Web API 2 project. Web.Develop.config web transform to set an app settings key value Web.Release.config web transform to remove an app settings key Develop.pubxml to map to the Web.Develop.config transform Release.pubxml to map to the Web.Release.config transform Details for each are found below. <!-- Web.Develop.config (Web Config Transform) --> <appSettings> <add key="ReportInputPath" value="DevelopPath" xdt:Transform="SetAttributes" xdt:Locator="Match(key)" /> </appSettings> <!-- Web.Release.config (Web Config Transform) -->

I am using Visual Studio Online to deploy my project continuously after the CI build pass. However I have to use a publish profile to build the production web.config transform so that the deployed website will be using the production DB instead of dev DB. I have followed Scott Hanselman's blog post to add the MSBuild arguments in the CI build definition. My arguments are like this: /p:DeployOnBuild=true /p:PublishProfile=[publish profile name] /p:AllowUntrustedCertificate=true /p:UserName=[credentials obtained from Azure Website portal] /p:Password=[from the portal as well] It seems working,

Using Visual Studio 2013 I have a set of 8 SSDT projects that can all be deployed to several distinct environments. The advanced publish settings for each project, however, are meant to be identical. At present I have created a distinct publish profile for each environment, meaning I have ~20 publish profiles all using the exact same settings but different connection strings. Tweaking the publish settings (which happens with some regularity as I am still a bit new to SSDT) for my databases is most annoying, but I have yet to find a way around this as I am unable to apply transforms to publish