Began using .Net professionally in March 2001 with the BETA 1. ASP.Net has been the cornerstone of my development career.

Design oriented towards one or more of the following:

• Efficient and maintainable architecture of UI, BL, and DAL
• Object representation of business entities which are extensible and self maintaining
• Base Classes & Master Pages for uniform design & functionality
• Utility classes for repetitive work
• Extension of existing classes through inheritance
• Reusability/Encapsulation of custom classes and controls
• Transparent implementation of features in all tiers which require limited or no coding on the part of other developers
• Intelligent caching and data storage strategies
• Secure web design patterns and their impact on performance

User Interface:

• Extensive experience developing Custom controls and User controls which perform defined sets of work and return predictable outputs.  Designed towards usability for both the end user as well as the UI developer
• MS AJAX control toolkit, leverage of the MS AJAX client side framework, custom AJAX including using direct interaction with Web Services via MSXML2.XMLHttp ActiveXObject, XML DOM parsing and DHTML updating
• Unique and intuitive design to capture user input
• Validation using .Net validation controls, custom Jscript and Regular Expressions

Business Logic:

• Design of entry points to DAL which simplify and normalize data processing
• Creation and exposure of business entities via established data containers (DataSet/Table/Row) as well as custom objects suitable for direct consumption, used in transport and/or caching
• Exposure of elements to BL consumers which ease repetitive member references and improve reliability and maintainability of UI code
• Security and Permissions via established MS methods (MembershipProvider) as well as custom controllers for CRUD access all the way down to a control level

Data Access:

• Method authorship of CRUD functions
• Utility class methods to simplify parameters passed in while ensuring data integrity
• Multiple data storage device access via Database Factory methods simplifying calls into the DAL

File System Access:

• Interaction with the file system from ASP.Net to retrieve, create, manipulate and index files
• Creation of standardized File Access Object serving the same purposes as the DAO
• Utility methods to parse file names and ease repetitive tasks related to dealing with files

Caching:

• Use of established caching mechanisms available through ASP.Net including Application, Profile (cross session), Session and Page caching
• Use of cache storage on both the client (via cookies) as well as on SQL server (UseUri) and the benefits/drawbacks to each

Security:

• Standard access controls through ASP.Net as well as administration
• Shielding sensitive data via data aliases, encryption and late associations with protected information
• Access protocols relying on ASP.Net entities, Active Directory and custom entities
• Access and manipulation of Active Directory through C#/.Net

Tools:

• Visual Studio .Net 2005 & 2008
• Visual SourceSafe
• CVS, WinCVS, Tortoise

Database Design oriented towards one or more of the following:

• Normalization
• Object friendly schema
• Legacy system replication, co-existence and/or transition
• Data integrity rules intelligently employing triggers and keys

Administration:

• Data export/importation
• Backup schedule & granular recovery
• Deployment scripting
• Database Synching

Programming:

• Stored Procedure authoring

Tools:

• SQL Server Management Studio
• SQL Enterprise Manager
• Query Analyzer
• Profiler
• Visio for Enterprise Architects
• SQL Scripter