Evolving a legacy ASP.NET application to the modern ASP.NET stack
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
Blog 1 - Introduction.md
Blog 2 - Evaluating the Code.md
Blog 3 - Moving to a Web Application Project.md
Blog 4 - Dealing with Dependencies.md
Blog 4.1 - Updating Logging.md
Blog 4.2 - Updating Search.md
Blog 4.3 - Updating Pop3 Integration.md
Blog 4.4 - Updating jQuery.md
Blog 4.5 - Updating CKEditor.md
Blog 5 - Security.md
Blog 5.1 - SQL Injection.md
Blog 5.2 - Password Hashing.md
Blog 5.3 - Validating Redirects and Forward.md
Blog 5.4 - Cross Site Scripting.md
Blog 5.5 - Revealing Sensitive Data.md
Blog 5.6 - Cookie Authentication.md
Blog 6 - Application Style and Layout.md
Blog 6 - Master Pages.md
Blog 6 - Styles of WebForms.md
Blog 6 - Updating Complex Grid Components.md
Blog 6 - Updating Simple Grid Components.md
Blog 8.1 - Replacing the mega postback with Web Api.md
Blog x - Database Access.md
Blog x - JavaScript.md



Evolving a legacy ASP.NET application to the modern ASP.NET stack.

Follow us here as we evolve the original BugTracker.NET to the latest version of ASP.NET. You can contact us at @stimms or @Dave_Paquette on twitter.

Thank you to Corey Trager for his permission to use BugTracker.NET in this project.

NOTE: This project is not intended to replace the original BugTracker.NET. The purpose of this project is to show examples of how you can evolve an older ASP.NET application to make use of newer technology and modern web development practices. The version of BugTracker.NET on Source Forge is more fully featured and actively supported. We do not currently recommend that this GitHub version of BugTracker.NET is used in a production environment.

Build status