ASP.NET at Work: Building 10 Enterprise Projects PHẦN 10 ppt

The first stored procedure you need is used in the first page, where the teams are shown along with the number of projects for each.. The code is shown in Listing 10.3.CREATE PROCEDURE d

For each timecard, we keep track of how many hours were spent, what date they were used, and what the individual’s hourly rate is This way, we can generate project- status information to be shown at the task and project levels We also require that a description of the member’s work be stored in the timecard This enables you to keep

a running history of what has been accomplished by your team

Creating the Views

We have two views that will help us aggregate billing and budget information for the task and project views We do this to remove some of the more complex SQL code that would otherwise be required to get summary information, in addition to join to other tables

The first view we create sums up the hours and dollars for timecards, grouped by task number The code for this view is shown in Listing 10.1.

CREATE VIEW vw_SummarizeTimecardsByTask

FROM dbo.tblTasks T INNER JOIN

dbo.vw_SummarizeTimecardsByTask V ON T.pkTaskID = V.fkTaskID

GROUP BY T.fkProjectID

Listing 10.2 vw_SummarizeTasksByProject

You’ll be seeing these views in a number of different places in the application as you work through the project

Creating the Stored Procedures

As usual, we are making extensive use of stored procedures for this portion of the application The primary reason we’re doing this is to help remove some of the need to build grids manually If we can get all the information from the database in the proper format, we can just feed it into the various Repeater controls instead of having to man- ually build all the tables; a few tables, however, will still have to be built manually The first stored procedure you need is used in the first page, where the teams are shown along with the number of projects for each The code is shown in Listing 10.3.CREATE PROCEDURE dbo.sp_RetrieveProjectCountByTeam

The next stored procedure we need to build returns all the projects for a particular team We’re doing a good deal of data formatting in this stored procedure to make it easier to display in the Web page The code for this stored procedure is shown in List- ing 10.4.

CREATE PROCEDURE dbo.sp_RetrieveProjectsByTeam

P.*, M.LastName + ‘, ‘ + M.FirstName As ProjectLead

FROM tblProjects P, tblMembers M

WHERE fkTeamID = @TeamID

AND fkCreatorID = M.pkMemberID

ORDER BY P.Name

Listing 10.4 sp_RetrieveProjectsByTeam

This joins the projects table with the members table in order to retrieve the project lead’s name If you wanted to, you could create a link to the member viewer so that

clicking the project leader’s name would bring up his or her profile Just copy the code used here to generate a link to the Project_view.aspx file and point to Member_ view.aspx

In order to show the Project Detail page, we have to run a fairly long query in order

to gather the data required for the page The code for this stored procedure is shown in Listing 10.5.

CREATE procedure sp_RetrieveProjectDetails

ProjectBudget = CONVERT(varchar, (SELECT SUM(Budget) FROM tblTasks

WHERE fkProjectID = @ProjectID), 1),

ProjectHours = IsNull((SELECT HoursByProject FROM

vw_SummarizeTasksByProject WHERE fkProjectID = @ProjectID), 0),

ProjectTotal = CONVERT(varchar, IsNull((SELECT TotalByProject FROM

vw_SummarizeTasksByProject WHERE fkProjectID = @ProjectID), 0), 1)

FROM tblProjects P, tblMembers M

WHERE P.fkCreatorID = M.pkMemberID

AND P.pkProjectID = @ProjectID

Listing 10.5 sp_RetrieveProjectDetails

There are a number of subqueries in this routine, so let’s go through it a little bit at a time We first tie into the tblMembers table to get the project lead’s name As in the other stored procedure, you could change this to return a link to the member’s profile.

We return a text version of the completion status so that we can display Yes or No We then calculate the number of tasks in the project This value is used to determine whether or not the project can be deleted, since we don’t allow deletions of projects once tasks have been added

Next, we add up the task budgets to determine the overall project budget Doing this summarization this way means less data entry and math for the team leader Once the task budgets are entered, the project budget is just a summary of them

We then use the view we created to determine how many hours and dollars have been expended on this project to date Since there is a possibility that no time has been spent on this project, we have code that converts null values to zeroes We also format the result using grouping symbols (commas) and two decimal places We don’t need to convert the number of hours, but we do check it for possible null results All of these results are shown on the project viewer in the header of the page

The next stored procedure returns all the tasks for a particular project The code for

it is shown in Listing 10.6.

CREATE PROCEDURE dbo.sp_RetrieveTasksByProject

@ProjectID intAS

SELECTT.pkTaskID,T.fkProjectID,T.Name,

‘<a href=”task_view.aspx?id=’

+ convert(varchar, T.pkTaskID) + ‘“>’

+ T.Name + ‘</a>’ As TaskNameWithLink,T.Description,

T.DueDate,DueDateStatus = (CASE

WHEN DueDate < getdate() THEN ‘#FF0000’

ELSE ‘#000000’

END),T.Budget,TaskStatus = (CASE WHEN T.IsCompleted = 1 THEN ‘Yes’ ELSE ‘No’ END)FROM tblTasks T

WHERE T.fkProjectID = @ProjectIDORDER BY DueDate

Listing 10.6 sp_RetrieveTasksByProject

This routine, given a project number, returns all the tasks associated with that ect Besides returning the files, it also returns other status information that is used in the display The DueDateStatus looks at whether the due date of the task has passed If

proj-so, it returns a color code for red This color code is used to change the color of the due date field in the list The TaskStatus field changes the 0 or 1 of the IsCompleted field into a Yes or No for display purposes We can use the data without having to do a lot

of manual formatting

Once the user selects a task, we have to show the details of that task The stored cedure to perform this function is similar to the one used to retrieve the project details and is shown in Listing 10.7.

Team-Fly®

CREATE PROCEDURE sp_RetrieveTaskDetails

TaskBudget = CONVERT(varchar, Budget, 1),

TaskHours = IsNull((SELECT HoursByTask FROM

vw_SummarizeTimecardsByTask WHERE fkTaskID = @TaskID), 0),

TaskTotal = CONVERT(varchar, IsNull((SELECT TotalByTask FROM

vw_SummarizeTimecardsByTask WHERE fkTaskID = @TaskID), 0), 1),

TimecardCount = (SELECT COUNT(*) FROM tblTimecards WHERE fkTaskID =

@TaskID)

FROM tblTasks T, tblProjects P

WHERE T.pkTaskID = @TaskID

AND T.fkProjectID = P.pkProjectID

Listing 10.7 sp_RetrieveTaskDetails

Instead of looking at the project summary view, we use the task summary view, which adds the timecards by task number We take this information, accounting for any nulls that might exist for tasks without timecards, and use it in the Task Detail win- dow

The final stored procedure that we need retrieves the timecards for a particular task.

We can show the work that has been accomplished for a particular task in the task viewer The code for this stored procedure is shown in Listing 10.8.

CREATE PROCEDURE sp_RetrieveTimecardsByTask

(SELECT pkTaskID FROM tblTasks WHERE fkProjectID IN

(SELECT pkProjectID FROM tblProjects WHERE fkCreatorID = @MemberID)))THEN

‘<a href=”tcard_create.aspx?id=’ + convert(varchar, pkTimecardID) +

‘“>’ + convert(varchar, TimecardDate, 101) + ‘</a>’

ELSE

convert(varchar, TimecardDate, 101)

END),

Listing 10.8 sp_RetrieveTimecardsByTask

WHERE T.fkMemberID = M.pkMemberID

AND T.fkTaskID = @TaskID

ORDER BY TimecardDate

Listing 10.8 sp_RetrieveTimecardsByTask (continued)

As with some of the other bit fields, we change the IsBilled bit into a Yes or No, which is shown in the Repeater control We also show the member name by joining to the tblMembers table You see who has been working on the task without having to click any additional links As with the other member names that we’ve shown, you could change this into a link to the Member Profile page

This page also generates a link to the timecard editor only if the member viewing the information (supplied by the member ID parameter) is the creator of the timecard or is the project manager In addition, the timecard has to be in an unbilled state Otherwise,

we would be changing history, and most accountants and CFOs get a bit upset about this When viewing this page, unauthorized users will just see the date of the timecard and not the link.

We have another stored procedure that returns the total hours and total dollars expended to date on each task This code is shown in Listing 10.9.

CREATE procedure sp_RetrieveTaskStatistics

The next stored procedure we need to build retrieves timecards that have not been billed yet This data is shown on the project invoice, and the code is shown in Listing 10.10.

CREATE PROCEDURE sp_RetrieveUnbilledTimecardsByProject

CONVERT(varchar, TC.HourlyRate, 1) As Rate,

CONVERT(varchar, TC.HourlyRate * TC.HourCount, 1) As TimecardTotal

FROM tblTimecards TC, tblTasks T, tblMembers M

WHERE fkTaskID IN

(SELECT pkTaskID FROM tblTasks WHERE fkProjectID = @ProjectID)

AND TC.fkTaskID = T.pkTaskID

AND TC.fkMemberID = M.pkMemberID

AND IsBilled = 0

Listing 10.10 sp_RetrieveUnbilledTimecardsByProject

We use this stored procedure to retrieve all timecards for a project that has not been billed for yet The Project Invoice page uses this routine to display the invoice, which the team leader can then print This is a particularly complex query, since we have to drill into the tasks table and find all the possible tasks in the timecards table It’s much easier to call the stored procedure from the ASP.NET page than to try to embed all this SQL code in the page

Another stored procedure used in the invoicing process is the following, which determines what the invoice total should be by adding all the unbilled timecards The code is shown in Listing 10.11

CREATE PROCEDURE sp_RetrieveUnbilledTotalByProject

CREATE PROCEDURE sp_UpdateTimecardsByProject

With the stored procedures out of the way, we can build the business objects for the subsystem.

Building the Business Objects

We have a total of six new objects to add to our Teamwork Network assembly: Project, Task, Timecard, and three corresponding exception classes We are following the same design pattern for these objects as we have used in previous projects, so you should be able to quickly build these objects The first object is the Project object, and its code is shown in Listing 10.13.

Imports AtWorkUtilities

Public Class Project

Inherits BaseServices

‘

‘ If no arguments are supplied, build a separate

‘ database connection for this object

‘

Public Sub New()

MyBase.New(New Database(), “SELECT * FROM tblProjects WHERE 1=0”)End Sub

‘

‘ If database connection is supplied, store it

‘ in the private connection variable for this

‘ object

‘

Public Sub New(ByVal db As Database)

Listing 10.13 Project class

MyBase.New(db, “SELECT * FROM tblProjects WHERE 1=0”)

End Sub

‘

‘ If both database and ID are supplied, retrieve

‘ data into the object from the database

‘ Verify that all data validation rules have been

‘ met Any errors get stored into the errors collection

‘ inherited from the BaseServices class

‘ Checks an individual row for validation rule

‘ compliance Any errors are added to the errors

‘ The base Save method stores the DataRow into the

‘ DataSet, whether it’s a new or existing row The

‘ rest of this routine handles specific validation

‘ for this type of data

‘ We separate the SaveRow method from the Save method

‘ to give us a chance to handle any validation We have

‘ a verification here that the data is good before we

‘ continue, however

‘

Public Sub Save()

If Not Me.IsValid Then

Throw New ProjectException(Me.ValidationError)Exit Sub

End If

m_DA.Update(m_DS)

End Sub

‘

‘ Since we only have a single row in our DataSet,

‘ delete it and then update the database with the

We enforce our validation rules for the tblProjects table by way of this class Unlike some other classes we’ve built, all fields but the Description field are required in this table, so we have to check them all We use the SaveRow routine to default the IsCom- pleted field to a zero, but we populate the rest of the fields by way of our form

The associated exception class is called ProjectException and is shown in Listing 10.14 This exception is only generated if an attempt is made to call the Save method while data-validation errors are present in the data

Public Class ProjectException

Listing 10.14 ProjectException class

The next object to build links the application to the tblTasks table The Task class is shown in Listing 10.15

Imports AtWorkUtilities

Public Class Task

Inherits BaseServices

‘

‘ If no arguments are supplied, build a separate

‘ database connection for this object

‘

Public Sub New()

MyBase.New(New Database(), “SELECT * FROM tblTasks WHERE 1=0”)

End Sub

‘

‘ If database connection is supplied, store it

‘ in the private connection variable for this

‘ object

Listing 10.15 Task class

Public Sub New(ByVal db As Database)

MyBase.New(db, “SELECT * FROM tblTasks WHERE 1=0”)

End Sub

‘

‘ If both database and ID are supplied, retrieve

‘ data into the object from the database

‘ Verify that all data validation rules have been

‘ met Any errors get stored into the errors collection

‘ inherited from the BaseServices class

Next

End Sub

‘

‘ Checks an individual row for validation rule

‘ compliance Any errors are added to the errors

AddError(“Budget amount is missing.”)

‘ The base Save method stores the DataRow into the

‘ DataSet, whether it’s a new or existing row The

‘ rest of this routine handles specific validation

‘ for this type of data

‘ We separate the SaveRow method from the Save method

‘ to give us a chance to handle any validation We have

‘ a verification here that the data is good before we

‘ continue, however

‘

Public Sub Save()

If Not Me.IsValid Then

Throw New TaskException(Me.ValidationError)

‘ Since we only have a single row in our DataSet,

‘ delete it and then update the database with the

‘ change

Listing 10.15 Task class (continued)

‘Public Sub Delete()

If m_DS.Tables(0).Rows.Count > 0 Thenm_DS.Tables(0).Rows(0).Delete()m_DA.Update(m_DS)

End IfEnd Sub

End Class

Listing 10.15 Task class (continued)

Like the Project class, all the fields of the Task object are required except for the Description field Any missing fields are flagged as errors and are displayed on the Web page While the budget and default hourly-rate fields are required, they can be zero If, for instance, you have an internal project that doesn’t really have a budget, you may want to assign a zero hourly rate but still track the number of hours spent The SaveRow method defaults these two fields, as well as the IsCompleted field, to zero The associated exception is called TaskException and follows the same pattern as all the other custom exception classes we’ve built The code for it is shown in Listing 10.16 Public Class TaskException

Inherits Exception

Public Sub New()MyBase.New()End Sub

Public Sub New(ByVal Message As String)MyBase.New(Message)

Listing 10.16 TaskException class

The final classes you need to build relate to the timecard feature of the application The Timecard class is shown in Listing 10.17

‘ If no arguments are supplied, build a separate

‘ database connection for this object

‘

Public Sub New()

MyBase.New(New Database(), “SELECT * FROM tblTimecards WHERE 1=0”)

End Sub

‘

‘ If database connection is supplied, store it

‘ in the private connection variable for this

‘ object

‘

Public Sub New(ByVal db As Database)

MyBase.New(db, “SELECT * FROM tblTimecards WHERE 1=0”)

End Sub

‘

‘ If both database and ID are supplied, retrieve

‘ data into the object from the database

‘ Verify that all data validation rules have been

‘ met Any errors get stored into the errors collection

‘ inherited from the BaseServices class

‘ Checks an individual row for validation rule

‘ compliance Any errors are added to the errors

‘ collection

Listing 10.17 Timecard class (continued)

‘ The base Save method stores the DataRow into the

‘ DataSet, whether it’s a new or existing row The

‘ rest of this routine handles specific validation

‘ for this type of data

‘ We separate the SaveRow method from the Save method

‘ to give us a chance to handle any validation We have

‘ a verification here that the data is good before we

‘ continue, however

‘

Public Sub Save()

If Not Me.IsValid Then

Throw New TimecardException(Me.ValidationError)Exit Sub

Listing 10.17 Timecard class (continued)

End If

m_DA.Update(m_DS)

End Sub

‘

‘ Since we only have a single row in our DataSet,

‘ delete it and then update the database with the

Listing 10.17 Timecard class (continued)

Every field in this class is required, so we have to validate each one For the large text field (WorkDescription), we use the maximum length in our CheckRequiredField routine, just in case the person creating the timecard is really verbose We also default the hourly rate and the IsBilled fields to zero if they are left blank in the SaveRow rou- tine

The associated exception class is called TimecardException and is shown in Listing 10.18.

Public Class TimecardException

With the business objects done, be sure to rebuild the assembly and copy it to your Web directory The next step is to build the Web pages for this application

Building the Web Pages

Since there are quite a few Web pages for this application, we’re going to break them into logical categories related to the main objects in the system: Project, Task, and Time- card This should make it a bit easier to follow the flow of the application in this proj- ect Because of the large amount of data we’re dealing with in these objects, these pages are generally bigger than the others you’ve built so far However, we are building on what you already know, so the code should still look familiar to you

Creating the Project Pages

We start with the pages that view and maintain the projects in the system The first page is the one linked to the main toolbar and is called Projects.aspx The ASPX file is shown in Listing 10.19.

<%@ Page Inherits=”TWNW.Projects” Src=”projects.aspx.vb” %>

<%@ Register Tagprefix=”TWNW” Tagname=”Header” Src=”Header.ascx” %>

<%@ Register Tagprefix=”TWNW” Tagname=”Footer” Src=”Footer.ascx” %>

<!DOCTYPE HTML PUBLIC “-//W3C//DTD HTML 4.0 Transitional//EN”>

<html>

<head>

<title>Teamwork Network: View Projects</title>

<link href=”styles.css” rel=”stylesheet” type=”text/css”>

</head>

<body leftmargin=0 topmargin=0>

<TWNW:Header id=”PageHeader” runat=”server” />

This page is designed to show just the team name and the number of projects ciated with the team This page performs two queries to do this, so we have to build the content table ourselves We have a label control called lblContent into which we’ll put the HTML that we generate in our code The code behind this page is shown in Listing 10.20.

Protected lblContent As Label

Sub Page_Load(objSender As Object, objArgs As EventArgs)

If (Request.Cookies(“mID”) Is Nothing) Then

Dim DB As New AtWorkUtilities.Database()

Dim DB2 As New AtWorkUtilities.Database()

Dim DR, DR2 As SqlDataReader

Dim strContent As New System.Text.StringBuilder()

Dim strColor As String = “tabletext”

‘

‘ Check for any new postings in the member’s teams

‘ or in the public forum

ElsestrContent.AppendFormat(“<td align=middle>{0}</td>”, _DR2(“Total”))

End IfstrContent.Append(“</tr>”)

If strColor = “tabletext” Then strColor = “tabletext_gray”

ElsestrColor = “tabletext”

End IfstrContent.Append(Environment.NewLine)DR2.Close()

Listing 10.20 projects.aspx.vb (continued)

We use the sp_RetrieveTeamsByMember stored procedure as the outer loop of this page For each team that we display, we need to look up the number of projects associ- ated with that team We use a second Database object here, since we can only have a single SqlDataReader open at a time per connection We run the sp_RetrieveProject- CountByTeam stored procedure, get our result back, and put it into the HTML Once we’ve displayed the data, we close the second SqlDataReader object and repeat the process

The next page the user would see shows all the projects for a particular team The code for this page is shown in Listing 10.21

<%@ Page Inherits=”TWNW.ProjectsView” Src=”projects_view.aspx.vb” %>

<%@ Register Tagprefix=”TWNW” Tagname=”Header” Src=”Header.ascx” %>

<%@ Register Tagprefix=”TWNW” Tagname=”Footer” Src=”Footer.ascx” %>

<!DOCTYPE HTML PUBLIC “-//W3C//DTD HTML 4.0 Transitional//EN”>

<html>

<head>

<title>Teamwork Network: View Team Projects</title>

<link href=”styles.css” rel=”stylesheet” type=”text/css”>

</head>

<body leftmargin=0 topmargin=0>

<TWNW:Header id=”PageHeader” runat=”server” />

<asp:label id=”lblPageTitle” class=”pageheading” runat=”server” />

<p class=”text”>

<a href=”project_create.aspx?tID=<% = Request.QueryString(“tID”)

Listing 10.21 projects_view.aspx

Listing 10.21 projects_view.aspx (continued)

We’re using the same page-design model here to show the projects for the team so that we can show the due date in an alternate color In some of the other pages, we’ll

do the same thing by way of the stored procedure Both methods are shown here so that you can get ideas for your own applications.

At the top of the page, a link is displayed for users who want to create a new ect In order to create a new project, you need a team ID By generating the link in this way, you force the team ID to always be supplied This prevents errors later on

proj-The Visual Basic code behind this file is shown in Listing 10.22

Protected lblPageTitle As Label

Protected lblContent As Label

Sub Page_Load(objSender As Object, objArgs As EventArgs)

Dim strColor As String = “tabletext”

If (Request.Cookies(“mID”) Is Nothing) Then

Response.Redirect(“login.aspx?msg=403&rURL=” _

Listing 10.22 projects_view.aspx.vb

& Request.ServerVariables(“SCRIPT_NAME”) _

& “?” _

& Request.ServerVariables(“QUERY_STRING”))End If

Dim DB As New AtWorkUtilities.Database()

Dim objReader As SqlDataReader

Dim T As New Team(DB, Request.QueryString(“tID”))

Dim DR As DataRow = T.GetRow()

Dim strOutput As New System.Text.StringBuilder()

Dim strFont As String = “#000000”

lblPageTitle.Text = DR(“Name”) & “ Projects”

objReader = DB.GetDataReader(“sp_RetrieveProjectsByTeam “ _

& Request.QueryString(“tID”), True)

Do While objReader.Read()

strOutput.AppendFormat(“<tr class=””{0}””>”, _strColor)

strOutput.AppendFormat(“<td>{0}</td>”, _objReader(“ProjectName”))

strOutput.AppendFormat(“<td>{0}</td>”, _objReader(“ProjectLead”))

strOutput.AppendFormat(“<td>{0}</td>”, _objReader(“Description”))

If DateTime.Compare(objReader(“DueDate”), _DateTime.Now()) < 0 Then

strFont = “#FF0000”

ElsestrFont = “#000000”

End IfstrOutput.Append(“<td align=””center””>”)strOutput.AppendFormat(“<font color=””{0}””>{1}</font></td>”, _strFont, objReader(“DueDate”).ToShortDateString)

strOutput.Append(“</tr>” & Environment.NewLine)

If strColor = “tabletext” ThenstrColor = “tabletext_gray”

ElsestrColor = “tabletext”

End IfLoop

This page uses the Team object to retrieve the name of the team An ASP.NET label control is used to restrict the page title to the lower corner of the main area of the win- dow We then instruct the routine to retrieve the projects for the particular team being viewed and start building our table We’re marking any tasks that are late (due date is less than the current date) in red through Visual Basic code instead of directly in the stored procedure When we’re done building the table, we store it in the label control

on the page

Now a user can create a new project from this page The code for the ASPX file is shown in Listing 10.23.

<%@ Page Inherits=”TWNW.ProjectCreate” Src=”project_create.aspx.vb” %>

<%@ Register Tagprefix=”TWNW” Tagname=”Header” Src=”Header.ascx” %>

<%@ Register Tagprefix=”TWNW” Tagname=”Footer” Src=”Footer.ascx” %>

<!DOCTYPE HTML PUBLIC “-//W3C//DTD HTML 4.0 Transitional//EN”>

<html>

<head>

<title>Teamwork Network: Project Management</title>

<link href=”styles.css” rel=”stylesheet” type=”text/css”>

<input type=”hidden” runat=”server” id=”pkProjectID”>

<input type=”hidden” runat=”server” id=”fkTeamID”>

<asp:textbox id=”txtDescription”

Listing 10.23 project_create.aspx (continued)

This ASPX file is a standard data-entry form similar to the others we’ve built for the Teamwork Network application We provide reasonable space for the dates required, since it’s hard to have a maximum length for the date October 21, 2001, is just as valid

a date as 10/1/2001 Pick a reasonable amount, and let the code-behind and the object take care of the parsing and validation

The code behind this page is shown in Listing 10.24

Protected pkProjectID As HTMLControls.HTMLInputHidden

Protected fkTeamID As HTMLControls.HTMLInputHidden

Protected txtName As TextBox

Protected txtDescription As TextBox

Protected txtStartDate As TextBox

Protected txtDueDate As TextBox

Protected chkIsComplete As CheckBox

Protected lblPageTitle As Label

Protected lblErrorMessage As Label

Sub Page_Load(objSender As Object, objArgs As EventArgs)

Dim DB As New AtWorkUtilities.Database()

Dim P As Project

Dim DR As DataRow

Dim objCookie As HTTPCookie

Listing 10.24 project_create.aspx.vb

objCookie = Request.Cookies(“mID”)

If Not Page.IsPostBack Then

If Request.QueryString(“ID”) <> “” ThenlblPageTitle.Text = “Edit Project”

P = New Project(DB, Request.QueryString(“ID”))

DR = P.GetRow()pkProjectID.Value = DR(“pkProjectID”).ToString()fkTeamID.Value = DR(“fkTeamID”).ToString()txtName.Text = DR(“Name”).ToString()txtDescription.Text = DR(“Description”).ToString()txtStartDate.Text = DR(“StartDate”).ToShortDateString()txtDueDate.Text = DR(“DueDate”).ToShortDateString()chkIsComplete.Checked = DR(“IsCompleted”)

ElselblPageTitle.Text = “Create New Project”

fkTeamID.Value = Request.QueryString(“tID”)End If

Else

If pkProjectID.Value = “” Then

P = New Project(DB)Else

P = New Project(DB, pkProjectID.Value)End If

DR = P.GetRow()DR(“Name”) = txtName.TextDR(“Description”) = txtDescription.TextDR(“fkTeamID”) = fkTeamID.Value

DR(“fkCreatorID”) = objCookie.ValueTry

DR(“StartDate”) = DateTime.Parse(txtStartDate.Text)Catch ex As Exception

‘ do nothing, object handles missing dataEnd Try

TryDR(“DueDate”) = DateTime.Parse(txtDueDate.Text)Catch ex As Exception

‘ do nothing, object handles missing dataEnd Try

DR(“IsCompleted”) = chkIsComplete.CheckedP.SaveRow(DR)

If Not P.IsValid ThenlblErrorMessage.Text = _P.ValidationError(“<b>ERROR:</b> The following “ _

& “errors were detected in your data:<br>”, _

“&bull;&nbsp;{0}<br>”, “”)Else

P.Save()DB.Close()Response.Redirect(“projects_view.aspx?tID=” _

Listing 10.24 project_create.aspx.vb (continued)

Listing 10.24 project_create.aspx.vb (continued)

We’re going to use this page for both creating new projects and editing existing ones,

so we need the code to load the form if an ID is supplied For creating new projects, the previous page will pass a value for the tID value in the query string For editing an exist- ing project, a page will pass the ID of the project in the ID value in the query string This keeps things simple, and there is no confusion as to what the value means at what time

We populate the form and save data using the Project object The team ID is passed between the modes of the form through the hidden-input field and is stored in the Proj- ect object along with the member ID of the user The member ID comes from the cookie

we created when the member logged in to the system Other than those fields, the rest

of the data comes directly from the input form For the IsCompleted field, which is stored as a bit value in SQL Server, we can store a Visual Basic NET True or False value

in the DataRow The DataRow will properly interpret a True or False value as a zero or one, respectively, and no further conversion is required The same thing is true when

we are loading the form with existing data We set the Checked property of the check box equal to the IsCompleted value, and the box is marked or cleared accordingly

Once members have added timecards to the system, the project lead has the option

to generate an invoice The Invoice page is shown without the normal page headers and footers for easier printing The ASPX file is shown in Listing 10.25

<%@ Page Inherits=”TWNW.ProjectInvoice” Src=”project_invoice.aspx.vb” %>

<!DOCTYPE HTML PUBLIC “-//W3C//DTD HTML 4.0 Transitional//EN”>

<html>

<head>

<title>Teamwork Network: Generate Project Invoice</title>

<link href=”styles.css” rel=”stylesheet” type=”text/css”>

<asp:label id=”lblMessage” class=”text” runat=”server” />

<asp:Repeater id=”rptList” runat=”server”>

<HeaderTemplate>

<p class=”subheading”>Detail of Work Performed</p>

<table cellpadding=”4” cellspacing=”0” width=”100%”>

Listing 10.25 project_invoice.aspx (continued)

This page is similar to the task viewer that you’ll build later in that it shows all the timecards for a specific task However, the difference is that it displays all the unbilled timecards for an entire project, sorted by date The code behind this page is shown in Listing 10.26

Imports TWNWObjects

Namespace TWNW

Public Class ProjectInvoice

Inherits System.Web.UI.Page

Protected lblMessage As Label

Protected lblName As Label

Protected lblProjectLead As Label

Protected lblInvoiceDate As Label

Protected lblInvoiceAmount As Label

Protected rptList As Repeater

Sub Page_Load(objSender As Object, objArgs As EventArgs)

If (Request.Cookies(“mID”) Is Nothing) Then

Response.Redirect(“login.aspx?msg=403&rURL=” _

& Request.ServerVariables(“SCRIPT_NAME”) _

& “?” _

& Request.ServerVariables(“QUERY_STRING”))End If

Dim DB As New AtWorkUtilities.Database()

Dim DR As SqlDataReader = _

DB.GetDataReader(“sp_RetrieveProjectDetails “ _

& Request.QueryString(“ID”))lblName.Text = DR(“Name”)

lblProjectLead.Text = DR(“ProjectLead”)

lblInvoiceDate.Text = DateTime.Now.ToShortDateString()DR.Close()

DR = DB.GetDataReader(“sp_RetrieveUnbilledTotalByProject “ _

& Request.QueryString(“ID”))lblInvoiceAmount.Text = DR(“InvoiceTotal”)

lblMessage.Text = “<br><br><b>All work in this “ _

& “project has been billed.</b>”

Else

rptList.DataSource = DSrptList.DataBind()End If

We’re letting the stored procedure do most of the work to display the lower grid It returns all the appropriate fields for display in the right formats (commas and two deci- mal places for currency amounts) so we don’t need a lot of code to show the data The rest of the information comes from the sp_RetrieveProjectDetails stored procedure that

we used in the project view

Along with showing the invoice, we need a way to mark all the unbilled items as billed This is done using a pair of short files shown in Listing 10.27 (ASPX file) and Listing 10.28 (VB file) There is no visual component to the file, so the ASPX file is just the @Page directive

<%@ Page Inherits=”TWNW.ProjectBill” Src=”project_bill.aspx.vb” %>

Private Sub Page_Load(ByVal sender As System.Object, _

ByVal e As System.EventArgs) Handles MyBase.Load

Dim DB As New AtWorkUtilities.Database()

The last maintenance function required is the ability to delete projects This action is only available if no tasks have been added to the project The ASPX page for this is shown in Listing 10.29.

<%@ Page Inherits=”TWNW.ProjectDelete” Src=”project_delete.aspx.vb” %>

<%@ Register Tagprefix=”TWNW” Tagname=”Header” Src=”Header.ascx” %>

<%@ Register Tagprefix=”TWNW” Tagname=”Footer” Src=”Footer.ascx” %>

<!DOCTYPE HTML PUBLIC “-//W3C//DTD HTML 4.0 Transitional//EN”>

<html>

<head>

<title>Teamwork Network: Project Management</title>

<link href=”styles.css” rel=”stylesheet” type=”text/css”>

</head>

<body>

<TWNW:Header id=”PageHeader” runat=”server” />

<p class=”pageheading”>Delete Project</p>

<p class=”text”>Are you sure you want to delete this project?</p>

<form runat=”server” id=”deleteForm”>

<input type=”hidden” runat=”server” id=”pkID”>

Protected pkID As HTMLControls.HTMLInputHidden

Sub Page_Load(objSender As Object, objArgs As EventArgs)

If Not Page.IsPostBack Then

pkID.Value = Request.QueryString(“ID”)

Listing 10.30 project_delete.aspx.vb