Strucuture of an Asp.NET Intranet

[Bob]

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 Barker]

the 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]

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

 

[Bruce Barker]

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)