| |
browse.develop.com
Browse.develop.com is a community that was established to collect and
organize valuable web information. Our technical staff have selected and
indexed information and courses that they feel will help you stay
current on best practices across the SDLC.
|
4 Articles match "Anti Pattern","Unit Testing"
| Related DevelopMentor Courses | MORE | | Use Common Instance Factory to Abstract Away the Dependency Injection Container lot of DI-specific code is needed for unit tests, where there is extensive mocking, and advanced features of a DI container such as Ninject come in handy. When searching for a way to abstract away the DI container, the first solution I examined was the Common Service Locator , built by Microsoft’s Patterns and Practices group back in 2008 with the source code posted on CodePlex. In his article, Inversion of Control Containers and the Dependency Injection Pattern , Martin Fowler describes some of the weaknesses of the service locator anti-pattern. DevelopMentor Courses - Wednesday, May 23, 2012 Guerrilla.NET (US) Training MVVM : Learn advanced WPF / Silverlight design patterns and techniques including MVVM (Model-View-ViewModel). Learn about IaaS, PaaS, and design patterns for scalable cloud-based applications. DI/IoC : Use powerful OO design patterns and techniques to build loosely-coupled, testable, and maintainable applications including Dependency Injection (DI), Inversion of Control (IoC), and unit testing. You learn a myriad of patterns and best practices, and you get hands-on experience developing applications using Visual Studio 2010. dynamic typing from C# 4.0, DevelopMentor Courses - Tuesday, March 1, 2011 Decouple WCF Services from their DI Container with Common Instance Factory Unlike the Common Service Locator (CSL), the Common Instance Factory (CIF) discourages the service location anti-pattern by using the abstract factory design pattern. If you are careful to register your types early in the startup of your application and avoid referencing the DI container from within your types (which is where the service location ant-pattern rears its ugly head), then selecting a DI container and sticking with it might be perfectly appropriate. null ) { disposable.Dispose(); } } } } }. To get CIF, download the NuGet CIF packages. Enjoy. DevelopMentor Courses - Saturday, May 26, 2012 |
3 Articles match "Anti Pattern","Unit Testing"
| The Latest from DevelopMentor | MORE | | Decouple WCF Services from their DI Container with Common Instance Factory Unlike the Common Service Locator (CSL), the Common Instance Factory (CIF) discourages the service location anti-pattern by using the abstract factory design pattern. If you are careful to register your types early in the startup of your application and avoid referencing the DI container from within your types (which is where the service location ant-pattern rears its ugly head), then selecting a DI container and sticking with it might be perfectly appropriate. null ) { disposable.Dispose(); } } } } }. To get CIF, download the NuGet CIF packages. Enjoy. DevelopMentor Courses - Saturday, May 26, 2012 Use Common Instance Factory to Abstract Away the Dependency Injection Container lot of DI-specific code is needed for unit tests, where there is extensive mocking, and advanced features of a DI container such as Ninject come in handy. When searching for a way to abstract away the DI container, the first solution I examined was the Common Service Locator , built by Microsoft’s Patterns and Practices group back in 2008 with the source code posted on CodePlex. In his article, Inversion of Control Containers and the Dependency Injection Pattern , Martin Fowler describes some of the weaknesses of the service locator anti-pattern. DevelopMentor Courses - Wednesday, May 23, 2012 Tackling the Problem of Modal Dialogs in MVVM Popping up a dialog, such as a MessageBox or a ChildWindow, from the view-model is an anti-pattern that violates the separation of concerns that exists between the view and the view-model. It is notoriously difficult to test the user interface by simulating things like button clicks and mouse overs. Encapsulating functionality into a view-model means that you can test it independently of the view, which is just another consumer of the view-model. One of the main benefits of MVVM is better application maintainability. Another benefit is testability. null). Tony and Zuzana's World - Friday, January 28, 2011 | -
| The Best from DevelopMentor | MORE | - Use Common Instance Factory to Abstract Away the Dependency Injection Container
lot of DI-specific code is needed for unit tests, where there is extensive mocking, and advanced features of a DI container such as Ninject come in handy. When searching for a way to abstract away the DI container, the first solution I examined was the Common Service Locator , built by Microsoft’s Patterns and Practices group back in 2008 with the source code posted on CodePlex. In his article, Inversion of Control Containers and the Dependency Injection Pattern , Martin Fowler describes some of the weaknesses of the service locator anti-pattern. DevelopMentor Courses - Wednesday, May 23, 2012 - Tackling the Problem of Modal Dialogs in MVVM
Popping up a dialog, such as a MessageBox or a ChildWindow, from the view-model is an anti-pattern that violates the separation of concerns that exists between the view and the view-model. It is notoriously difficult to test the user interface by simulating things like button clicks and mouse overs. Encapsulating functionality into a view-model means that you can test it independently of the view, which is just another consumer of the view-model. One of the main benefits of MVVM is better application maintainability. Another benefit is testability. null). Tony and Zuzana's World - Friday, January 28, 2011 - Decouple WCF Services from their DI Container with Common Instance Factory
Unlike the Common Service Locator (CSL), the Common Instance Factory (CIF) discourages the service location anti-pattern by using the abstract factory design pattern. If you are careful to register your types early in the startup of your application and avoid referencing the DI container from within your types (which is where the service location ant-pattern rears its ugly head), then selecting a DI container and sticking with it might be perfectly appropriate. null ) { disposable.Dispose(); } } } } }. To get CIF, download the NuGet CIF packages. Enjoy. DevelopMentor Courses - Saturday, May 26, 2012 %>
| |   |
