My first DOT NET PROJECT - advice needed

I'm about to start my first Dot Net Project. It seems fairly simple but then
I'm a neophyte. I've just taken a few dot.net courses and have some
background in classic ASP.
The application is web-based. Basically one set of users fills out various
portions of a form, submits the data to another set of users in other
locations who then perform various actions (online and offline) and then post
the item 'job completed' and send it back to the original user. The whole
thing must be HIPAA compliant since the data contains personal health
information. A logon mechanism for users is required.
I envisage a 'form' object with a 'state'. The state will determine what
stage in processing the form is and who can perform what actions on it.
Does anyone have any guidelines or advice we should follow to develop this.
Thanks.

I think the first thing you should do is read the ASP.NET 2.0 quickstart.
Its a very useful guide for inexperienced asp.net developers.

http://www.johntimney.com/home/redir...artv20/aspnet/

Specifically lookout for the wizard controls and login controls in relation
to what you describe below.

Regards

John Timney (MVP)
VISIT MY WEBSITE:
http://www.johntimney.com

"mscertified" <rupert@tigerlily.comwrote in message
news:2E0CAD7D-7C40-4051-ABAC-C499916E65A0@microsoft.com...

Quote:

I'm about to start my first Dot Net Project. It seems fairly simple but
then
I'm a neophyte. I've just taken a few dot.net courses and have some
background in classic ASP.
The application is web-based. Basically one set of users fills out various
portions of a form, submits the data to another set of users in other
locations who then perform various actions (online and offline) and then
post
the item 'job completed' and send it back to the original user. The whole
thing must be HIPAA compliant since the data contains personal health
information. A logon mechanism for users is required.
I envisage a 'form' object with a 'state'. The state will determine what
stage in processing the form is and who can perform what actions on it.
Does anyone have any guidelines or advice we should follow to develop
this.
Thanks.
>

I looked at those pages and they are pretty basic and low-level. What I'm
looking for right now is guidance on how to architect this application. For
instance someone suggested we use a web service. So I'm looking for direction
on how to plan the overall structure of this application rather than get into
details about how to program individual pages or controls.

David

"John Timney (MVP)" wrote:

Quote:

I think the first thing you should do is read the ASP.NET 2.0 quickstart.
Its a very useful guide for inexperienced asp.net developers.
>
http://www.johntimney.com/home/redir...artv20/aspnet/
>
Specifically lookout for the wizard controls and login controls in relation
to what you describe below.
>
Regards
>
John Timney (MVP)
VISIT MY WEBSITE:
http://www.johntimney.com
>
>
"mscertified" <rupert@tigerlily.comwrote in message
news:2E0CAD7D-7C40-4051-ABAC-C499916E65A0@microsoft.com...

Quote:

I'm about to start my first Dot Net Project. It seems fairly simple but
then
I'm a neophyte. I've just taken a few dot.net courses and have some
background in classic ASP.
The application is web-based. Basically one set of users fills out various
portions of a form, submits the data to another set of users in other
locations who then perform various actions (online and offline) and then
post
the item 'job completed' and send it back to the original user. The whole
thing must be HIPAA compliant since the data contains personal health
information. A logon mechanism for users is required.
I envisage a 'form' object with a 'state'. The state will determine what
stage in processing the form is and who can perform what actions on it.
Does anyone have any guidelines or advice we should follow to develop
this.
Thanks.

>
>
>

Microsoft has provided guidance documents. Do this search...

hippa site:microsoft.com

and...

hippa template site:microsoft.com

--
<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL http://clintongallagher.metromilwaukee.com/
MAP 43°2'17"N 88°2'37"W : 43°2'17"N 88°2'37"W

"mscertified" <rupert@tigerlily.comwrote in message
news:55D0B7ED-1778-4B97-B357-4226631D657F@microsoft.com...

Quote:

>I looked at those pages and they are pretty basic and low-level. What I'm
looking for right now is guidance on how to architect this application.
For
instance someone suggested we use a web service. So I'm looking for
direction
on how to plan the overall structure of this application rather than get
into
details about how to program individual pages or controls.
>
David
>
"John Timney (MVP)" wrote:
>

Quote:

>I think the first thing you should do is read the ASP.NET 2.0 quickstart.
>Its a very useful guide for inexperienced asp.net developers.
>>
>http://www.johntimney.com/home/redir...artv20/aspnet/
>>
>Specifically lookout for the wizard controls and login controls in
>relation
>to what you describe below.
>>
>Regards
>>
>John Timney (MVP)
>VISIT MY WEBSITE:
>http://www.johntimney.com
>>
>>
>"mscertified" <rupert@tigerlily.comwrote in message
>news:2E0CAD7D-7C40-4051-ABAC-C499916E65A0@microsoft.com...

Quote:

I'm about to start my first Dot Net Project. It seems fairly simple but
then
I'm a neophyte. I've just taken a few dot.net courses and have some
background in classic ASP.
The application is web-based. Basically one set of users fills out
various
portions of a form, submits the data to another set of users in other
locations who then perform various actions (online and offline) and
then
post
the item 'job completed' and send it back to the original user. The
whole
thing must be HIPAA compliant since the data contains personal health
information. A logon mechanism for users is required.
I envisage a 'form' object with a 'state'. The state will determine
what
stage in processing the form is and who can perform what actions on it.
Does anyone have any guidelines or advice we should follow to develop
this.
Thanks.
>

>>
>>
>>

Well a web service is not going to add anything unless you have a specific
remit to solve that involves using webservies, such as different or
geographically split clients wanting to make use of a common data layer. If
the asp.net quickstarts are too low level for you, and they dont cover
design really - have a fish around for some good tutorials on multi tiered
web developement. Here's one to get you started:

http://www.johntimney.com/home/redir...le.aspx?id=515

--
Regards

John Timney (MVP)
VISIT MY WEBSITE:
http://www.johntimney.com

"mscertified" <rupert@tigerlily.comwrote in message
news:55D0B7ED-1778-4B97-B357-4226631D657F@microsoft.com...

Quote:

>I looked at those pages and they are pretty basic and low-level. What I'm
looking for right now is guidance on how to architect this application.
For
instance someone suggested we use a web service. So I'm looking for
direction
on how to plan the overall structure of this application rather than get
into
details about how to program individual pages or controls.
>
David
>
"John Timney (MVP)" wrote:
>

Quote:

>I think the first thing you should do is read the ASP.NET 2.0 quickstart.
>Its a very useful guide for inexperienced asp.net developers.
>>
>http://www.johntimney.com/home/redir...artv20/aspnet/
>>
>Specifically lookout for the wizard controls and login controls in
>relation
>to what you describe below.
>>
>Regards
>>
>John Timney (MVP)
>VISIT MY WEBSITE:
>http://www.johntimney.com
>>
>>
>"mscertified" <rupert@tigerlily.comwrote in message
>news:2E0CAD7D-7C40-4051-ABAC-C499916E65A0@microsoft.com...

Quote:

I'm about to start my first Dot Net Project. It seems fairly simple but
then
I'm a neophyte. I've just taken a few dot.net courses and have some
background in classic ASP.
The application is web-based. Basically one set of users fills out
various
portions of a form, submits the data to another set of users in other
locations who then perform various actions (online and offline) and
then
post
the item 'job completed' and send it back to the original user. The
whole
thing must be HIPAA compliant since the data contains personal health
information. A logon mechanism for users is required.
I envisage a 'form' object with a 'state'. The state will determine
what
stage in processing the form is and who can perform what actions on it.
Does anyone have any guidelines or advice we should follow to develop
this.
Thanks.
>

>>
>>
>>

"mscertified" <rupert@tigerlily.comwrote in message
news:2E0CAD7D-7C40-4051-ABAC-C499916E65A0@microsoft.com...

Quote:

I'm about to start my first Dot Net Project. It seems fairly simple but
then
I'm a neophyte. I've just taken a few dot.net courses and have some
background in classic ASP.
The application is web-based. Basically one set of users fills out various
portions of a form, submits the data to another set of users in other
locations who then perform various actions (online and offline) and then
post
the item 'job completed' and send it back to the original user. The whole
thing must be HIPAA compliant since the data contains personal health
information. A logon mechanism for users is required.
I envisage a 'form' object with a 'state'. The state will determine what
stage in processing the form is and who can perform what actions on it.
Does anyone have any guidelines or advice we should follow to develop
this.

Can you explain the "offline" part of the application?

PS

This application is essentially replacing a paper form that is mailed back
and forth. One set of users fills out the form and then mails it to a
different set of users geographically separate in many different offices
state-wide. These users receive the form and act on it and then communicate
with the originator just to say 'its done'. The 'act on it' (which is what I
call offline) is not being webified only the rest of the process

David.

"PS" wrote:

Quote:

"mscertified" <rupert@tigerlily.comwrote in message
news:2E0CAD7D-7C40-4051-ABAC-C499916E65A0@microsoft.com...

Quote:

I'm about to start my first Dot Net Project. It seems fairly simple but
then
I'm a neophyte. I've just taken a few dot.net courses and have some
background in classic ASP.
The application is web-based. Basically one set of users fills out various
portions of a form, submits the data to another set of users in other
locations who then perform various actions (online and offline) and then
post
the item 'job completed' and send it back to the original user. The whole
thing must be HIPAA compliant since the data contains personal health
information. A logon mechanism for users is required.
I envisage a 'form' object with a 'state'. The state will determine what
stage in processing the form is and who can perform what actions on it.
Does anyone have any guidelines or advice we should follow to develop
this.

>
Can you explain the "offline" part of the application?
>
PS
>
>

My first DOT NET PROJECT - advice needed

re: My first DOT NET PROJECT - advice needed

re: My first DOT NET PROJECT - advice needed

re: My first DOT NET PROJECT - advice needed

re: My first DOT NET PROJECT - advice needed

re: My first DOT NET PROJECT - advice needed

re: My first DOT NET PROJECT - advice needed

Similar .NET Framework bytes

/bytes/development

/bytes/it

/bytes/about