SPA2005 session: Legacy .NET | |||
One-line description: | Lessons from taking over and bringing under control 0.5mloc of .NET | ||
Session format: | Case study [read about the different session types] | ||
Abstract: | This session will cover two areas; technical and management. We will describe how we took a troubled .NET project, stabilised it and finished the development. Topics will include: + .NET techniques that obfuscate. + Experiences comprehending and reading .NET code. + Killing bugs - lessons stabilising an unstable code base. + Key management approaches - how we put shape around the project to stabilise it. The attendee should leave with an understanding of how easily applications become problem legacy children, what uses of .NET can contribute to that and some basic techniques for bringing things under control. | ||
Audience background: | Have worked on a development project | ||
Benefits of participating: | Learn how to avoid your .NET becoming a legacy problem, benefit from our experiences and share your own with other interested parties. | ||
Materials provided: | None | ||
Process: | 60 minute presentation. 15 minutes questions | ||
Outputs: | |||
History: | |||
Presenters | |||
1. Jon Saunders BJSS |
2. | 3. |