Web 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
- Configure solution build profiles
- Configure transformation of web.config file
- Configure publishing profiles
- Create a web deployment package with MSBuild script
- Run deployment from command line
Sample solution that includes build script and configured publishing profiles can be downloaded here https://github.com/mchudinov/BuildWebDeployPackage
A multilingual site should translate the following:
- Date and time formatting
- Text resources: lables, buttons, validation messages, tooltips
It must be easy to switch languages.
It should be relatively easy to add more languages.
An example ASP.NET MVC 5 project can be downloaded here https://github.com/mchudinov/AspMvc5Multilingual
LocalDB is an instance of SQL Express. It is easy to use it in development from Visual Studio. I want to have localdb database files included into Visual Studio solution for easy connect to database wherever I work.
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:
- Assign a version number to an assembly
- Build binaries
- Copy binaries to package folder and build msi-package with the same version as assembly
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:
Here is a simple application that will log to console and syslog demon. On Windows platform we can use free edition of Kiwi Syslog Server. On Linux application will use both local and remote syslog. As a logger library I use NLog.
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:
- Assign a version number to a .NET assembly code
- Build binaries
- Copy binaries to package folder and build deb-package with the same version as an assembly
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: