Mjr Net Ppt Portfolio Template


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Mjr Net Ppt Portfolio Template

  1. 1. <ul><li>. </li></ul><ul><li>Michael J. Rady </li></ul><ul><li>[email_address] </li></ul><ul><li>(303) 909 - 4999 </li></ul>.NET C# Portfolio
  2. 2. Table of Contents <ul><li>Set Focus Master .NET C# Program </li></ul><ul><li>Four phase Library Project </li></ul><ul><ul><li>Windows Application </li></ul></ul><ul><ul><li>ADO.NET </li></ul></ul><ul><ul><li>ASP.NET </li></ul></ul><ul><ul><li>Distributed Services </li></ul></ul><ul><li>Additional Experience </li></ul>
  3. 3. C# Masters Program Overview <ul><li>C# </li></ul><ul><li>.NET Framework </li></ul><ul><li>Windows Forms </li></ul><ul><li>Microsoft SQL Server </li></ul><ul><li>ADO.NET </li></ul><ul><li>ASP.NET </li></ul><ul><li>Distributed Applications </li></ul>
  4. 4. OOP using C# <ul><li>C# offers Object Oriented concepts </li></ul><ul><ul><li>Encapsulation – protection, hiding </li></ul></ul><ul><ul><li>Polymorphism – Apply parent/child relations </li></ul></ul><ul><ul><li>Cohesion – How well data fits </li></ul></ul><ul><ul><li>Overloading – redefinition of method params </li></ul></ul><ul><ul><li>Abstract Classes – base class casting </li></ul></ul><ul><ul><li>Inheritance Classes – parenting rules </li></ul></ul><ul><ul><li>Object class – properties, methods </li></ul></ul>
  5. 5. .NET Framework <ul><li>Common Language Runtime (CLR) </li></ul><ul><li>Version control, publishing </li></ul><ul><li>.Net Framework Class Libraries </li></ul><ul><li>Visual Studio </li></ul><ul><li>Serialization </li></ul><ul><li>Components – Toolboxes, Templates </li></ul><ul><li>Object browser </li></ul>
  6. 6. Windows Forms <ul><li>Tools / controls in the Toolbox </li></ul><ul><li>Debugging techniques </li></ul><ul><li>Three tiered approach </li></ul><ul><li>Multi-threading techniques </li></ul><ul><li>Menus, Tree structuring </li></ul><ul><li>Input Validation </li></ul><ul><li>Deployment using ClickOnce </li></ul>
  7. 7. MS SQL SQL SERVER <ul><li>Transaction SQL </li></ul><ul><li>Stored Procedures, IO parameters </li></ul><ul><li>Debugging in Visual Studio </li></ul><ul><li>Data Definition Language Statements </li></ul><ul><li>Data Control Language Statements </li></ul><ul><li>Data Manipulation Language Statements </li></ul><ul><li>Data Integrity – Constraints, Normalization </li></ul><ul><li>Sub-Queries, joins, grouping, ordering </li></ul>
  8. 8. ADO.NET – Data Access Layer <ul><li>Connections to DataSources </li></ul><ul><li>DataReader, DataAdaptor </li></ul><ul><li>DataTable, DataSets, DataRelations </li></ul><ul><li>TableAdaptor </li></ul><ul><li>Exception Handling </li></ul><ul><li>Interface to Business Layer </li></ul><ul><li>XML data manipulation </li></ul>
  9. 9. ASP.NET – Web Interface <ul><li>Master Pages, Themes, Skins </li></ul><ul><li>Site navigation Controls </li></ul><ul><li>Membership, user validation </li></ul><ul><li>Windows Installer </li></ul><ul><li>Toolbox controls </li></ul><ul><li>AJAX Extensions </li></ul><ul><li>Data Binding to controls </li></ul>
  10. 10. Distributed Application <ul><li>Web Service configuration </li></ul><ul><li>Asynchronous methodology </li></ul><ul><li>Serialization of remote-able types </li></ul><ul><li>Remote Events </li></ul><ul><li>Message Queues </li></ul><ul><li>WSE 3.0 Security and Policy </li></ul><ul><li>XML/Soap, Binary Messaging </li></ul><ul><li>Headers and Extensions. </li></ul>
  11. 11. Library Project <ul><li>The class was assigned individual projects on the 3 rd , 5 th , 8 th , 10 th , 12 th weeks of class. The final project was a group project where we broke up into teams and managed the assignment as a group. </li></ul><ul><li>The majority of the work involved applying the prior week’s lecture into a library application that was to be used by a librarian to input members (adults/juveniles) into the data base. The members then were allowed to check-in/check-out books using validations on membership, book availability, number of books etc. </li></ul><ul><li>The first phase involved implementation of the user front-end using windows forms. The Business Layer was set up and interfaced with a data access layer and data base provided by Set Focus. </li></ul><ul><li>The second phase involved implementation of the Entity classes, SQL Server Data Base and the Data Access layer. </li></ul><ul><li>The third phase was a rewrite of the front end using ASP.NET enabling the user to access the project through a web browser. User security and roles were implemented as well. </li></ul><ul><li>The fourth project involved setting up policy and certificates to further enhance security </li></ul><ul><li>Our final group project involved institution of version control using Sub-Version. The TA worked as a project manager for the group. The project itself was a true life application that Set Focus was implementing based on customization of our Student Class Evaluations. </li></ul>
  12. 12. This Screen shows the member and the books that are checked out. The user can select a book and check it in or check out additional books that will show up in the data grid. In this case, the member is an adult and has no “Adult ID” association. The Adult may however, have juvenile associations…
  13. 13. The following two screens show Membership input. The first form adds an adult into the data base. The second screen shows that there is an association between an adult and juvenile. The adult member ID has been populated and validated allowing entry of the juvenile information.
  14. 14. Below are two forms depicting the Check In and Check Out services. These forms are outlined in a menu form that allows selection of the various services available in the project.
  15. 15. A Flourishing Career in IT Growing with Technology <ul><li>As a software developer for 20+ years, I have been exposed to many programming languages. Some of them are still in use today! In college, I programmed in Fortran 4 and later Fortran 77. with the advent of early microprocessors such as the Zilog80, I coded in Basic. This interpreted language allowed instant execution of code but introduced the user to code. Migration to ‘C’ coding and it’s compiler generated code, allowed a more stable environment. Later, I wrote various applications in Perl, TK/TCL and PHP. </li></ul><ul><li>In 1980, Kent State University was obtaining a VAX mainframe that used the UNIX operating platform. In my senior year, I was introduced to the UNIX file and process structure that enabled programmer analysts to better control application development. Shortly after graduation, I implemented a multi-user environment in Xenix which was based on UNIX principals. As disk space and processor speeds grew, these systems became more and more powerful. I worked on XENIX/UNIX (system3,V7,SVR3, SCO, SVR4 and SVR5, HP-UX,Solaris,Linix) for 20+ years. </li></ul><ul><li>In 1986, a data base engine became available on microprocessor levels. Informix RDBMS was the DB of choice and I wrote several applications involving barcoding, shop floor tracking, order processing and golf handicapping… I moved up to ORACLE 3.0 in the late 80’s and became quite practiced at using Embedded-SQL in C. My projects immediately became more complicated involving database analysis. </li></ul><ul><li>In the mid 1980’s, I was involved with researching PC’s and applications that were available at the time. A new PC came out (IBM – AT) that ran an operating system that had similar characteristics of UNIX called DOS. As DOS became windows and multi=media became all the rage, I was constantly exposed to this technology. I’ve been on all versions of windows through Vista. Although not in an administrator position, I often was called upon to play the role. </li></ul>