Search - Articles
DevASP.NET for ASP.NET, VB.NET, XML and C# (C-Sharp) Developers Sunday, December 17, 2017

Dev Articles
Search Directory
SQL Server

Home > Search > Articles & Samples > Visual Studio 2005 > Design and Strategies
Using AOP to Implement Functional Requirements - Closing Dirty Forms        
Total Hits: 368  |  Today: 0 Author: alanliu0110, fendyzhong.       Rating:  
Read Reviews | Write Review | Your Rating: 

I have seen or done so several times, for my school projects, at work and etc. Recently, I did it again for my little fun project and got bitten by it. First, I forgot to set the flag somewhere sometimes. Second, the "dirty" code was so scattered that the flag got set/reset accidently and the YesNo dialog popped up surprisingly. Third, the dirty flag doesn't reflect the definition of dirty data. If user undoes changes, the data is not dirty but the applicaiton pops up the YesNo dialog. Last, and the worst, if I need the same capability in another Form, I have to write the same code again. It results in duplicate code. In addition, different ..

What's New at DevASP.Net
04/23  A Debug Stopwatch
04/23  The virtual bool bug
04/23  Application.EnableVisualStyles Bu..
04/23  The Process Async Reader Bug
04/23  Load a DBF into a DataTable
04/23  Weird Error: Unable to Validate D..
04/23  ASP.NET and jQuery to the Max
04/23  Fixing Error: "SetConfigurationSe..
04/23  Generics in .NET
04/23  Builder Design Pattern
04/23  Abstract Factory Design Pattern
04/23  Prototype Design Pattern
04/23  Bridge Design Pattern
04/23  Composite Design Pattern
04/23  Decorator Design Pattern
04/23  Validation in .NET Framework 4
04/23  Windows Phone 7: How to Encrypt C..
04/23  Text box to accept only number
04/23  Using the Raw Input API to Proces..
04/23  Study EVM (Earned Value Managemen..

DevASP.Net - Disclaimer - Privacy