 |
Refer Listing To A Friend |
|
|
 |
SUGGEST .NET - Use Refactoring To Handle Multiple Versions of Classes TO A FRIEND...
If you have a friend that you would like to recommend this page to,
or if you just want to send yourself a reminder, here is the easy
way to do it!
Simply fill in the e-mail address of the person(s) you wish to tell
about .NET - Use Refactoring To Handle Multiple Versions of Classes, your name and e-mail address (so they do
not think it is spam and can reply to you directly with gracious thanks),
and click the SEND button.
If you want to, you can also enter a message that will be included
on the e-mail.
After sending the e-mail, you will be transported back to the
page you recommended!
| Resource Title: |
.NET - Use Refactoring To Handle Multiple Versions of Classes |
| URL: | [CLICK HERE] |
| Description: |
Recently, I had a requirement to put together a website that deals with taking somewhat elaborate financial surveys. While the questions and answers themselves are good candidates for being database driven, there were a large number of nuiances ranging from UI items, business rules, and calculations that just didn't fit into a database driven strategy. With this in mind, my initial strategy was to create version specific classes and reference them in version specific ASP.NET pages. Of course, this accomplished the initial requirement. However, whenever a new version needs to be implemented, I had to copy all of the ASP.NET pages and modify the references to the appropriate version specific class name. Refactoring provides a better alternative and here's how:
| |
|
|
|
|
|
