Structuring Site/Solution

Hi All,
I work in a team of three developers. 99% of our work is developing
'applications' for our organisations Intranet - mainly whats become known to
us as e-employee apps, such as sickness/holiday reporting/authrisation,
handling the new starter/leaver processes, etc...the list goes on.
Up to recently, we have been developing in 'classic' ASP, storing all apps
in subdirectories of there own.
We are now starting to develop using VS.Net...We want to get this as right
as we can from the start, hence the following Q's...
- Should the 'site' be one project, or one solution? Or should each app be a
project, or even solution of its own?
- How do we share code? (Previously shared functions etc using include
files) Is this where the global assembly cache comes into play? I've not had
much luck finding documentation about this - I guess 'sharing' code becomes
a whole lot more important now, thinking in terms of building reusable
classes/functions...etc!
- We also need away of sharing chunks of HTML for headers etc...Are ASCX
files the right way to go for this?
I guess the questions arose when we started to discuss when to do builds,
when to deploy from development to live servers etc...We would need to do
this individually, for each application, as we tend to develop apps that
way - One developer will work on one project for X ws, and then test and
deploy.
Hope that makes sense! Look forward to any advice anyone may have.
Regards,
Simon.We used a single solution and a directory for each "module".
Developement is done using the isolated model (ie using IIS on the developer
machine). Once the source is checked in on the build server we have a batch
file that compiles the app as a DLL for each module. It allows to update
indivually each module (and we have also a common support DLLs for common
stuff).
Sharing is really easy. Use user controls for HTML fragments but you could
use just classes to share "pure" code...
Patrice
"Simon Harris" <too-much-spam@.makes-you-fat.com> a crit dans le message de
news:%23720RBwqEHA.1152@.TK2MSFTNGP11.phx.gbl...
> Hi All,
> I work in a team of three developers. 99% of our work is developing
> 'applications' for our organisations Intranet - mainly whats become known
to
> us as e-employee apps, such as sickness/holiday reporting/authrisation,
> handling the new starter/leaver processes, etc...the list goes on.
> Up to recently, we have been developing in 'classic' ASP, storing all apps
> in subdirectories of there own.
> We are now starting to develop using VS.Net...We want to get this as right
> as we can from the start, hence the following Q's...
> - Should the 'site' be one project, or one solution? Or should each app be
a
> project, or even solution of its own?
> - How do we share code? (Previously shared functions etc using include
> files) Is this where the global assembly cache comes into play? I've not
had
> much luck finding documentation about this - I guess 'sharing' code
becomes
> a whole lot more important now, thinking in terms of building reusable
> classes/functions...etc!
> - We also need away of sharing chunks of HTML for headers etc...Are ASCX
> files the right way to go for this?
> I guess the questions arose when we started to discuss when to do builds,
> when to deploy from development to live servers etc...We would need to do
> this individually, for each application, as we tend to develop apps that
> way - One developer will work on one project for X ws, and then test
and
> deploy.
> Hope that makes sense! Look forward to any advice anyone may have.
> Regards,
> Simon.
>
>

Structuring Site/Solution

Hi All,

I work in a team of three developers. 99% of our work is developing
'applications' for our organisations Intranet - mainly whats become known to
us as e-employee apps, such as sickness/holiday reporting/authrisation,
handling the new starter/leaver processes, etc...the list goes on.

Up to recently, we have been developing in 'classic' ASP, storing all apps
in subdirectories of there own.

We are now starting to develop using VS.Net...We want to get this as right
as we can from the start, hence the following Q's...

- Should the 'site' be one project, or one solution? Or should each app be a
project, or even solution of its own?
- How do we share code? (Previously shared functions etc using include
files) Is this where the global assembly cache comes into play? I've not had
much luck finding documentation about this - I guess 'sharing' code becomes
a whole lot more important now, thinking in terms of building reusable
classes/functions...etc!
- We also need away of sharing chunks of HTML for headers etc...Are ASCX
files the right way to go for this?

I guess the questions arose when we started to discuss when to do builds,
when to deploy from development to live servers etc...We would need to do
this individually, for each application, as we tend to develop apps that
way - One developer will work on one project for X weeks, and then test and
deploy.

Hope that makes sense! Look forward to any advice anyone may have.

Regards,
Simon.We used a single solution and a directory for each "module".

Developement is done using the isolated model (ie using IIS on the developer
machine). Once the source is checked in on the build server we have a batch
file that compiles the app as a DLL for each module. It allows to update
indivually each module (and we have also a common support DLLs for common
stuff).

Sharing is really easy. Use user controls for HTML fragments but you could
use just classes to share "pure" code...

Patrice

--

"Simon Harris" <too-much-spam@.makes-you-fat.com> a crit dans le message de
news:%23720RBwqEHA.1152@.TK2MSFTNGP11.phx.gbl...
> Hi All,
> I work in a team of three developers. 99% of our work is developing
> 'applications' for our organisations Intranet - mainly whats become known
to
> us as e-employee apps, such as sickness/holiday reporting/authrisation,
> handling the new starter/leaver processes, etc...the list goes on.
> Up to recently, we have been developing in 'classic' ASP, storing all apps
> in subdirectories of there own.
> We are now starting to develop using VS.Net...We want to get this as right
> as we can from the start, hence the following Q's...
> - Should the 'site' be one project, or one solution? Or should each app be
a
> project, or even solution of its own?
> - How do we share code? (Previously shared functions etc using include
> files) Is this where the global assembly cache comes into play? I've not
had
> much luck finding documentation about this - I guess 'sharing' code
becomes
> a whole lot more important now, thinking in terms of building reusable
> classes/functions...etc!
> - We also need away of sharing chunks of HTML for headers etc...Are ASCX
> files the right way to go for this?
> I guess the questions arose when we started to discuss when to do builds,
> when to deploy from development to live servers etc...We would need to do
> this individually, for each application, as we tend to develop apps that
> way - One developer will work on one project for X weeks, and then test
and
> deploy.
> Hope that makes sense! Look forward to any advice anyone may have.
> Regards,
> Simon.

Strucuture of an Asp.NET Intranet

Hi,

We have recently begun to upgrade our classic ASP intranet to ASP.NET.

We will be creating functional projects and different projects for
different departmental sites.

All the sites have common facets (user controls, custom controls) which
need to have available to all the projects we write and automatically
cascade to the other projects

(i.e. no rebuilding of dependent projects)

Can anyone suggest the best way of achieving this or a good source of
literature. Everything I have read so far has been a bit thin in this
area.

Many thanksthe easiest way to do this is the side by side model and a source control
system. put your shared controls in their own project. then add this project
to the solution file of each site. when you deploy a site, you will get a
copy of the shared code that was tested with the site. you can freely update
the shared code, because it will not break a running site, and a site that
needs a new feature in the shared code can ship right away, rather than
waiting for compliance testing of the change with the other sites.

-- bruce (sqlwork.com)

"Bob" <Arthur.Nyunt@.kellogg.com> wrote in message
news:1121184177.802972.227110@.o13g2000cwo.googlegr oups.com...
> Hi,
> We have recently begun to upgrade our classic ASP intranet to ASP.NET.
> We will be creating functional projects and different projects for
> different departmental sites.
> All the sites have common facets (user controls, custom controls) which
> need to have available to all the projects we write and automatically
> cascade to the other projects
> (i.e. no rebuilding of dependent projects)
> Can anyone suggest the best way of achieving this or a good source of
> literature. Everything I have read so far has been a bit thin in this
> area.
> Many thanks
Bruce,

Thanks for your reply.

I have created an empty project and created a user control, then tried
to add the project to solution file of a web application. I got a error
message saying that I was trying to access another application.

Could I just ask you

1) Is this because I need to run some source control program such as
source safe (as you mentioned source control)

2) Also could you clarify what is meant by a side by side model - I
have looked around and not found any references to this

Thanks

Arthur
i didn't read closely. usercontrols (ascx) don't share very well, as they
can not be in a seperate project (well they can but you have to fake out
vs). standard custom web controls (which i use) work fine.

to share usercontrols, it easy with a source control, because you jusrt add
a link to the shared source, and add the files to the current project.

-- bruce (sqlwork.com)

"Bob" <Arthur.Nyunt@.kellogg.com> wrote in message
news:1121187092.565144.76500@.z14g2000cwz.googlegro ups.com...
> Bruce,
> Thanks for your reply.
> I have created an empty project and created a user control, then tried
> to add the project to solution file of a web application. I got a error
> message saying that I was trying to access another application.
> Could I just ask you
> 1) Is this because I need to run some source control program such as
> source safe (as you mentioned source control)
> 2) Also could you clarify what is meant by a side by side model - I
> have looked around and not found any references to this
> Thanks
> Arthur