Continuous Integration (CI) is probably already part of your developer workflow to build your application and run unit tests after each check in. It may also be used to deploy your application to QA for testing, or run integration tests and code analysis. But where does versioning your software come in? Who is responsible for it? How and when is it done?
Configs per environment made easy
If you are working in a team with multiple developers, chances are you have different environment settings for things such as directory paths or database connection strings. One solution is for each dev to have a seperate configruation file (Web.config or App.config) which is not checked into source control. However this requires each dev to manually change their web.config when updates need to be applied (ie adding a new configuration setting).
Sneaky AppDomain is sneaky
The topic of this post is a general warning about writing code that you might need and not what you actually use right now. It focuses specifically on the performace of the C# XmlSerialixer, and the potential pitfalls of trying to handle all possible cases. Below is a basic Serialize...
Tracking exceptions made easy
During load testing last week, we had a situation where our Json requests were failing and the exceptions that were logged did not contain enough information. We suspected that the raw JSON payload was incorrect, as it was being generated by a Performance Testing Scripting tool, rather than the browser...