You have two choices. First choice is actually write the data to the Database, ideally within a transation so that it can be rolled back. You need to be able to run your Unit Tests repeatedly without leaving a mess behind. Second Choice is to Mock the Database. If you haven't designed your app from the start with this in mind then it can be tricky to retrofit. If you need more info on Mocking just ask. -Rd Hit any user to continue.

This[^] is one. I have not used it though. You can try out workflow foundation if that fits your need.

We recently looked into this exact same situation LOB => Silverlight. Watched the video on RIA and left in horror, it seems RIA not only wants the enterprise foundation but wants to put all the binding into the xaml. Note these are not mandatory but you need work arounds to avoid them. Avoiding RIA seemed a much better option. We opted for MVVM Lite with our own DAL. Never underestimate the power of human stupidity RAH

Is there any thing useful for you here[^] Yusuf May I help you?

Hi Shubhabrata, There's exist no such tool to convert ASP.NET application to a Silverlight application. ASP.NET applications & Silverlight applications are two different things and there is no relation between them. One is in .aspx and the other is in .xaml. The controls are all different for them. Thus, you can't use any tool to convert from one to another. If you want to migrate from one to the other, you have to know each technology first and then you have to manually convert them. Once migrated to Silverlight, you will get more power over your application with the help of Rich UI and StoryBoards. Don't forget to Click on [Vote] and [Good Answer] on the posts that helped you. Regards - Kunal Chowdhury | Software Developer | Chennai | India | My Blog | My Tweets | Silverlight Tutorial

What is the exception? Copy the exception type, the exception message, and the line of code associated with that exception so we can help. I can say, that the reason you are getting an exception later on is solely due to the problem that is created within your static constructor. Any object that throws an exception while being constructed cannot be used anywhere in the code. -Jeff

Interesting question. According to the GoF, the purpose of a singleton is to "ensure a class has only one instance, and provide a global point of access to it." Your second example has no instance, its just a collection of static methods and hence we couldn't get a reference to it. Microsoft has a best practice with regard to singletons - they say it should be implemented as follows - a thread safe lazy implementation public class Singleton { // private constructor to prevent instantiation private Singleton() {} private static volatile Singleton \_singleton; private static object \_lock = new object(); public static Singleton Value { get { if (\_singleton == null) { lock(\_lock); { if (\_singleton == null) \_singleton = new Singleton(); } } return \_singleton; } } } Regards, Rob Philpott.

Hi there, I guess you might be interested in some articles: ASP.NET Web Services or .NET Remoting: How to Choose[^] Performance Comparison: .NET Remoting vs. ASP.NET Web Services[^]

Shubhabrata Mohanty wrote: ASP.NET Cache object or Using Static Variables The Static variables should be faster IMO. Shubhabrata Mohanty wrote: If static variables are faster then why should we use Cache object? Is it only for setting expiration? Yes, the Cache supports to set the expire time or dependency for the item saved in the Cache. Shubhabrata Mohanty wrote: Is there any different between Application object and Static variables? Again, the static variables are faster. For more information, you can see Improving ASP.NET Performance[^]

A better question would be, what are you trying to do anyway? There may be better ways to solve your problem. For example, if you don't want event handlers to fire under a certain condition, use a state variable and don't run all or the brunt of your event handler code if that state variable is set. If you have a lot of code to synchronize you might use Monitor.TryEnter against a singleton used by the entire application. This posting is provided "AS IS" with no warranties, and confers no rights. Software Design Engineer Developer Division Customer Product-lifecycle Experience Microsoft [My Articles] [My Blog]

That only gives the Delegate type, but how to actually get the reference to the Delegate?

Actually the problem is that I don't know what all the EventHandlers each Derived Form is using. So it's become very difficult to remove all EventHandlers from each Derived Form manually. I just want to know if there is any way to remove all EventHandlers for all controls in the Form so that I can loop through all controls in the Form and Remove it in Base Form class. Please Help.