Posted by Eric Polerecky in ASP.NET, AutoDeploy.NET, GitHub, MEF, Unity, autodeploy, fluent interfaceJul 20th, 2009 | No Comments
First; When I pushed to GitHub I decided to rename the project to AutoDeploy.NET.
In the hopes of keeping my sanity and in the context of working in an organization that strictly follows a 50+ page “release management handbook” I started working on AutoDeploy.NET; a deployment automation tool.
As with all my personal projects I took an academic approach to the design and implementation. Instead of building an entire application I created a class library (dll) and used a few 3rd party libraries that I was either unfamiliar.
Class Library
My thought here is that by just creating the class library...
Posted by Eric Polerecky in ASP.NET, ASP.NET MVC, ASP.NET MVC Futures, AutoMapper, CruiseControl.NET, Entity Framework, Facebox, Feedreader, FxCop, LINQPad, MSTest, SVN, SourceMonitor, Spark, Unity, Visual Studio, WebSVN, iTextSharp, jQueryJun 1st, 2009 | No Comments
Most of my work so far this year has been with one client. This client was a Java shop for quite some time and is pretty green to Microsoft. Also, they don’t seem to ever have had real success with building enterprise class systems. That’s not to say that they haven’t wrote very large and very complex systems. They have done it all with either the bare minimum in tooling or a incorrect implementation of the tooling.
In fact; one of their primary reasons for moving to .NET was to perform a tooling reset. They decided it was too hard to use technology like OR/M, DI, Messaging, and MVC. The...