Cutting edge .NET Development
Artificial Gold is a small .NET Development company using many of the latest, bleeding edge .NET Development technologies.
We specialise in being the technical partner in start-up projects or providing development teams to established projects who need new or extra development capacity in an outsourced environment.
We are experts in Test Driven Development using Continuous Integration to drive excellence in coding and delivered work.
Areas of expertise:
- - Test Driven Development
- - ASP.NET MVC
- - Continuous Integration (through TeamCity)
- - BDD Automation Testing (through Specflow/Watin)
- - Service Oriented Architecture
- - Continuous Delivery
- - Effective Development Outsourcing
Our latest project is www.restaurant-sale.co.uk and uses all of the above points.
One of the reasons a lot of developers get promoted at work is due to “knowledge of the system”. They know how everything works for a project, company or similar and therefore can perform tasks that brand new developers can’t. … Continue reading
The way I have got TeamCity working (with TeamCity version 6.5.4 I must add) is to use the TeamCity module that is provided in the psake download.
Add this to your script:
...
Import-Module "$build_dir\psake\teamcity.psm1"
#Tasks here
...
Remove-Module teamcity
#End Of File
I have a build folder that I have put the module in so that all my builds can access it.
Then it worked out of the box.
I am not using the built in NUnit runner though, I have also put the NUNit console in my build folder and then call that with each UnitTest assembly:
Task Test -depends Build {
$testAssemblies = (get-childitem $base_dir -r -i "*UnitTests.dll" -exclude "*.config" -Name | Select-string "bin")
foreach($test_asm_name in $testAssemblies) {
$full_test_assembly_name = "$base_dir\$test_asm_name"
Exec { invoke-expression "$nunitconsole_path $full_test_assembly_name" }
}
}
