Good .Net training centers in Chennai

Many of the first press reactions to Microsoft's July announcement of the .NET framework were (surprisingly for anyone who knew the technology) remarkably condescending and dismissive, tending to treat the whole thing as hype. Bob Metcalfe mocked .NET in his InfoWorld column (http://www.infoworld.com/articles/op/xml/00/07/03/000703opm
etcalfe.xml) as "a ton of vaporware that even Microsoft does not expect to ship for years". Having pledged to eat his December 1995 column if reality did not bear his prediction that the Internet would collapse in 1996, Metcalfe can now make all the predictions he wants. The truth is that .NET fundamentally changes the state of the art in software development. In fact it has a direct bearing on many of the issues we have debated in this column over the past year: the true nature of components, their relation to the classes and objects of O-O technology, how to document components, the role of Interface Definition Languages, how to combine components from different languages. It doesn't mean you have to like everything in .NET (and I will state my disagreements with some of its technical choices); but it does mean that it will be impossible to discuss issues of component-based development in the same way after the advent of this technology. This is why I am devoting this column to .NET, or more specifically - since the technology has many other contributions, ranging from Web services to database access, version management and development environments - to its effect on component issues.
Wana Get Placed as .Net developer????
Kindly contact:
Contact
Naina Mohamed
Mobile : 9382553763
Email : [email protected]
Websites: http://www.cegonsoft.com/learn-and-earn/