NDesk Options I started writing an argument parser without knowing about: NDesk.Options Where you have the following kind of syntax: string data = null; bool help = false; int verbose = 0; var p = new OptionSet () { { "file=", v => data = v }, { "v|verbose", v => { ++verbose } }, { "h|?|help", v => help = v != null }, }; List extra = p.Parse (args); FubuCore Since this post, there is a new option: Command line in FubuCore. Powershell If you’re using powershell it j[...]

NDesk Options I started writing an argument parser without knowing about:NDesk.Options Where you have the following kind of syntax:string data = null; bool help = false; int verbose = 0; var p = new OptionSet () { { "file=", v => data = v }, { "v|verbose", v => { ++verbose } }, { "h|?|help", v => help = v != null }, }; List extra = p.Parse (args); FubuCore Since this post, there is a new option: Command line in FubuCore.PowershellIf you're using powershell it just mig[...]

What strategies do I know of on how to test your code depending on a database? Using TransactionScope so that you can roll back any changes done by tests. Setting up a fresh database with the same schema. Using NHibernate SchemaExport(cfg).Execute to export an existing schema onto the new database. Run your migrations to set the database in the correct state. Use Code First, auto migrations or whatchamacallit call it. That is, let the ORM generate the tables and columns based upon your data objects. For [...]

What strategies do I know of on how to test your code depending on a database? Using TransactionScope so that you can roll back any changes done by tests. Setting up a fresh database with the same schema. Using NHibernate SchemaExport(cfg).Execute to export an existing schema onto the new database. Run your migrations to set the database in the correct state. Use Code First, auto migrations or whatchamacallit call it. That is, let the ORM generate the tables and columns based u[...]

Keep solutions simple and think about your deliverables Chad Myers at Los Techies tries to get a discussion about why it’s bad to have to many projects: Project anti-pattern: Many projects in a Visual Studio Solution File Some of the consideration is about build performance. He is referencing microsoft blog posts… I know the lure of getting to drink coffee while waiting for builds, but you’re not getting paid for coffee ;) There is an article on O’Reilly about the cost of long development cycles: Dead Tim[...]