MS.NET

PHASE 1: Introduction to .NET Programming

• Overview
• Microsoft .NET & Architecture
• Object Oriented Programming
• Net Framework essentials
• Programming in C#

Detailed Coverage for PHASE 1

Object Oriented Programming (OOP)

• Class
• Object
• Encapsulation
• Inheritance
• Polymorphism
• Abstract Class and Function
• Interface
• Constructors
• Access Modifiers
• Overriding/Overloading
• Shadowing

.Net Concepts

• Framework
• Common Language Runtime
• Base Class Library
• Common Type System (CTS)
• Intermediate Language
• Assemblies
• Shared Assemblies
• Namespaces

Programming with C#

• Variables
• Comments
• XML Documentation
• Constants
• Keywords
• Data Types
• Reference Types
• Control Statements
• Conditional Statements
• Switch Statement
• Loops
• Jump Statements
• Go to
• Break
• Continue
• Return
• Arrays
• Anonymous Methods
• Delegates
• Properties
• Events
• Exception Handling
• Collections
• Generics
• Struct
• Anonymous Types

PHASE 2: Developing Windows Forms Applications

• Desktop Application Development
• Console Application Development
• Web Forms and Applications development
• Basic Controls
• Event handlers
• Demo Project

Detailed Coverage for PHASE 2: Objective of this module

Windows Forms

• Why Windows Forms?
• Windows Form Layout options
• Walk through: Creating Simple Windows Form application
• Form Members
• Form Code Behind
• Startup Form
• Modal and Modaless Forms

Standard Controls – Windows Application

• Labels
• Textboxes
• RichTextBox
• Button
• Checkbox
• RadioButton
• ComboBox
• PictureBox
• ListBox
• ImageList
• ListView
• TabControl
• MenuStrip
• DataGridView
• DatePicker

Event Handlers

• Creating Event Handlers
• Default Event Handlers
• Associating Event Handlers at Run Time
• Order of events
• Custom Controls
• Creating a sample desktop Application

PHASE 3: Developing Web Applications using ASP.NET

• ASP .Net Web Application Life Cycle and Events
• Web application architecture
• Web forms Development
• Master Pages
• User Controls and Custom Controls

Coverage for PHASE 3

• Objective of this module
• First things first
• Creating ASP.NET Application
• Components an ASP.NET Application
• ASP.NET Page Processing
• Server Controls
• State Management
• Master Pages
• User Controls and Custom Controls
• Site Navigation
• Caching
• Configuration
• Globalization and Localization
• Custom Controls
• User Controls
• Directives
• Error handling
• Security

PHASE 4: Data access with ADO.NET and XML Mail Management

• ADO .Net
• Data Access using XML
• WPF, LINQ, AJAX
• Data structures and Collections in .Net
• LINQ
• Lambda Expressions

Detailed Coverage for PHASE 4

• First things first
• Introduction to ADO.NET
• Data Structures and Data Access Components
• Data Binding
• Data Access using XML
  • LinQ
  • Lambda Expressions

PHASE 5: Web Services and WCF

• Communication and messaging in ASP .Net
• SOA basics
• Conventional ASP .Net Web services
• Creation and consumption of a web service
• Necessity of WCF
• Components of WCF & Service creation
• Consuming the WCF Service

Detailed Coverage for PHASE 5

• Objective of this module
• First things first
• ASP .Net Web Services
• Creating a service
• Service class
• Service method
• Consuming a web service
• Service Reference
• Proxy Class
• Introduction to WCF
• Address
• Binding
• Contracts
• Instance Management
• Operations
• Transaction Management
• Security

PHASE 6: Design Patterns- MVC Framework, introduction to MVVM

• Introduction to Design patterns
• MVC, MVP and MVVM
• Net MVC Framework 4

Detailed Coverage for PHASE 6

• Introduction to Design Patterns
• MVC
• MVVM
• MVC Framework
• Razor Coding Basics
• Introduction to Entity Framework

PHASE 7: Deployment, Version Control, Unit Testing Framework

• Build and Deployment Process
• Tools Used for deployment
• Version Control
• Unit Testing and Code coverage

Detailed Coverage for PHASE 7

• Introduction to Version Control
• Team Foundation server
• Build process
• Unit Testing
• .Net 4.0 Unit Testing Framework

PHASE 8: Development Methodologies

• Development Methodologies
• Waterfall and Agile Models

Detailed Coverage for PHASE 8

• Introduction to development methodologies
• Waterfall Model
• Agile Model
• Sprint Process

Detailed Objectives

• To teach attendees how to enhance their sites with special effects created by integrating Cascading Style Sheets (CSS) and JavaScript
• To teach students how to create these effects in a way that is compatible with a wide array of browsers, including Internet Explorer 4 through 6 and Netscape 4 through 7
• To learn how XML, XAML and its related technologies function and how they facilitate integration between applications
• To teach attendees the fundamentals of VB.NET programming and how to use VB.NET to write applications
• To explore core object-oriented design patterns and their application to MS.NET
• To learn core MS.NET web design patterns
• Design and build robust and maintainable web applications
• Create dynamic HTML content with ASP.NET Server Pages
• Access databases with ADO.NET, ODBC
• Build stateless session beans as part of a service layer or SOA.
• Develop systems of entities to manage complex data models including 1:1, 1:N, and N:N associations.
• Manage transactional behavior of the application through declarative and programmatic techniques.
• Implement message-driven beans to process queued messages asynchronously.
• Declare and/or program transaction boundaries, persistence contexts, and exception handling to properly control persistence logic.
• Describe the inter operable web services architecture, including the roles of SOAP and WSDL.
• Understand the importance of the WCF, WPF Basic Profile for inter operable web services.
• Customize data binding by specifying specific type mappings or altering method or parameter names.
• Expose session beans as web services.
• Incorporate binary data, such as images, into service and client code.
• To teach attendees the mechanics of the MS.NET 2/3/4 framework for building ASP.NET applications
• To migrate from MS.NET Framework 2 till 4
• Understand the scope, purpose, and architecture of Framework
• Use Dependency Injection to further control object relationships from outside the ILM code base
• Build a Web application as a Website/Project  and associated application context, acting as controllers, command objects, and view resolver
• Master deploying and managing VB.nET and Web Services applications in IIS
• Understand workload and security management
• Learn how to define deployment descriptors and troubleshoot deployment problems using the advanced features of the IIS Web Administrator’s Console and other tools
• Learn how to implement the Web-Security specification to provide Web services with authentication, message integrity and confidentiality
• Examine MS SQL deployment and configuration
• Describe the fundamentals of SOA.
• Understand the business advantages of SOA.
• Explain the SOA run time elements.
• Describe the concept of an Enterprise Service Bus.
• Identify features of typical SOA Framework Products.

Interview Preparation

• Mock Interviews
• Interview Preparation Tips
• Sample Interview Questions
• How to clear an Interview

CASE STUDY # 1 – “Healthcare System”

Healthcare System Application

As the Product Manager for Inner Expressions you are asked to provide one of your largest clients with additional features in the EMR ( Electronic Medical Records Management) System. The client has requested an integrated Referral Management System that tracks patients from Primary care into the Specialist departments. Appointments are created by either the Primary Care Physicians themselves or other clinical staff like Nurse Practitioners or Clinical Assistants. Each appointment must go through the appropriate checks including checking if the patient has an active insurance with the client, whether the insurance program covers the condition of the patient, patient’s preference for location and timings and availability of the Specialist doctor.
Some appointments may have to be reviewed by the Specialists themselves before they can be approved, the administrator of the facility (hospital) must have the ability to choose by appointment type to either make it directly bookable by the Primary Care Staff or as a type that requires review by the specialist. The system should also allow the Primary Care Staff and specialists departments to exchange notes and comments about a particular appointment. If the specialist department requests tests or reports as mandatory for the appointment, the system must ensure that the patient has these available on the date of the appointment.
The system shall also allow users to track the status of patients’ appts & must store the entire clinical history of each patient. This will be used by the hospital for two main purposes; the specialist and the primary care providers will have access to the patients complete medical history before the patient walks in for the appt and hence allowing for better patient care, the Hospital also stores this data in a general data warehouse ( without Protected Health Information) to do analytics on it and come up with local disease management programs for the area. This is aligned with the Hospitals mission of providing top quality preventive medical care.
The Hospital sets about 300 appointments per day and must support about 50 users at the same time. The existing EMR system is based on Java and an Oracle database system.

TASKS

• Identify Actors, Use Cases, Relationships,
• Draw Use Case Diagrams
• Identify Ideal, Alternate and Exception Flows
• Write a Business Requirements Document

CASE STUDY # 2 – “Asset Management System”

Asset Management Application

An e Examination system is also known as (e-Pariksha/ Online Examination Scheduler), an Intelligent Web Application which automates the process of pre examination scheduling of Any Academic Institutions, Universities, Colleges and School. This automations primary scope is to save nature by saving tons of paper involved in conducting the examination. All examination communications are done via email management between student and Academia. Usually any examination would start with Exam Registrations, which is connected to Subject Creation, Exam Room Management , Room Allotment, Examination Hall Dairy, and Absentees Information (Variety of Reports) – Required by University This Web App edges two sides of Client side and Server side Application. Client side enables student community to fill up their examination registration form online via internet and also they have privileges to check out their examination details like (Day of Start, Complete Time Table, Day-wise Exam Details and Day seating details of the candidate- like room name, seating number subject, date and time. The Server side involves the processing of each candidate exam registration form into workflow like, Subject Loader, Room Management, Seating Manager, Room Allotment, Room Dairies, Absentee Marking, and Rich Crystal Reports to meet various needs of Data set. The Web App Admin records new chattel into database, deletes archaic ones, and revises any information related to examination. “User”. All users are known to the system by their USN, ID and their The asset management system keeps track of a number of assets that can be borrowed, their ownership, their availability, their current location, the current borrower and the asset history. Assets include books, software, computers, and peripherals. Assets are entered in the database when acquired, deleted from the database when disposed. The availability is updated whenever it is borrowed or returned. When a borrower fails to return an asset on time, the asset management system sends a reminder to the borrower and informs the asset owner.
The administrator enters new assets in the database, deletes obsolete ones, and updates any information related to assets. The borrower search for assets in the database to determine their availability and borrows and returns assets. The asset owner loans assets to borrowers. Each system has exactly one administrator, one or more asset owners, and one or more borrowers. When referring to any of the above actor, we use the term “user”. All users are known to the system by their name and their email address. The system may keep track of other attributes such as the owner’s telephone number, title, address, and position in the organization.
The system should support at least 200 borrowers and 2000 assets. The system should be extensible to other types of assets. The system should checkpoint the state of the database every day such that it can be recovered in case of data loss. Owners and the administrator are authenticated using a user/password combination. Actors interact with the system via a web browser capable of rendering HTML and HTTP without support for JavaScript and Java.
The persistent storage is realized using an SQL database. The business logic is realized using the Web Objects run time system. The system includes:

TASKS

• Identify Actors, Use Cases, Relationships,
• Draw Use Case Diagrams
• Identify Ideal, Alternate and Exception Flows
• Write a Business Requirements Document

OTHER CASE STUDIES

Social Networking, Cruise Management System, Collegiate Sporting system