Six Years Later and All The DataSets Are Gone

• All new functionality would use the new Microsoft Entity Framework EF4 instead of ADO.NET DataSets
• We would refactor 1-2 modules to use EF per release of the system

Now we can fast forward to 2017, with the release of v5.2 in March we will have retired the last of the DataSet code. It has taken:

• over 1,000,000 lines of code to be rewritten
• approximately 4,500 cups of coffee
• 1,800 searches on Stack Overflow
• 1 copy of the great O'Reilly book on Entity Framework
• 250 merge conflicts in Subversion with the dratted .EDMX file
• 85 attempts to get round the composite key issue in Entity Framework
• 120 new stored procedures

But at the end of it, we have a completely re-architected data access and business logic framework to SpiraTeam.

Of course, now we want to move to ASP.NET 4.6 and Entity Framework 6.0... but that's a story for another day!