.Net overviewrajnish

1,003 views
796 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,003
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
19
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • The .NET framework exposes numerous classes to the developer. These classes allow the development of rich client applications and Web based applications alike. In the above slide these classes have been divided into 4 areas. ASP.NET provides the core Web infrastructure such as Web Forms for UI based development and Web Services for programmatic interface development, User interface development on the Windows platform can be done using Windows Forms ADO.NET and XML provide the functionality for data access. Finally, the core base classes provide infrastructure services such as security, transaction management etc.
  • Common Language Runtime Common, secure execution environment. We’ll drill into this in some detail in the first parts of the presentation. Windows ® forms Framework for building rich clients A demonstration will highlight some of these features, such as the delegate-based event model. ASP.NET Web forms Manageable code (non spaghetti) Logical evolution of ASP (compiled) Again, we’ll drill into a hint at the power of Web Forms with a demonstration Web Services Programming the Internet to leverage the "power at the edge of the cloud". We will cover this in detail, as this – along with the CLR – is one of the more powerful aspects of .NET Framework. ADO.NET, evolution of ADO New objects (e.g., DataSets, Datareader) Visual Studio.NET Most productive development environment gets better and fully supports the .NET Framework
  • The first incarnation of ASP proved very successful. As part of the .NET Framework, Microsoft support ASP.NET. ASP.NET is a logical evolution of ASP, but addresses many of the issues associated with ASP. ASP.NET is now compiled and not interpreted. A great deal of work has also been done to make sure that ASP.NET development becomes cleaner and more productive.
  • The Web Form is basically an ASP.NET file (.ASPX) that makes use of the new features of ASP.NET. ASP.NET in conjunction with Web Forms eliminate a number of the traditional problems associated with ASP. ASP.NET provides the developer with the option of separating the code from the UI elements using ‘code-behind’ forms. Using such a mechanism will also make Form tools much easier to develop. ASP.NET also conquers one of the annoying side effects of using ASP – state. Imagine that a user has filled in an ASP generated form and then hits the submit button. At this stage IIS (server side) will regenerate the form and as a side effect all the information that the user entered into the form will be erased. In many situations this is unacceptable, and many an ASP developer has struggled to find work arounds (most of which may not be considered elegant). Fortunately, ASP.NET allows controls to maintain state. ASP.NET supports a number of new rich server controls. These controls can be used to improve data connectivity (data bound controls) and data validation.
  • Technically a Web Service is “ A programmable application component accessible via standard Web protocols”. In other words, it’s a component that can be called remotely, over the internet, from a client application. Take our previous example of a Web application that required ‘stock information’. This Web application possibly would not have that information readily at hand. However, what if another Web application (possibly on another machine, on the other side of the planet) did? Further more what if this remote machine exposed a component with a method such as ‘GetStockPrice (string strCompanyName)’ . Surely this would make life much easier, making separate Web sites act like ‘one big application’. Web service consumers can send and receive messages using XML, and therefore the audience of clients is unlimited.
  • .Net overviewrajnish

    1. 1. Introduction to .NET Framework BY- Rajnish kalla
    2. 2.  Software platform Language neutral In other words: .NET is not a language (Runtime and a library for writing and executing written programs in any compliant language)
    3. 3.  .Net is a new framework for developing web- based and windows-based applications within the Microsoft environment. The framework offers a fundamental shift in Microsoft strategy: it moves application development from client-centric to server- centric.
    4. 4. .NET Framework• First developed by Microsoft in 2000• Current version (3.0) released in Nov 2006• Targets primarily Windows OS, but Mono Project (headed by Novell) supports Linux, Unix, FreeBSD, Mac OS X, Solaris• Primary languages: C#, Visual Basic .NET, C++/CLI, and J#• Third-party languages: Ada, COBOL, LISP, Perl, Ruby, and many more
    5. 5. .NET Application .NET FrameworkOperating System + Hardware
    6. 6. VB VC++ VC# JScript … Common Language Specification Visual Studio.NET Visual Studio.NETASP.NET: Web Services Windows and Web Forms Forms ADO.NET: Data and XML Base Class Library Common Language Runtime
    7. 7.  Common Language Runtime Windows® Forms ASP.NET ◦ Web Forms ◦ Web Services ADO.NET, evolution of ADO Visual Studio.NET
    8. 8. CLR works like a virtual machine in executing alllanguages.All .NET languages must obey the rules andstandards imposed by CLR. Examples:◦ Object declaration, creation and use◦ Data types,language libraries◦ Error and exception handling◦ Interactive Development Environment (IDE)
    9. 9.  Development ◦ Mixed language applications  Common Language Specification (CLS)  Common Type System (CTS)  Standard class framework  Automatic memory management ◦ Consistent error handling and safer execution ◦ Potentially multi-platform Deployment ◦ Removal of registration dependency ◦ Safety – fewer versioning problems
    10. 10. Comparison to Java compile executeHello.java Hello.class JVMSource code Byte code compile execute Hello.vb Hello.exe CLRSource code CIL
    11. 11. • CTS is a rich type system built into the CLR – Implements various types (int, double, etc) – And operations on those types• CLS is a set of specifications that language and library designers need to follow – This will ensure interoperability between languages
    12. 12. Code in anotherCode in VB.NET Code in C# .NET Language AppropriateVB.NET compiler C# compiler Compiler IL(Intermediate Language) code CLR just-in-time execution
    13. 13.  .NET languages are not compiled to machine code. They are compiled to an Intermediate Language (IL). CLR accepts the IL code and recompiles it to machine code. The recompilation is just-in-time (JIT) meaning it is done as soon as a function or subroutine is called. The JIT code stays in memory for subsequent calls. In cases where there is not enough memory it is discarded thus making JIT process interpretive.
    14. 14.  Languages provided by MS ◦ VB, C++, C#, J#, JScript Third-parties are building ◦ APL, COBOL, Pascal, Eiffel, Haskell, ML, Oberon, Perl, Python, Scheme, Smalltalk…
    15. 15. Windows Forms• Framework for Building Rich Clients – RAD (Rapid Application Development) – Rich set of controls – Data aware – ActiveX® Support – Licensing – Accessibility – Printing support – Unicode support – UI inheritance
    16. 16. ASP.NET,the platform services that allow toprogram Web Applications and Web Services inany .NET languageASP.NET Uses .NET languages to generateHTML pages. HTML page is targeted to thecapabilities of the requesting BrowserASP.NET “Program” is compiled into a .NET classand cached the first time it is called. All subsequentcalls use the cached version.
    17. 17. ASP.NET• Logical Evolution of ASP – Supports multiple languages – Improved performance – Control-based, event-driven execution model – More productive – Cleanly encapsulated functionality
    18. 18.  Allows clean cut code ◦ Code-behind Web Forms Easier for tools to generate Code within is compiled then executed Improved handling of state information Support for ASP.NET server controls ◦ Data validation ◦ Data bound grids
    19. 19.  A technical definition ◦ “A programmable application component accessible via standard Web protocols”
    20. 20. Web Services• It is just an application…• …that exposes its features and capabilities over the network…• …using XML…• …to allow for the creation of powerful new applications that are more than the sum of their parts…
    21. 21. ADO.NET (Data and XML)• New objects (e.g., DataSets)• Separates connected / disconnected issues• Language neutral data access• Uses same types as CLR• Great support for XML
    22. 22.  Development tool that contains a rich set of productivity and debugging features
    23. 23. CLRCLR
    24. 24.  The .NET Framework ◦ Dramatically simplifies development and deployment ◦ Provides robust and secure execution environment ◦ Supports multiple programming languages
    25. 25. Comparison between J2EE and .NET Architectures
    26. 26. Execution Engine J2EE Java source code compiles into machine- independent byte code Runtime Environment : JVM .NET Any compliant language compiles into MSIL Runtime environment : CLR Both JVM and CLR ,support services, such as code verification, memory management via garbage collection, and code security
    27. 27. Cross Platform Portability J2EE Platform Independent JDK should exist on target machine .NET Supports Windows platform CLR should exist on target machine Can support other platforms provided it has its own JIT complier
    28. 28. Language Support J2EE Tied to Java Supports other languages via interface technology .NET Language independent Supports any language if mapping exists from that language to IL
    29. 29. Tools Support J2EE Can employ any number of tools Pro :Developer has a great deal of choice Con :Difficulty in choosing a right tool for a given job .NET Visual Studio.NET, single IDE for building an application
    30. 30. Background Web Architecture PC/Mac/Unix/...Client + Browser Request: http://www.digimon.com/default.aspNetwork HTTP, TCP/IP Response: <html>….</html>Server Web Server
    31. 31. Background What is ASP?• Server-side programming technology• Consists of static HTML interspersed with script• ASP intrinsic objects (Request, Response, Server, Application, Session) provide services• Commonly uses ADO to interact with databases• Application and session variables
    32. 32. Background What is ASP?HTTP request HTTP response(form data, HTTP HTML, XML header data) ASP page (static HTML, server-side logic)
    33. 33. Background ASP Successes• Simple procedural programming model• Access to COM components – ActiveX Data Objects (ADO) – File System Object – Custom components• Script-based: no compiling, just edit, save & run – VBScript, JScript – leverages existing skills• Support for multiple scripting languages
    34. 34. Programming Model Controls and Events Button codeButton ... List codeList ... Text codeText ... Browser ASP.NET Event handlers
    35. 35. Programming Model Automatic Browser Compatibility• Controls can provide automatic browser compatibility• Can target UpLevel or DownLevel browsers – UpLevel browsers support additional functionality, such as JavaScript and DHTML – DownLevel browsers support HTML 3.2
    36. 36. Server Controls HTML Controls• Supported controls  <textarea> – <a>  <button> – <img>  <input type=text> – <form>  <input type=file> – <table>  <input type=submit> – <tr>  <input type=button> – <td>  <input type=reset>  <input type=hidden> – <th> – <select>
    37. 37. Resources• General Sites – http://msdn.microsoft.com/net/aspnet/default.asp – http://www.asp.net/ – http://www.fmexpense.com/quickstart/aspplus/defa ult.htm – http://www.asptoday.com/ – http://www.aspng.com/aspng/index.aspx – http://www.4guysfromrolla.com/ – http://www.aspfree.com/ – http://www.devx.com/dotnet/ – http://www.ibuyspy.com/
    38. 38. Resources• ASP.NET Overview http://msdn.microsoft.com/msdnmag/issues/0900/ASPPlus/AS PPlus.asp• Validation http://msdn.microsoft.com/library/techart/aspplusvalid.h tm• Databinding in 3 parts http://msdn.microsoft.com/msdnmag/issues/01/03/cutting/c utting0103.asp http://msdn.microsoft.com/msdnmag/issues/01/04/cutting/c utting0104.asp http://msdn.microsoft.com/msdnmag/issues/01/05/cutting/c utting0105.asp• ASP.NET component model http://msdn.microsoft.com/msdnmag/issues/01/02/cutting/c utting0102.asp

    ×