Azure Web App supports deployment slots. Production slot is the main one and there can be a couple of others. In order to follow a principle of least privileges different slots should have different security principals for deployment.
A service principal with deployment permissions for only a dedicated slot is useful in order to limit access to production deployment.
Continue readingWeb application packaging and deployment automation using MSBuild needs the following steps:
Step 0. Server preparation is covered here How to prepare a Windows Server 2012 for web deployment
Sample solution that includes build script and configured publishing profiles can be downloaded here https://github.com/mchudinov/BuildWebDeployPackage
Continue reading
Here is a list of steps for preparation of a Windows Server 2012 for deployment of web packages or deployment from Visual Studio.
This post is about how to package .NET application for Windows into an MSI (MicroSoft Installer) package using Wix# tool in command line. Packaging process can be easily automated on continues integration server.
Generally application building workflow is simple:
Build process will be controlled by MSBuild project file and can be started from a continues integrations server.
Sample solution is available for download here https://github.com/mchudinov/PackagingMSI. Solution is compatible with Visual Studio 2013.
Automated building and versioning processes were described in my previous posts:
How to package a Mono (.NET) applications for Debian-based Linux in command line. Packaging process can be easily automated on Continues Integration Server.
Package building workflow is quite simple:
Build process will be controlled by MSBuild project file and run from a continues integrations server. MSBuild on Mono platform is substituted by xbuild utility.
Sample solution is available for download here https://github.com/mchudinov/PackagingMono. Solution is compatible with Visual Studio 2012, MonoDevelop/Xamarin Studio 5.
This is my third blogpost about automation of development workflow with Mono. Automated building and versioning were covered in my previous posts:
I use four-parts version pattern that looks like: {Major}.{Minor}.{Date (MMdd)}.{Build Number}
An example version in this format would look like: 1.7.1028.37, which breaks down into being the first major release, seventh minor release, built on 28 October, and has been the 37th build for v1.7. Every time assembly is rebuild build counter increases.
Sample solution is available for download here https://github.com/mchudinov/Versioning.
Setup: Windows – .NET 4.5, Linux – Mono 3, Mint 17 (based on Ubuntu 14). I need to build and test .NET application from command line and on CI server.
Sample solution can be downloaded from here https://github.com/mchudinov/BuildingTesting. Solution is compatible with MonoDevelop 5, Xamarin Studio 5 and Visual Studio 2012,2013,2015.
1. Building in command line
There are two standard command line building tools for .NET: MSBuild on Windows and xbuild on Linux/Mono. xbuild build files are compatible (with some exceptions) with MSBuild files.
We need at least 4 simple steps (targets as they called in MSBuild terminology) to build a .NET solution:
How to make work TeamCity Agent on Windows with Git through SSH
1. Run TeamCity Agent not from System account
2. This account must have a PuTTY session stored with SSH key
3. Server’s key must be cached by the TeamCity agent acount. Run plink in console and point plink to the target server.
plink -agent -i c:\[path-to-key]\my_teamcity_private_key.ppk bitbucket.org
Confirm key caching ‘y’
How to setup TeamCity (tested with versions 8 and 9 on Windows) with https with not valid certificate.
When PEAR installs itself on Windows it places pear.ini file in the system folder c:\Windows by default. Which sometimes needs to be changed after all. And sometimes it is not possible for some reasons (not sure why, probably a bug in PEAR installation scripts) to change this location during the installation. Then we need to change this location when PEAR is already installed and in use.
Continue reading