blueprint

.Net technologies blueprint: .NET frameworks & IDE

1.0 obsolete
1.1 VS 2003
  * win 2003 has built in

2.0 (sp1) VS 2005/8/(?)10
3.0 WPF, WCF, WF, VS 2005/8/(?)10
3.5 (sp1) Linq, C#3.5, Entity fw..., sp1: System.Web.Abstraction, Sys.Web.Routing. VS 2008/(?)10
  * win 2008 has built in
  * the same runtime
  * upgrade is convinient (not risky , backward compat)

4.0 VS 2010
  * new machine.config, mscorlib, runtime
  * C#4.0, ASP.NET 4.0
  * upgrade might be risky, requeres changes in web.config.

mono
  * integration with VS
  * MonoDev
  * The Mono API today is somewhere in between .NET 2.0 and .NET 3.5,
  * cross platform

 

 

igorz 20/01/2010 - 11:15
.NET, .NET frameworks, blueprint, IDE
.NET Technologies Blueprint: Business Object Frameworks – Dependency Injection

1. Traditional Object Oriented Programming encourages us to use classes for our business objects. Dependency Injection frameworks take us a few steps  forward down these roads.  Always use interface to create Business Objects models. This ensures implementation may be changed at later stage regardless of initial code. Ensures better decupling between software layers

 

dror 05/01/2010 - 12:54
.NET, .NET, blueprint, business objects, Dependency Injection, FrameWork
Syndicate content