29. January 2007 00:22
I have not messed around with this too much but I have registered my PAD (Portable
Application Description) file for the Verse
Popper with www.asp-shareware.org...
Looks like I have a bit more work to do but setting up a PAD file is easy and makes
submitting your software to a "download site" very quick.
The actual Verse Popper PAD file is here:
The ASP Shareware rendering looks like this:
Bit ugly I thought!! I need to work out if there is any benifit to the end user seeing
this or if its just so generic it puts them off...
13. January 2007 03:26
Jeremy Miller has put together a great post on Orthogonal Code - I must admit, I used
to code like that! Lucky we can learn and move on... well worth the read.
10. January 2007 02:50
At some point in the unit testing game you will need to tackle the unpleasant task
of actually coding and running unit tests on the data access code. This in itself
can open a bit of a can of worms - the bigger the database, the more worms you need
to deal with. If you want a quick solution to being able to run a bunch of data
access tests that insert, update and delete data in tables - try putting a TransactionScope object
at the test fixture level. If the scope is not committed the changes are not stored,
perfect scenario for a group of unit tests.
Marcus Rosen prompted the idea and
I have been using this technique against a local copy of an MSSQL database
and have had no issues to date. It has simplified the development process in that
data does not keep disappearing due to my unit tests clearing tables and inserting
I have seen "Rollback" attributes around (such as http://weblogs.asp.net/rosherove/archive/2004/10/05/238201.aspx)
but the above solution is a one liner and requires no new libraries, and
I like a simple solution ;-)
MSDN TransacrionScope Help: