Archives
-
Building AssemblyInfo for BizTalk with NAnt
All assemblies deployed into production are versioned. My personal preference is to achieve that with build scripts, ensuring that build number, code revision, minor and major versions are all inserted. AssemblyInfo.cs is the file that normally contains that information. I normally generate a dummy AssemblyInfo file in the build project and reference that from the project(s). This way, when building with scripts, we can generate dynamic AssemblyInfo.cs file and overwrite the link. The link is a one way link, nothing is updated in the build project. And since link is just a reference, nothing is modified from the repository point of view. NAnt has <asmInfo> task that does all the job. Except that for BizTalk its not straight forward process (of course, how could it be).
-
When Whiteboard Is Not Available
You use wall :)
-
Change MsBuild Script with NAnt XmlPoke
For automated deployments of BizTalk application, I am using MsBuild scripts packaged with compiled BizTalk artifacts. Build scripts are in NAnt. I wanted from NAnt build script to update MsBuild deployment script.
-
Testing BizTalk Custom Pipeline
There are a few ways to test BizTalk Custom Pipelines out there. If you want automatically execute pipeline on input and verify it’s not exploding, you can leverage TestableSendPipeline coming along with BT projects.
-
Automated Builds and Deployment for BizTalk
Automated builds are an essential part of Continuous Integration. Definition commonly found is
-
Digitally Imported
If you are a fan of electronic music, and happen to find yourself in a place where there’s not a single radio station playing electronic music – this is the URL to remember: http://www.di.fm/