Lots of stuff out there on unit testing and mocking GAE:
http://blog.appenginefan.com/2008/06/unit-tests-for-google-app-engine-apps.html
Unit Testing Google App Engine Applications - Blogs at Near Infinity
Got this working locally:
http://appengine-cookbook.appspot.com/recipe/app-engine-test-runner/
Wednesday, May 20, 2009
Rake and .NET: The Story Continues
So many new tools to help there is no time to code!
Sounds like Rake, NDepend and NCover in particular will be useful. I'd like to see what NDepend makes of our legacy code base.
Tobin Harris blogs about this and other things here - Rake and .NET: The Story Continues
Sounds like Rake, NDepend and NCover in particular will be useful. I'd like to see what NDepend makes of our legacy code base.
Tobin Harris blogs about this and other things here - Rake and .NET: The Story Continues
Friday, May 15, 2009
Welcome to Shelfari! Read, Share, Explore! - Shelfari
This could be a good way of building up a recommended reading list for Agile Yorkshire as GoodReads doesn't seem to do what we want.
Welcome to Shelfari! Read, Share, Explore! - Shelfari
Welcome to Shelfari! Read, Share, Explore! - Shelfari
Friday, April 24, 2009
Visual Studio Remote Debugging Setup
Setting up remote debugging on our UAT environment turned out to be pretty straight forward after a false start.
The steps I followed were from here
In summary they were:
* Copy over msvsmon.exe fromMicrosoft Visual Studio 9.0\Common7\IDE\Remote Debugger\x86 on the development machine to the UAT box
* Ensure that you have a local account with the same name on both machines - we used the local administrator account which is created as a matter of course on all machines. (Note: I tried to avoid having to do this step by setting msvsmon to run in "No Authentication" mode but, although I could attach to processes, symbols were not loading from pdbs making debugging impossible - this is a known limitation when using No Authentication)
* Use "Run As" option to run VisualStudio as the local administrator account
* Use the qualifier field in Attach To Process dialog in Visual Studio to point at the remote machine. I needed to select only Native and Managed code types as T-SQL was reporting an error.
* It then just works - and very well too
The steps I followed were from here
In summary they were:
* Copy over msvsmon.exe fromMicrosoft Visual Studio 9.0\Common7\IDE\Remote Debugger\x86 on the development machine to the UAT box
* Ensure that you have a local account with the same name on both machines - we used the local administrator account which is created as a matter of course on all machines. (Note: I tried to avoid having to do this step by setting msvsmon to run in "No Authentication" mode but, although I could attach to processes, symbols were not loading from pdbs making debugging impossible - this is a known limitation when using No Authentication)
* Use "Run As" option to run VisualStudio as the local administrator account
* Use the qualifier field in Attach To Process dialog in Visual Studio to point at the remote machine. I needed to select only Native and Managed code types as T-SQL was reporting an error.
* It then just works - and very well too
Monday, April 20, 2009
InfoQ: Domain Driven Design Quickly
DDD was heavily referenced at alt.net in the north.
InfoQ: Domain Driven Design Quickly is a useful summary to DDD and a good read before launching at Eric Evans' Domain Driven Design
InfoQ: Domain Driven Design Quickly is a useful summary to DDD and a good read before launching at Eric Evans' Domain Driven Design
Friday, March 20, 2009
Subscribe to:
Posts (Atom)