Understanding primary of.NET composition

SEnuke: Ready for action

With the release of the.NET Framework, Microsoft is taking the most significant risk in its history. Microsoft has spent millions of dollars, representing over 80 percent of its R&D budget, on planning and making this fundamental shift in its development resources in order to create a platform for the long run of application development. Microsoft has efficiently realized its vision of Windows in every PC and a PC o-n every desk-top. Its current problem is that the desk-top shows just a portion of the newest Internet universe. This cogent http://informedwithroblowe.com wiki has several engaging warnings for how to flirt with it. With the large shift brought on by the Internet and its pervasiveness in-to everything from watches to cell phones to cars, Microsoft should now shift its view of the future from a PC-centric orientation to a service-centric orientation. To read more, please consider taking a glance at: advertiser.

What exactly could be the future? From Microsoft's standpoint, the long run is delivering software as something. Instead of purchasing a shrink-wrapped installable s-olution, you will rather hire, acquire, or purchase application logic across a distributed network. Computer software may of course still be sold on store shelves. Nevertheless, most, or even all of the business logic and power of those applications will reside across a set of distributed applications using open Internetbased standards such as XML and HTTP. This construction will open extensive new possibilities for you in the process of building, making, giving, licensing, and accumulating fees for your software.

Why Microsoft.NET?

Why would you as a developer invest in understanding and learning this new base of products and services? Those of you who're practicing option designers already probably have a code base of Internet-based and Windows- applications written in Visual Basic, ASP, C++, or even a mixture of all three. If you've to address Windows API calls from C++ and Visual Basic and then integrate those calls as a COM component named by an ASP page, you will be amazed at how the.NET Frameworkbased classes provide a common approach and object type to accessing Windows services and resources. You will be further impressed at how the range of devel-opment languages is not any longer influenced by power, freedom, or support of OOP best-practices. Now all languages make to a Microsoft Intermediate Language (MSIL) and execute against a Typical Language Runtime (CLR)..