1 / 19

Understanding Microsoft.NET

Understanding Microsoft.NET. Steven B. Raines. Summary. What is .NET Why Move to .NET How Does .NET work. Microsoft says:

adamdaniel
Download Presentation

Understanding Microsoft.NET

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Understanding Microsoft.NET Steven B. Raines

  2. Summary • What is .NET • Why Move to .NET • How Does .NET work

  3. Microsoft says: .NET is a comprehensive family of products, built on industry and Internet standards, that provide for each aspect of developing, managing, using and experiencing XML services. What Is .NET?

  4. But What Does It Mean? Microsoft .NET.  2003. Defining the basic elements of .NET Microsoft. World Wide Web Publication, http://microsoft.com/net/basics/whatis.asp

  5. Suite of Technologies • Developer tools • ASP.NET • Visual Studio .NET • Visual Basic .NET • Visual C# .NET • Visual C++ .NET • Jscript .NET • Visual J# .NET • Visual FoxPro 7.0 (.NET) • Can consume .NET XML web services generated by ASP.NET. • Can publish XML web services usable by .NET

  6. Suite of Technologies (Cont.) • Smart Clients • Windows 2000 and Windows XP PCs with .NET Framework. • XBOX • Machines running Ximian Mono (open source implementation of .NET) • Smart phones • Handheld computers / PDAs • Smart Appliances

  7. Suite of Technologies (Cont.) • Web Service Technology • W3C-based Technology • Simple Object Access Protocol (SOAP) • Universal Description, Discovery, and Integration (UDDI) (an online registry of web services)

  8. Suite of Technologies (Cont.) • .NET Servers • .NET Standard Server (replacing Windows 2000) • .NET Web Server • .NET Enterprise Server • .NET Datacenter Server

  9. Rich User Experiences • User specific (.NET Identity) • Location independent – Understands and accommodate bandwidth considerations including online vs. offline and appropriate UI. Know how to find and interact with other devices. • UI appropriate to device

  10. Rich User Experiences (Cont.) • Microsoft’s Example: Imagine you wanted to turn up the heat in your house while you were away from home. You could use a .NET experience that controls your household utilities through a smart device. The device you use could be your desktop computer while you were at the office, your smart phone while you were driving to the grocery store, or kiosk while you were shopping for dinner ingredients.

  11. Why Move to .NET • On-going support from Microsoft • Designed to solve internet / web development problems. System features that programmers used to have to create are now provided. Features previously available only from 3rd-party components are now part of the tool set • Designed to ease integration with many different types of systems via XML Web Service technologies. • Allows organizations to leverage many existing developer skill sets • Easier to use development environment

  12. How Does .NET Work? • Common Language Runtime (CLR) • Class Libraries • Loosely Coupled Web Services

  13. Common Language Runtime (CLR) Assembly-based deployment, with side-by-side versioning of reusable components. No more “DLL Hell”. Interoperability across languages. Core set of language features across languages. Support for existing infrastructure (COM/DCOM) Server generated “Web Controls” make experience more like windows. Supports compiled execution. Web Farm Session State. Update running applications (unlike COM/DCOM restarts)

  14. Class Libraries • .NET Framework provides functionality for tasks such as user interface design, threading, security management, network communications, and so on. • ADO.NET for data manipulation • ASP.NET for building Web applications and XML Web services • Windows Forms for building Windows-based smart client applications. • Mobile Toolkit for delivering applications to web enabled handheld devices.

  15. Loosely Coupled Web Services • Built on the framework of the web, but uses XML in mutually agreed upon frameworks like SOAP. • Not transport specific. • Usually HTTP • SMTP • Instant Messaging Protocols (Jabber) • Raw TCP • XML based message instead of MIME (as in HTTP).

  16. Summary • What is .NET • Why Move to .NET • How Does .NET work

  17. Internet Resources Microsoft .NEThttp://www.microsoft.com/net Microsoft .NET for IT Professionalshttp://www.microsoft.com/technet/treeview/default.asp?url=/technet/itsolutions/net/evaluate/itpronet.asp Security in a Web Services World: A Proposed Architecture and Roadmaphttp://www.msdn.microsoft.com/library/?url=/library/en-us/dnwssecur/html/securitywhitepaper.asp?frame=true .NET Security Overviewhttp://www.microsoft.com/net/downloads/security_net.doc

  18. Internet Resources .NetWirehttp://www.dotnetwire.com/ GotDotNet?http://www.gotdotnet.com/ Active Server Pages .NEThttp://www.asp.net/ Ximian Mono (Open Source .NET)

  19. About the Presenter Steven B. Raines raines@algonquinstudios.com Co-Founder Steve has over seven years experience implementing business solutions through Internet, intranet and Extranet systems. He has an extensive knowledge of Internet technologies, focused on design integration, scalable systems development and legacy systems integration. Steve has been involved in the delivery of and integration with a number of web service based systems for the City of Buffalo and the ABC Companies. He is also the principal developer of Quantum CMS, a content management system that integrates and XML service-based architecture, currently undergoing a move to .NET.

More Related