Comments on: Real singleton approach in WPF application http://khason.net/dev/read-singleton-approach-in-wpf-application/ Take care of the sense, and the sounds will take care of themselves. Tue, 07 Feb 2012 22:44:08 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: as http://khason.net/dev/read-singleton-approach-in-wpf-application/comment-page-1/#comment-4424 as Fri, 24 Jun 2011 08:57:49 +0000 http://khason.net/dev/read-singleton-approach-in-wpf-application/#comment-4424 alert(1); alert(1);

]]> By: as http://khason.net/dev/read-singleton-approach-in-wpf-application/comment-page-1/#comment-4423 as Fri, 24 Jun 2011 08:57:01 +0000 http://khason.net/dev/read-singleton-approach-in-wpf-application/#comment-4423 8) 8)

]]> By: Sly Gryphon http://khason.net/dev/read-singleton-approach-in-wpf-application/comment-page-1/#comment-3400 Sly Gryphon Thu, 22 Oct 2009 10:31:59 +0000 http://khason.net/dev/read-singleton-approach-in-wpf-application/#comment-3400 @MF You need to read the original "Design Patterns" book by the GoF (Gamma, etc). Some of the _benefits_ of using the Singleton (as described in that classic book on patterns) is that you _can_ use different instances for different reasons. In fact, using the Singleton pattern actually makes unit testing easy! (In unit tests the accessor returns a mock or test version of the class, whilst the real code returns the real instance.) @MF You need to read the original “Design Patterns” book by the GoF (Gamma, etc).

Some of the _benefits_ of using the Singleton (as described in that classic book on patterns) is that you _can_ use different instances for different reasons.

In fact, using the Singleton pattern actually makes unit testing easy!

(In unit tests the accessor returns a mock or test version of the class, whilst the real code returns the real instance.)

]]> By: Tamir http://khason.net/dev/read-singleton-approach-in-wpf-application/comment-page-1/#comment-3254 Tamir Tue, 25 Aug 2009 06:56:30 +0000 http://khason.net/dev/read-singleton-approach-in-wpf-application/#comment-3254 @MF sometimes you have no chance other than using Singletons @Luis it's because my singleton object is not freezable it's only source for given dependency objects. @MF sometimes you have no chance other than using Singletons

@Luis it’s because my singleton object is not freezable it’s only source for given dependency objects.

]]> By: Luis Guerrero http://khason.net/dev/read-singleton-approach-in-wpf-application/comment-page-1/#comment-3253 Luis Guerrero Tue, 25 Aug 2009 00:18:23 +0000 http://khason.net/dev/read-singleton-approach-in-wpf-application/#comment-3253 And why don't call Freeze() method of Freezable objects, it will detached from dispatcher and you can use in every control you like and more faster, because MIL composition engine know about freezable objets. Luis. And why don’t call Freeze() method of Freezable objects, it will detached from dispatcher and you can use in every control you like and more faster, because MIL composition engine know about freezable objets.

Luis.

]]> By: MF http://khason.net/dev/read-singleton-approach-in-wpf-application/comment-page-1/#comment-3252 MF Mon, 24 Aug 2009 23:13:56 +0000 http://khason.net/dev/read-singleton-approach-in-wpf-application/#comment-3252 Be careful using singletons (they are an anti-pattern) they seem useful but they become painful later on when you want to do unit testing or use a different instance for some other reason. Use IoC (DI) instead Be careful using singletons (they are an anti-pattern) they seem useful but they become painful later on when you want to do unit testing or use a different instance for some other reason. Use IoC (DI) instead

]]>