Employee Info Starter Kit

NEW POST: Mal-functioning of OnSelectedIndexChanged

Aung — Wed, 15 Jul 2009 03:51:03 GMT

Hi,

Problem: OnSelectedIndexChanged of dropdownlist is triggered when it is not supposed to.

I used part of sample project in my project.
It required to use OnSelectedIndexChanged for dropdownlist.
In "details-page.aspx", make OnSelectedIndexChanged for "Country" and "Report To" dropdownlists.

To simulate the problem,
- Change "Country" first,
- then change "Report To" and check at breakpoints.
- It triggers both of OnSelectedIndexChanged for changing of "Report To".

Please help to explain where does it go wrong.

Thanks,

Aung.

NEW POST: Kindly clarify my doubts in understanding the scripts. Please

Ganesh — Tue, 07 Jul 2009 21:31:59 GMT

Hi Great Code, Undoubtedly

Right I understand the basic functionality of this system is to create,update,delete on employees.

The major part of this project i have a problem understanding is in the Back end and that`s where is one major procedure the Create Schema Script. I kindly request you to help me understand this

1.
CREATE PROCEDURE dbo.Employees_DeleteEmployees @employeeIds xml
AS
BEGIN

SET NOCOUNT ON;

--BEGIN TRAN

delete Employees Where EmployeeID in
(
SELECT ParamValues.ID.value(''.'',''int'') as Id
FROM @employeeIds.nodes(''/Id'') as ParamValues(ID)
)

2.
CREATE PROCEDURE dbo.Employees_DeleteEmployee
@EmployeeID Int

The Major difference between 1 and 2 is that 1 and 2 are overloaded procedures. 1 is used when the user of the application tries to delete a bunch of employees

Doubt 1
Even if you have a purpose of taking a bunch of employees as @xml because there is no support for arrays, i dont understand why the need when at the end the delete from employee table is being made as a set,

why couldn't you just get all the emp id into some sort of temporary table parameter and delete from employee table where the employee id is in the #table -- Reason possibly as when the user selects a bunch of user id they need to be stored in some sort of array, but couldn't they be stored in a table in order to say delete from table where id is in this collection, i understand there is no support for arrays as you mentioned you used @xml but what about using a temp table to hold all the selected emp id passed by the user and then delete from the table those id in the column. I might be sounding confusing or weird excuse my understanding, i am just trying to make sense.

Doubt 2
FROM @employeeIds.nodes(''/Id'') as ParamValues(ID)

Does FROM @employeeIds.nodes(''/Id'') means to search in the xml tree for nodes which contain "/Id"
>If so r u trying to say to search for Employee_Id tags attached to those nodes or something like that.

Doubt 2.1
What is the meaning of saying find me all the nodes which contain "/Id"(as said by FROM @employeeIds.nodes(''/Id'')) and pass them onto ParamValues(ID) i could had understood if you said as ParamValues thinking you are renaming it but why (ID), is it like some counter. like an array something.

Doubt 3
SELECT ParamValues.ID.value(''.'',''int'') as Id

Here right say in FROM you got all the nodes containing "/Id" i.e all the employee Id nodes then isn't it node name.value to get the value Why r u specifying node name which is ParamValues.ID.value

does it mean to say if you stored the first emp_id as ParamValues(0) then fetch me the value in that node by saying ParamValues.0.value

Doubt 3.1

What does (".","int") specify i understand on the whole your trying to get the value inside the node and when "." occurs convert the xml text into int.
Is this understanding right.

Doubt 4

CREATE PROCEDURE dbo.Employees_GetEmployeesByReportsTo_Paged
(@reportsTo Int, @orderby varchar(50),@startrow int,@pagesize int)
As

Here
You specified

In the sql statement below, using the ''WITH'' statement we are first populating a temporary table,where we considered the ROWNUMBER() function to creating ROWIndex.

set @sql=''
WITH Employees_PageSegment AS

I did not entirely understand how this functions because i understand the part where you say

with Employees_PageSegment as
( Select .... from table ) that the Employees_PageSegment table now holds all these columns

BUT my doubt is when you say

select ...
from ...
where
reportsTo = ''
+ CONVERT(nvarchar(10),@reportsTo)
+ '' AND
RowIndex BETWEEN ''
+ CONVERT(nvarchar(10),@startrow)
Here by using " + what is hapenning here ?

what are you concatenating ?

Can I Also request you to point me out the way through which i will understand the working of the code better, i mean i started out by going through the back end scripts. Is there any better way to understand like maybe go though some front end c# scripts and then go through the rest of back end or maybe do some debugging, i am just asking as being the developers of this project you know the best way to get an easier and efficient way to get an idea of working of the project.

I am really trying hard to understand this project as i have to create something similar to it.
please i request you not to be frustrated if i sound naive and help me understand.

Thank you.

NEW POST: Error in running the Employee Info Starter Kit first time

dalewz — Fri, 05 Jun 2009 18:59:32 GMT

I checked the software again. There is only one 'Report To'. There is no immediate supervisors in the Edit page.

More testing shows that only one employee under Andrew can be listed, although I had two people reported to him.

Any reason?

Thanks.

{quote}
joycsc wrote:
Only immediate supervisors will be considered.

NEW POST: Error in running the Employee Info Starter Kit first time

joycsc — Fri, 05 Jun 2009 12:11:37 GMT

Only immediate supervisors will be considered.

{quote}
dalewz wrote:
Thanks a lot for your help. after i changed 'Report To' of Nancy D. to Andrew, the filter worked for andrew.

but i also added an employee "dale young" with 'Report To' Andrew, the filter only gave Nancy instead of Nancy and Dale.

Why?

Regards.

joycsc wrote:
Check ur answers below:

1. No, the feature is not broken. As there is no employee which has the 'Report To' field to be set to Andrew, you are no been able to see any of them.

NEW POST: Error in running the Employee Info Starter Kit first time

dalewz — Wed, 03 Jun 2009 02:12:17 GMT

Thanks a lot for your help. after i changed 'Report To' of Nancy D. to Andrew, the filter worked for andrew.

but i also added an employee "dale young" with 'Report To' Andrew, the filter only gave Nancy instead of Nancy and Dale.

Why?

Regards.

{quote}
joycsc wrote:
Check ur answers below:

1. No, the feature is not broken. As there is no employee which has the 'Report To' field to be set to Andrew, you are no been able to see any of them.

NEW POST: Error in running the Employee Info Starter Kit first time

joycsc — Tue, 02 Jun 2009 08:46:50 GMT

Check ur answers below:

1. No, the feature is not broken. As there is no employee which has the 'Report To' field to be set to Andrew, you are no been able to see any of them.

2. Yes, your assumption is right. However the member and admin page are empty, but with a single line of text message and intended for only role based security demonstration purpose only.

3. You can't log-in there, since the ASP.NET Member and Role membership is not been used here. Check the underlying codes in the source code to have the idea of the way it is implemented.

4. These are the advanced functionalities to be implemented with C# logic, and is totally out of scope in employee info started kit. In the employee info starter kit, you can get the basic idea (with hard-coded user names) how the security model can be implemented, but to make it dynamic/database driven you need to write your own custom logic.

Hope this helps!

{quote}
dalewz wrote:
Hi,

Your suggestion is exactly right. After moving the files to C:, it works. Thank you.

With the site running, I have a few more questions (sorry i can not find answers anywhere else):

1. filter:

after I selected Andrew and hit filter button, I got no employee info. But Andrew's info is in the list.

this feature is broken?

2. login:

i could login as "any" with password "any". the difference between logined user and public is the logined user can access member and admin pages, while public can't. am i right?

member page (which is empty)?

admin page (which is empty)?

3. add user:

I used Website -> ASP.NET Configuration -> Security ->
Use the security Setup Wizard to configure security step by step

to add user a. dale with no role; b. admin with the role of admin.

when I tried to login as dale and hit log in, I got "can't log-in! ".

when I tried to login as admin and hit admin log in, I got "can't log-in! "; if hit log in, i got "can't log-in! ".

Why? I did the same thing for the classified ad starter kit, it worked fine.

4. access:

how can I add users like dale to be able to "add employee and enter related info"?

how can i set managers like admin to be able to "modify the employee info and delete employee info"?

Thanks a lot. -Dale

joycsc wrote:
Rather using the solution, open 2008 VWD express, go to File -> Open Web Site, point to the location where the employee info starter kit web site is located on your local directory, and once it opens, just press F5 to run the web site!

NEW POST: cache layer

joycsc — Tue, 02 Jun 2009 08:33:45 GMT

@markmurf

The cache layer contains the similar method signatures as the data access layer, and is intended to handle the cache layer functionalities. So, to utilize it, you just need to re-factor the user interface layer codes (data binding tags on aspx page etc) to replace the class name of data access layer with the class name of the cache layer.

However, if you are advanced developer, then you may want to create a data access provider that is implemented by both data access layer and cache layer, which can be easily pluggable by the web.config.

markmurf wrote:
Hi Ashraf,

Smashing piece of work.

I like the 2 layer architecture (user interface and data access layer), how do I introduce the optional cache layer? Does the sealed keyword affect the ObjectDataSource UI control?

Thanks,
Mark

NEW POST: cache layer

markmurf — Tue, 26 May 2009 10:50:44 GMT

Hi Ashraf,

Smashing piece of work.

I like the 2 layer architecture (user interface and data access layer), how do I introduce the optional cache layer? Does the sealed keyword affect the ObjectDataSource UI control?

Thanks,
Mark

NEW POST: Error in running the Employee Info Starter Kit first time

dalewz — Thu, 21 May 2009 15:20:41 GMT

Hi,

Your suggestion is exactly right. After moving the files to C:, it works. Thank you.

With the site running, I have a few more questions (sorry i can not find answers anywhere else):

1. filter:

after I selected Andrew and hit filter button, I got no employee info. But Andrew's info is in the list.

this feature is broken?

2. login:

i could login as "any" with password "any". the difference between logined user and public is the logined user can access member and admin pages, while public can't. am i right?

member page (which is empty)?

admin page (which is empty)?

3. add user:

I used Website -> ASP.NET Configuration -> Security ->
Use the security Setup Wizard to configure security step by step

to add user a. dale with no role; b. admin with the role of admin.

when I tried to login as dale and hit log in, I got "can't log-in! ".

when I tried to login as admin and hit admin log in, I got "can't log-in! "; if hit log in, i got "can't log-in! ".

Why? I did the same thing for the classified ad starter kit, it worked fine.

4. access:

how can I add users like dale to be able to "add employee and enter related info"?

how can i set managers like admin to be able to "modify the employee info and delete employee info"?

Thanks a lot. -Dale

{quote}
joycsc wrote:
Rather using the solution, open 2008 VWD express, go to File -> Open Web Site, point to the location where the employee info starter kit web site is located on your local directory, and once it opens, just press F5 to run the web site!

NEW POST: Error in running the Employee Info Starter Kit first time

joycsc — Wed, 20 May 2009 13:14:36 GMT

Rather using the solution, open 2008 VWD express, go to File -> Open Web Site, point to the location where the employee info starter kit web site is located on your local directory, and once it opens, just press F5 to run the web site!

dalewz wrote:
Hi There,

I am very interested in this good work. But I had encountered some problems when I ran it first time.

I had installed the 2008 VWD express, 2008 SQL database express, and this kit in order. When I clicked on e-i-s-k-2008.sln and hit F5, I got the following:

1. in address bar:
http://localhost:3301/web/

2. in browser window:
Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: An error occurred loading a configuration file: Failed to start monitoring changes to 'H:\Projects\Eisk 2.2.0.1 - VS 2005-2008 Edition\source\web' because the network BIOS command limit has been reached. For more information on this error, please refer to Microsoft knowledge base article 810886. Hosting on a UNC share is not supported for the Windows XP Platform.

Source Error:

No relevant source lines

Source File: H:\Projects\Eisk 2.2.0.1 - VS 2005-2008 Edition\source\web\web.config Line: 0

Can some experts help?

Many thanks, -Dale

NEW POST: Error in running the Employee Info Starter Kit first time

dalewz — Fri, 15 May 2009 15:28:43 GMT

Hi There,

I am very interested in this good work. But I had encountered some problems when I ran it first time.

I had installed the 2008 VWD express, 2008 SQL database express, and this kit in order. When I clicked on e-i-s-k-2008.sln and hit F5, I got the following:

1. in address bar:
http://localhost:3301/web/

2. in browser window:
Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: An error occurred loading a configuration file: Failed to start monitoring changes to 'H:\Projects\Eisk 2.2.0.1 - VS 2005-2008 Edition\source\web' because the network BIOS command limit has been reached. For more information on this error, please refer to Microsoft knowledge base article 810886. Hosting on a UNC share is not supported for the Windows XP Platform.

Source Error:

No relevant source lines

Source File: H:\Projects\Eisk 2.2.0.1 - VS 2005-2008 Edition\source\web\web.config Line: 0

Can some experts help?

Many thanks, -Dale

NEW POST: Any documentation/tutorial ?

joycsc — Tue, 21 Apr 2009 06:36:36 GMT

Please check the latest version that includes detailed documentations and whitepapers https://code.msdn.microsoft.com/Release/ProjectReleases.aspx?ProjectName=eisk&ReleaseId=2550.

elxany wrote:
Hi, thanks for quick reply.
Is it possible to place a "quick start" steps that will made this project better understandable for mid-level guys?

NEW POST: Version Legends for Employee Info Starter Kit

joycsc — Tue, 21 Apr 2009 06:28:42 GMT

We are planning to release several new versions of Employee Info Starter Kit, focused on several new technologies, like Silverlight, ASP.NET MVC, LINQ, SQL Server CLR Stored Procedure and so on. To keep the versions well organized, here is a version legend that we'll be considering.

There will be 4 part of each version (for example A.B.C.D), as mentioned below

A: The major version. It includes but not limited to, the first digit of .net framework that been used there. For instance v2.2.0 is based .net framework 2.0.
B: This version focused on a specific architecture/implmentation model under the major version. For instance v3.1.0 is a version with major version of .net framework 3.5 and may be focused on LINQ implementation model in data access layer, where as v3.1.1 is a version with major version of .net framework 3.5 and may be focused on ASP.NET Framework implementation model in data access layer
C: The newer version (for instance v2.2.1) of this point contains the code optimization, completion of segments that were incomplete or bug fixes with respect to the previous version (for instance v2.2.0)
D: Small bug fixed/fine tuning. Typically a new change in this location doesn't form a new 'Code Gallery' release, but may be visible via the download file name (for instance "VSTS 2008 Edition v2.2.0.1").

UPDATED RELEASE: v2.2.0 (Apr 17, 2009)

Tue, 21 Apr 2009 06:12:51 GMT

This is a starter kit, which includes very simple user requirements, where we can create, read, update and delete (CRUD) the employee info of a company.
The primary purpose of this starter kit is, to provide a solid guideline with respect to building enterprise level projects, by utilizing asp.net 2.0 and Sql server 2005 features, as well as latest best coding practices.

The starter kit includes several cases where we can perform multi-table joining and/or write operations. Combining high performance and security features this starter kit shows how we can solve in real world problems and challenges, from a wide range of view point.

*Minimum System Requirements*

* Visual Studio 2005 (or higher)
* Sql Server 2005 or higher

*User End Functional Specification*

The user end functionalities of this starter kit are pretty simple and straight forward that are focused in to perform CRUD operation on employee records as described below.

+Creating a new employee record+
The users should be able to create new employee record, one at a single time.
+Read existing employee record+
The users should be able to view the employee records in list style, where maximum 10 records can be visible per page and the list can be filtered out based on their supervisors. The user should also be able to view employee records with details, once at a single time and can print it in a printable format.
+Update an existing employee record+
The users should be able to update an existing employee record, one at a single time.
+Delete existing employee records+
The users should be able to delete single or multiple employees at a time while viewing employee records in list style.

*Architectural Overview*

* Simple 2 layer architecture (user interface and data access layer) with 1 optional cache layer
* ASP.NET Web Form Based User Interface
* Custom Entity Data Container implemented (with primitive C# types for data fields)
* Static type CRUD methods embedded with Data container, implemented in C#
* Sql Server Stored Procedure to perform actual CRUD operation
* Automated testing infrastructure to ensure quality

*Technology Utilized*

+Programming Languages/Scripts+
* Browser side: JavaScript
* Web server side: C# 2.0
* Database server side: T-SQL

+.NET Framework Components+
* .net 2.0 generic type
* .net 2.0 nullable type
* asp.net 2.0 object data source
* asp.net 2.0 grid view
* asp.net 2.0 form view
* asp.net 2.0 skin
* asp.net 2.0 theme
* asp.net 2.0 master

+Visual Studio Features+
* Visual Studio Unit Test
* Visual Studio Database Unit Test
* Visual Studio Web Test
* Visual Studio Load Test
* Visual Studio Ordered Test

+Sql Server Features+
* Sql server 2005 Stored Procedure
* Sql server 2005 Xml type
* Sql server 2005 Paging support

UPDATED WIKI: Home

joycsc — Mon, 20 Apr 2009 13:16:52 GMT

Resource Page Description

This is a starter kit, which includes very simple user requirements, where we can create, read, update and delete (crud) the employee info of a company.

The primary purpose of this starter kit is, to provide a solid guideline with respect to building enterprise level projects, by utilizing new asp.net 2.0 and sql server 2005 features, as well as latest best coding practices.

The starter kit includes several cases where we can perform multi-table joining and/or write operations. Combining high performance and security features this starter kit shows how we can solve in real world problems and challenges, from a wide range of view point.

Quick link

Download latest version of Employee Info Starter Kit (Visual Studio 2005-2008 Edition):
http://code.msdn.microsoft.com/Project/Download/FileDownload.aspx?ProjectName=eisk&DownloadId=5474

Download latest version of Employee Info Starter Kit with Automated Tests (Visual Studio Team System 2008 Edition):
http://code.msdn.microsoft.com/Project/Download/FileDownload.aspx?ProjectName=eisk&DownloadId=5476

NEW POST: Documentation and enhancements

joycsc — Mon, 20 Apr 2009 12:55:55 GMT

Supremestar,

Please check the latest version now that includes lots of enhancements and requierd documentations. Stay tuned with the upcoming version that will include LINQ/MVC/Azure samples.

Supremestar wrote:
Ashraful,

This is great starting point for everyone who wants to develop an enterprise level project. Having said that It needs some documentation. Do you have any plans to provide documentation and enhancements.

Have you planned new release with more functionality. It will be very helpful for everyone in the community if you could provide us more insights and carry on adding futures on regular basis.

Thanking you.

NEW POST: Product Documentation Request

joycsc — Mon, 20 Apr 2009 12:53:48 GMT

johnwilk wrote:
Can someone please provide a simple to understand step by step guide on how to set this up? (Or if anyone has successfully installed this and got it working I would much appreciate a guide on how you did it :)

As promised check the new version that includes a detailed documentation. Enjoy!

UPDATED RELEASE: v2.2.0 (Apr 17, 2009)

Mon, 20 Apr 2009 12:31:37 GMT

This is a starter kit, which includes very simple user requirements, where we can create, read, update and delete (CRUD) the employee info of a company.
The primary purpose of this starter kit is, to provide a solid guideline with respect to building enterprise level projects, by utilizing asp.net 2.0 and Sql server 2005 features, as well as latest best coding practices.

The starter kit includes several cases where we can perform multi-table joining and/or write operations. Combining high performance and security features this starter kit shows how we can solve in real world problems and challenges, from a wide range of view point.

*Minimum System Requirements*

* Visual Studio 2005 (or higher)
* Sql Server 2005 or higher

*User End Functional Specification*

The user end functionalities of this starter kit are pretty simple and straight forward that are focused in to perform CRUD operation on employee records as described below.

+Creating a new employee record+
The users should be able to create new employee record, one at a single time.
+Read existing employee record+
The users should be able to view the employee records in list style, where maximum 10 records can be visible per page and the list can be filtered out based on their supervisors. The user should also be able to view employee records with details, once at a single time and can print it in a printable format.
+Update an existing employee record+
The users should be able to update an existing employee record, one at a single time.
+Delete existing employee records+
The users should be able to delete single or multiple employees at a time while viewing employee records in list style.

*Architectural Overview*

* Simple 2 layer architecture (user interface and data access layer) with 1 optional cache layer
* ASP.NET Web Form Based User Interface
* Custom Entity Data Container implemented (with primitive C# types for data fields)
* Static type CRUD methods embedded with Data container, implemented in C#
* Sql Server Stored Procedure to perform actual CRUD operation
* Automated testing infrastructure to ensure quality

*Technology Utilized*

+Programming Languages/Scripts+
* Browser side: JavaScript
* Web server side: C# 2.0
* Database server side: T-SQL

+.NET Framework Components+
* .net 2.0 generic type
* .net 2.0 nullable type
* asp.net 2.0 object data source
* asp.net 2.0 grid view
* asp.net 2.0 form view
* asp.net 2.0 skin
* asp.net 2.0 theme
* asp.net 2.0 master

+Visual Studio Features+
* Visual Studio Unit Test
* Visual Studio Database Unit Test
* Visual Studio Web Test
* Visual Studio Load Test

+Sql Server Features+
* Sql server 2005 Stored Procedure
* Sql server 2005 Xml type
* Sql server 2005 Paging support

UPDATED RELEASE: v2.2.0 (Apr 17, 2009)

Mon, 20 Apr 2009 10:37:23 GMT

This is a starter kit, which includes very simple user requirements, where we can create, read, update and delete (CRUD) the employee info of a company.
The primary purpose of this starter kit is, to provide a solid guideline with respect to building enterprise level projects, by utilizing asp.net 2.0 and Sql server 2005 features, as well as latest best coding practices.

The starter kit includes several cases where we can perform multi-table joining and/or write operations. Combining high performance and security features this starter kit shows how we can solve in real world problems and challenges, from a wide range of view point.

*Minimum System Requirements*

* Visual Studio 2005 (or higher)
* Sql Server 2005 or higher

*User End Functional Specification*

The user end functionalities of this starter kit are pretty simple and straight forward that are focused in to perform CRUD operation on employee records as described below.

+Creating a new employee record+
The users should be able to create new employee record, one at a single time.
+Read existing employee record+
The users should be able to view the employee records in list style, where maximum 10 records can be visible per page and the list can be filtered out based on their supervisors. The user should also be able to view employee records with details, once at a single time and can print it in a printable format.
+Update an existing employee record+
The users should be able to update an existing employee record, one at a single time.
+Delete existing employee records+
The users should be able to delete single or multiple employees at a time while viewing employee records in list style.

*Architectural Overview*

* Simple 2 layer architecture (user interface and data access layer) with 1 optional cache layer
* ASP.NET Web Form Based User Interface
* Custom Entity Data Container implemented (with primitive C# types for data fields)
* Static type CRUD methods embedded with Data container, implemented in C#
* Sql Server Stored Procedure to perform actual CRUD operation
* Automated testing infrastructure to ensure quality

*Technology Utilized*

+Programming Languages/Scripts+
* Browser side: JavaScript
* Web server side: C# 2.0
* Database server side: T-SQL

+.NET Framework Components+
* .net 2.0 generic type
* .net 2.0 nullable type
* asp.net 2.0 object data source
* asp.net 2.0 grid view
* asp.net 2.0 form view
* asp.net 2.0 skin
* asp.net 2.0 theme
* asp.net 2.0 master

+Visual Studio Features+
* Visual Studio Unit Test
* Visual Studio Database Unit Test
* Visual Studio Web Test
* Visual Studio Load Test

+Sql Server Features+
* Sql server 2005 Stored Procedure
* Sql server 2005 Xml type
* Sql server 2005 Paging support

UPDATED RELEASE: v2.2.1 (Apr 17, 2009)

Mon, 20 Apr 2009 08:49:19 GMT

This is a starter kit, which includes very simple user requirements, where we can create, read, update and delete (CRUD) the employee info of a company.
The primary purpose of this starter kit is, to provide a solid guideline with respect to building enterprise level projects, by utilizing asp.net 2.0 and Sql server 2005 features, as well as latest best coding practices.

The starter kit includes several cases where we can perform multi-table joining and/or write operations. Combining high performance and security features this starter kit shows how we can solve in real world problems and challenges, from a wide range of view point.

*Minimum System Requirements*

* Visual Studio 2005 (or higher)
* Sql Server 2005 or higher

*User End Functional Specification*

The user end functionalities of this starter kit are pretty simple and straight forward that are focused in to perform CRUD operation on employee records as described below.

+Creating a new employee record+
The users should be able to create new employee record, one at a single time.
+Read existing employee record+
The users should be able to view the employee records in list style, where maximum 10 records can be visible per page and the list can be filtered out based on their supervisors. The user should also be able to view employee records with details, once at a single time and can print it in a printable format.
+Update an existing employee record+
The users should be able to update an existing employee record, one at a single time.
+Delete existing employee records+
The users should be able to delete single or multiple employees at a time while viewing employee records in list style.

*Architectural Overview*

* Simple 2 layer architecture (user interface and data access layer) with 1 optional cache layer
* ASP.NET Web Form Based User Interface
* Custom Entity Data Container implemented (with primitive C# types for data fields)
* Static type CRUD methods embedded with Data container, implemented in C#
* Sql Server Stored Procedure to perform actual CRUD operation
* Automated testing infrastructure to ensure quality

*Technology Utilized*

+Programming Languages/Scripts+
* Browser side: JavaScript
* Web server side: C# 2.0
* Database server side: T-SQL

+.NET Framework Components+
* .net 2.0 generic type
* .net 2.0 nullable type
* asp.net 2.0 object data source
* asp.net 2.0 grid view
* asp.net 2.0 form view
* asp.net 2.0 skin
* asp.net 2.0 theme
* asp.net 2.0 master

+Visual Studio Features+
* Visual Studio Unit Test
* Visual Studio Database Unit Test
* Visual Studio Web Test
* Visual Studio Load Test

+Sql Server Features+
* Sql server 2005 Stored Procedure
* Sql server 2005 Xml type
* Sql server 2005 Paging support