1. DotNET A Developer’s Perspective Mike Litzkow University of Wisconsin - MadisonOne

2. Microsoft’s Goals Better software development tools Better software Take over the world – Desktop – Servers – Small Devices

3. What Is DotNET? Execution environment above Win32 – Common Language Runtime Major Technology Pieces – DotNET Framework – C# – ASP.NET – XML Web Services (passport & friends) – Visual Studio.NET

4. Common Language Runtime (CLR) Supports multiple languages – Languages interoperate freely All code is compiled on target machine – Compiler aware of actual CPU to be used – Nothing is interpreted (not even script) – JIT is default, can compile at install time Type safety – Including array bounds checking Garbage collection (including inheritance) C++, C#, VB, JavaScript Cobol, Fortran, Perl, Python, Eiffel, Pascal, SmallTalk, …

5. But, Will the CLR Last? Enterprise development – language interoperability Security – buffer overrun problems eliminated Software reliability – memory leaks, access errors eliminated – versioning problems addressed (end of DLL Hell) Transition to 64-bit architecture – no pointers, target machine compilation Probably Yes

6. Multi-language development Multi-language debugging Syntax coloring and checking Intellisense Drag ‘n Drop GUI development – Same GUI tools for multiple languages – Similar GUI tools for desktop and web Visual Studio.NET C++, C#, VB, JavaScript, HTML, XML, Schema, Bitmaps, … Command line development is available (and free) DotNET Framework SDK

7. DotNET Framework Example content – Object, String, Int, Float, … – I/O – Windows forms – Web forms – XML processing – Reflection Usage model – Direct use – Use by inheritance – Custom toolbox

8. C# Extremely similar to Java Differences – Enumerations – Properties – Delegates – No “checked” exceptions – Everything is an object Reference types Value types

9. C# - Syntax Examples Enumeration public enum Direction {North, South, East, West}; private Direction direction; Property public Direction Direction { get { return direction; } set { direction = value; pointTo( direction ); } Property usage obj.Direction = Direction.North; Delegate too complex to show here

10. But, Will C# Last? It’s a good language, but a lot like Java MS has control – unlike Java Heavily used inside MS Is C# a really important part of DotNET? Probably Yes Nah

11. ASP.NET Server-side code – runs on CLR – uses.NET Framework All code is compiled (even JavaScript) Supports separation of code and HTML Easy and efficient DB connectivity Drag ‘n drop web forms development – Forms work across multiple browsers – Even small devices Xcopy deployment Debugging, logging, caching, …

12. But, Will ASP.NET Last? Probably Yes (CLR on Server,.NET Framework support) Not sure about web forms, HTML/Script connection, DB Connectivty …

13. XML Web Services RPC implemented with XML (SOAP) Service description in XML (WSDL) Underlying protocol HTTP – penetrates firewalls Lots of hype and controversy (Passport) Geneva convention

14. But, Will XML Web Services Last? Web services are an industry wide initiative Lots of questions about compatibility remain Will be important for B2B commerce Much more slowly than Microsoft hopes

15. DotNET Books Introducing Microsoft.NET – David S. Platt C# Essentials – Ben Albahari Applied Microsoft.NET Framework Programming – Jeffery Richter Essential.NET: The Common Language Runtime – Don Box Programming Microsoft Windows With C# – Charles Petzold Easy Intro to Whole Platform Compact reference for C# CLR Windows Forms (desktop apps)

16. Further Talks C# – Delegates – C# vs C++ performance – GUI builder CLR – Types – Metadata – Versioning – Security ASP.NET – Web forms – Database connectivity – “Business” logic – Security

17. Contact Info Mike Litzkow – mlitzkow@facstaff.wisc.edu – mike@cs.wisc.edu – 262-6122 eTEACH Home Page – http://eteach.engr.wisc.edu http://eteach.engr.wisc.edu