Overall, I ilke where MS is going with .NET 3.0, but there's still a lot of overlap in the current offerings. These range from multiple ORM tools (Linq and Entity Spaces) down to the dramatic differences a developer experiences when switching between C# and VB.NET. Why can't, for example, the only difference between C# and VB.NET be purely syntatical?
How can we be sure we're selecting the right overlapping technologies? Does MS strive to eliminate these conflicts? How/why are the conflicts ever created in the first place?
Another example: Does every MS product use WCF for communication? Obviously, they don't, but why not? And will they ever?
(Hi Joe, I'll get back to work now)
Copyright (c) 2008 GSP Developers Walling Info Systems | Terms Of Use | Privacy Statement