MICROSOFT.
NET
PRESENTATION BY
NEHA KUMARI
WHAT IS .NET?
• Microsoft® .NET is a set of Microsoft software technologies for connecting
information, people, systems, and devices
• It is a device and platform independent distributed computing model based on
Web Services (which are in turn based on open XML communication technology),
and consists of
• a software platform for building .NET experiences
• a programming model and tools to build and integrate XML Web services
• a set of programmable XML Web services
• a way to enable users to interact with a broad range of smart devices via
the Web, while ensuring that the user, rather than the application, controls
the interaction .
• .NET is all about creation, consumption and delivery of Web Services
WHAT IS WEB SERVICES
Client to Client
- Clients can use XML Web Services to
communicate data
Client to Server
- Clients can send data to and receive data from
servers.
Server to Server
- Servers can share data with each other.
Service to Service
- web services can work together.
WHAT ARE THE COMPONENTS OF .NET?
.NET EXPERIENCE
.NET Experiences are XML web services that allow you to access information
across the internet in an integrated way
Products transitioning into the .NET experiences are:
MSN Website
Visual Studio .NET Website
Passport Website
.NET CLIENTS
Clients are PCs, handheld computers,
Tablet PCs, game consoles (Xbox), smart
phones …
All of them use XML Web Services
.NET client software includes
Windows CE
Windows XP
Windows Embedded
Windows 2000
.NET SERVICES
XML Web Services
Offer a direct means for applications to
interact with other applications
First set of XML Web Services developed
are called .NET My Services (“HailStorm”)
.NET TOOLS
Microsoft Visual Studio .NET and Microsoft .NET Framework
supplies complete solution for developers to build, deploy and run
XML services
Visual Studio .NET is the next generation of Microsoft’s popular
multi-language development tool built especially for .NET
Enhances existing languages like Visual Basic with new OO
features
Introduces C#
.NET ARCHITECTURE
ARCHITECTURE EXPLAINED
• Web Services
• Top layer provides .NET users with Web Services for e-commerce and business to business
applications
• Frameworks and Libraries
• ASP.NET for developing smart web pages
• ADO.NET which is an XML based improvement for databases and object relational processing
• Interchange Standards
• Platform independent means of exchanging objects
• SOAP (Simple Object Access Protocol)
• WSDL (Web Services Description Language)
ARCHITECTURE EXPLAINED
• Development Environment
• Visual Studio .NET
• Visual C++, Visual BASIC, Visual C#
• Component Model
• Derived from original component based development: CORBA, J2EE, COM
• .NET allows building “assemblies” consisting of a number of classes with well
defined interface
• IDL absent in .NET
COMMON LANGUAGE RUNTIME
• The CLR is at the core of the .NET platform - the execution engine. A unifying
framework for designing, developing, deploying, and executing distributed
components and applications.
• Manages memory, thread execution, type safety verification and garbage
collection.
• Performs compilation (Just In-time Compiler)
• Makes use of a new common type system capable of expressing the
semantics of most modern programming languages. The common type system
defines a standard set of types and rules for creating new types.
MICROSOFT C#
• A modern, object-oriented programming language built from the
ground up to exploit the power of XML-based Web services on the
.NET platform.
• The main design goal of C# was simplicity rather than pure power.
• Features of C#
Simplicity Type Safety
Consistency Version Control
Modernity Compatibility
Object Orientation Flexibility
CONCLUSION
• . Net creates a new concept, “the Internet Operating System”.
• . Net allows cross-platform development to an extent not before possible.
• . Net web services can be integrated into existing distributed object
technologies today by replacing their RPC wire protocol with SOAP .
• Large-scale distributed application development and deployment become
possible on a level that presents major difficulties today.
• Stricter versioning policies help to ensure greater stability during upgrades,
even in shared libraries.
• "Software as a service" - a subscription model for application deployment -
becomes a feasible option
