.NET Omid Darroudi

.NET Vision – The Next Generation IT applications in the future will use the internet more and more .NET has a central role in the Microsoft strategy to integrate devices and web services over the internet. .NET creates new opportunities to communicate or process data ‘any time, anywhere and on any device’

Defining the Basic Elements of the .NET platform Microsoft .NET is a set of Microsoft software technologies for connecting information, systems, and devices. It enables a high level of software integration through the use of Web services small building-block applications that connect to each other as well as to other, larger applications over the Internet.

The Components of Microsoft .NET-Connected Software The .NET Microsoft platform provides the ability to quickly and reliably build, host, deploy, and utilize connected solutions using Web services The .NET platform consists of the following five things: Clients XML-web services Servers Tools.

The Components of Microsoft .NET-Connected Software “Smart" client application software and operating systems enable PCs and other smart computing devices to act on Web services, allowing anywhere, anytime access to information. Microsoft and others are developing a core set Web services—from authentication to calendaring—that can be combined with other Web services or used directly with smart client applications. Microsoft provides the best server infrastructure for deploying and managing Web services. Microsoft Visual Studio .NET and the Microsoft .NET Framework are a complete solution for developers to build, deploy, and run Web services.

.NET Architecture So what is .NET? An open language platform for enterprise and Web development. The .NET platform’s overall structure consists of six layers 1) Web Services 2) Frameworks and libraries: ASP.NET, ADO.NET, Window Forms 3) Interchange standards: SOAP, WSDL | Common development tools: Visual Studio.Net 4) Component Model 5) Object Model and Common Language Specification (CLS) 6) Common Language Runtime (CLR)

Web Services Web services are small reusable applications written in XML XML is a universal language for data exchange They allow data to be communicated across the internet (or internal Intranet) between otherwise unconnected sources that are enabled to host or act on them, for example: Client to client: ‘Smart’ clients or devices can host and apply XML web services that allow data to be shared anywhere, any time Client to server: XML web services can share data from a server application to a desktop or mobile computing device via the internet Server to server: XML web services provide a common interface between existing applications within an environment of Independent servers. Service to service: XML web services can work together in sequence to create a more complex data operation. You can see this like components that are used with each other to create a new application.

XML- Web services: A universal language XML-Web services make it possible for applications to communicate via the internet, notwithstanding the operating system or programming language. Platform independant Defined by open standard configurations Applications grant access to XML web services via standard web protocols like HTTP, XML and SOAP, independent of the way each XML-web service is implemented With XML-web services, applications can not only exchange data, but also call functions throughout other applications

Advantages Web Services Human intervention not required Fast Efficient, Reliable

The .NET platform’s overall structure consists of six layers 1) Web Services 2) Frameworks and libraries: ASP.NET, ADO.NET, Window Forms 3) Interchange standards: SOAP, WSDL | Common development tools: Visual Studio.Net 4) Component Model 5) Object Model and Common Language Specification (CLS) 6) Common Language Runtime (CLR)

Frameworks and libraries A set of frameworks and libraries provides the most immediately attractive aspect for developers .NET contains thousands of reusable components. This makes building real world Web applications fast and easy These include ASP.NET, active server pages for developing smart Web Sites and services for database and object-relational processing; and Windows Forms for graphics

ASP.NET HTML-like style of declarative programming Displaying data, validating user input, and uploading files are all amazingly easy with just the use of the existing libraries ASP.NET removes the distinction between traditional software development and Web development work in all browsers and have great language flexibility which allows every programmer in a different language to use it ASP.NET makes exposing and calling XML Web Services simple

The .NET platform’s overall structure consists of six layers 1) Web Services 2) Frameworks and libraries: ASP.NET, ADO.NET, Window Forms 3) Interchange standards: SOAP, WSDL | Common development tools: Visual Studio.Net 4) Component Model 5) Object Model and Common Language Specification (CLS) 6) Common Language Runtime (CLR)

Interchange standards and development tools Standards for Microsoft .NET Because of the standardisation of technologies which allow software to communicate with each other and exchange data, solutions become possible which conclude more platforms Standards for describing data and interaction, like HTML, make solutions possible for a bigger reach than would be possible with only company specific standards. The .NET platform is build on a technology fundament from industry standards The most important technology standards with regard to .NET XML SOAP UDDI WDSL CLI and C#

XML The eXtensible Markup Language is the universal graduation for structured data on the web XML is a sequence of rules for designing a text graduation for data, in such particular way that it creates files which can be easily generated and read by a computer and which are platform independent Possible for XML-web services to exchange the data on the fly

SOAP The Simple Object Access Protocol (SOAP) is based on XML. If we compare the interactions between XML-web services with a telephone call, then XML describes the things the applications say to each other during their call, and SOAP on the other hand describes how they talk over the telephone. How requests will be handled.

UDDI Universal Description, Discovery and Integration foresees in a directory of XML-web services, where you can find companies which offer it. If XML describes the contents of a conversation and SOAP the rules, then UDDI is the telephone book.

WSDL The Web Services Description Language foresees in a standard way to describe which functions a specific XML-web service provides and which arguments must be passed to call these functions.

C# en de CLI C# programming language that is developed for the XML-web services Common Language Infrastructure (CLI), is a subset of the Microsoft .NET framework. Because of the standard, it can be implemented on different platforms, so that software can be developed that complies to the .NET framework with a lot of different tools and on different platforms.

Development Environment The new Visual Studio.NET provides the tool of most direct use to developers: A common software development environment offering facilities for development, compilation, browsing, and debugging shared by many languages also allows third party vendors to plug in tools and compilers for other languages

The .NET platform’s overall structure consists of six layers 1) Web Services 2) Frameworks and libraries: ASP.NET, ADO.NET, Window Forms 3) Interchange standards: SOAP, WSDL | Common development tools: Visual Studio.Net 4) Component Model 5) Object Model and Common Language Specification (CLS) 6) Common Language Runtime (CLR)

Component model Standards and models for component based development CORBA COM .NET offers developers a new component model based on Object oriented concepts Benefit .NET above COM and CORBA To turn a software element into a reusable component, CORBA and COM require writing an interface description in a special Interface Description Language (IDL). .NET gets rid of IDL: You can use a .NET assembly directly as a component without any further wrapping because it is already equipped with the necessary information. The trick in removing IDL is to use interface information that is already present in the source code

Metadata Compilers for .NET-supported languages retain this information as metadata in the generated code Metadata is accessible in many ways ILDASM (intermediate language disassembler) is a graphical tool that lets you visually examine an assembly’s interface to obtain information from the metadata The metadata is also available in XML format, any application, whether it is part of .NET or not, can obtain information about components

Language Interoperability Modules written in different languages can both call each other and-in the case of classes- inherit from each other, across languages Makes it possible for developers to choose the best language for each part of an application, based on the expectation that it will smoothly and automatically interface with the other parts

The .NET platform’s overall structure consists of six layers 1) Web Services 2) Frameworks and libraries: ASP.NET, ADO.NET, Window Forms 3) Interchange standards: SOAP, WSDL | Common development tools: Visual Studio.Net 4) Component Model 5) Object Model and Common Language Specification (CLS) 6) Common Language Runtime (CLR)

Object Model Object model A set of concepts that defines the type system: what is a class, what is an object, how classes can inherit from one another, and so on The .NET object model provides a coherent set of base concepts, based on a strongly typed Object Oriented Policy. All language compilers generate an intermediate code, MSIL (Microsoft Intermediate Language), a machine language for an abstract stack oriented, object oriented machine that knows about objects, inheritance, methods, dynamic binding, and other Object Oriented concepts. When a compiler generates Microsoft Intermediate Language and associated metadata, it produces a .NET assembly that can potentially interact with other assembly.

Common Language Specification (CLS) Defines restrictions ensuring language operabilities. CLS compliance comes with three levels Supplier: others can consume what you produce Consumer: your modules can be clients of others’ producer-compliant modules Extender: your classes can inherit from classes in other languages

The .NET platform’s overall structure consists of six layers 1) Web Services 2) Frameworks and libraries: ASP.NET, ADO.NET, Window Forms 3) Interchange standards: SOAP, WSDL | Common development tools: Visual Studio.Net 4) Component Model 5) Object Model and Common Language Specification (CLS) 6) Common Language Runtime (CLR)

Common Language Runtime (CLR) .NET offers a virtual machine, the Common Language Runtime Compare it to Java Virtual Machine Execute a specific instruction set, known here as Microsoft Intermediate Language Difference with Java Virtual Machine Java provides an interpreter Microsoft Intermediate Language is meant for on the fly compilation to machine code (JIT = Just In Time Compilation)

Language interoperability Porting a compiler to .NET means, among other things, retargeting it to generate Microsoft Intermediate Language instead of machine code. The virtual machine provides a number of mechanisms useful to the implementers of all languages: signal handling, exception handling, security, memory management, garbage collection and debugging support.