NET Framework Introduction Nouman Qureshi [email protected]

.NET Framework Introduction

Nouman Qureshi [email protected]

• Support Structure



• Support Structure.

• Software also designs or develop before framework , but there we should have to do extra efforts .





• Minimum Libraries Available.






• Garbage Collection , Exception Handling , Mouse Routine etc.

• Wheel is Invent. !






• Garbage Collection , Exception Handling , Mouse Routine etc.

• Applications was thick (thousand’s lines of code).



• No Layer Between App and OS.




• Minimum libraries was available we built maximum

• Like in C/C++ Mouse Programming etc

• Now In framework such type of libraries are from very first day.



• Before Framework your application was thick and libraries was thin.

• Because minimum libraries was available and maximum you should develop.

• For example to enable mouse in C/C++ we code thousands of lines of code. So your application size will be large.



• Also if two developer are developing then they both have to define their own code for mouse no one can use code of other.

• But Now If framework is available your application will be thin.

• Before framework your application communicate OS directly.

• Components of framework are highly integrated with each other.


Prepared By : Syed Noman Ali

• Garbage Collection , Exception Handling , Mouse Routine are available from first day.

• Now you don’t to have to invent wheel , wheel is available you just use wheel.

• To Run Application You required Framework.



• Framework platform independent, language independent , tool independent .

• Different framework are available in different languages.

• .NET New and Enhanced Technology.



• Means a Framework which is new and also enhanced, Enhanced means which was available before.

• .Net Framework Software is a software component, which install on Os.

• . For Internet.

• Framework Has Different Components.



• Framework platform independent, language independent , tool independent .

• Different framework are available in different languages.

• .NET New and Enhanced Technology.



• Means a Framework which is new and also enhanced, Enhanced means which was available before.

• .Net Framework Software is a software component, which install on Os.

• . For Internet.

• Framework Has Different Components.



Libraries

• Libraries are set of functionalities.

• Libraries provide functionalities.

• There are Base Class Library which provide common functionalities like DataType IO Generics.



• Frame Work Class Library has un common things like ASP.NET ADO.NET etc.

• As A whole Framework library is FCL.

• BCL is a sub set of FCL and FCL is a super set of BCL.

• Framework libraries are dynamic.



CLR • Before framework application directly communicate with your OS .

• there was no layer between OS and Application .

• Which was vulnerable. Your application can do any thing with your OS.

• If Your application crash Your OS also Crash.



• Like Blue Screen in Earlier Version of Windows.

• But Now if your application crashed , framework close your application rather than impact on OS.



• Requirement of Application or OS services which is required to your application framework (CLR) provide to your application.



• Before framework application directly communicate with your OS .

• there was no layer between OS and Application .

• Which was vulnerable. Your application can do any thing with your OS.

• Microsoft gives a layer between your application and OS.



• If Your application crash Your OS also Crash.

• Like Blue Screen in Earlier Version of Windows.

• But Now if your application crashed , framework close your application rather than impact on OS.



• Requirement of Application or OS services which is required to your application framework (CLR) provide to your application.

• CLR is live or run time environment when you run your application , CLR communicate with your OS.



• Strong Reason For Developing .NET , Application which is created in C++ ,Vb6

programmer can’t use application of C++ .

• If an Application is Written in C++ in VB you have to write this application again.

• Because Tool Change , Language Change , Input Change , Output change.



• C++ Developer Says he/she create strong application he/she use pointers etc .

• VB6 programmer says he/she creates application rapidly.

• Now like a wheel we create and application in C++ and we can use in VB6 etc.



• Now you have visual studio single integrated development environment, one tool in which you can create application in C++ as Well a VB6 etc.

• But Before .NET tool change language change , input change , output change , Compiler different .



• First your learn Tool then language syntax etc.

• Now Tool same , IDE same , Input (Libraries ) same, out put same . • 30 + languages run on single IDE



• A tool which facilitate all developers.

• C# developer using these tool as well as VB , C++ etc.

• In a single tool VB6 application is compiling , C# sharp compiling , C++ compiling , not possible to think , but Microsoft does.



• VB.Net compiler is vbc , C# compiler is csc .

• All language running on a single platform.

• Behind the scene when you compile your application of VB vbc compiler use, C# application csc compiler use on a single IDE.



• How its possible application written in C++ or VB can use in C#.

• When you compile your application of C# , C# compiler csc produce output in MSIL which is another low level language.

• Also when you compile your VB application , vb compiler vsc compiler produce out in MSIL.



• C# application out is in MSIL and VB application out also in MSIL.

• Out which is produce by vsc VB.NET in the form of MSIL , VB.NET compiler

can consume this out put.

• You can write library , now you can use this library through add reference on 1000 places now your compiler is also producer as well as consumer.



• Suppose you write a function after compile make it DLL , now you can use any where.

• VB.NET compiler is producing and consuming MSIL , C# compiler consuming and producing MSIL , SO now C# compiler can understand output produced by VB.NET.



• Because when both C# and VB.NET understands MSIL so they can communicate.



• You compile your application MSIL or exe produce. When your double click or run your application CLR again Compile your application using JIT and

produce native according to your OS.

• IF Your Os is windows 7 then it will generate native code according to windows7.



• Before framework when you compile your code on 32 bit system , so 32 can use your code only.

• But Now your application can run after 10 years because of forward compatibility. Except one platform 16bit.

• Now Your application will be platform independent but for Windows.



• When JIT compile MSIL this is double compilation.

• When you compile one language and in the result another language produce is cross compilation.

• Double compilation .NET framework does and Cross compilation you have to do.



What is WinAPI Or Win32 API ?


• Windows APIs are dynamic-link libraries (DLLs) that are part of the Windows operating system.



• You use them to perform tasks when it is difficult to write equivalent procedures of your own.



• Is Microsoft's core set of application programming interfaces (APIs) available in the Microsoft Windows operating systems.



• For example, Windows provides a function named FlashWindowEx that lets you make the title bar for an application alternate between light and dark

shades.



• The advantage of using Windows APIs in your code is that they can save development time because they contain dozens of useful functions that are already written and waiting to be used.



• The disadvantage is that Windows APIs can be difficult to work with and unforgiving when things go wrong.



• Windows APIs represent a special category of interoperability.



• The Windows API, informally WinAPI,.

• It was formerly called the Win32 API;



• .NET provides a new API, new functionality, and new tools for writing Windows and Web applications, components, and services in the Web age.



• Windows APIs do not use managed code, do not have built-in type libraries, and use data types that are different than those used with Visual Studio.



• The Windows API, the library of functions used to write Windows applications, was originally written in C and has steadily grown over the years.

Why do we need a new API


• It now consists of many thousands of routines and has several problems.



• First, it has grown very large and has no coherent internal organization, which can make it hard to use.



• During its growth, features were added piecemeal,

• so it doesn’t always present a unified interface to developers, and it contains a lot of legacy functions and data types.



• Second, a more major problem is that the Windows API was initially designed for use by C programmers.



• This means that it can be difficult to use in languages other than C.

• It also doesn’t fit in very well with modern object-oriented programming methods and languages



Documents

NET Framework Introduction Nouman Qureshi [email protected]