How to Split a Web Project to serveral Projects

Question

0.00/5 (No votes)

See more:

I have a Web site which was developed by one developer.
Now the compony hired some other developers,each developer is responsile for each part. BTW I dont want each developer to have access to all the project files and can work independent, but they can have others complied files(dll files).
And the admin can gather the DLLs and compile them as one project the same before.

For example there are some directoies like :
A-Directory
B-Directory
C-Directory
D-Directory

in each directory there are some URLs which can call other directories.

Thanks in advance.

Posted 5-Feb-11 20:45pm

Jamal Seyedi

Updated 6-Feb-11 4:02am

v2

Add a Solution

3 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Keith Barrow · Answer 1 · 2011-02-05T21:00:00

This sounds like a recipie for disaster to me: each dev will work in their own silo, changes in one dll can impact another without warning, this will be made worse by the dev being unaware of the potential impact of their changes. Finally, at each new build you will have to re-distribute the new dlls to each team using them. It will be very hard to manage.

You can use source control to acheive what you want. It is a good idea anyway, even without your requirents as it keeps track of changes, most allow you to roll-back code if needed and provide other support as well, I've used Visual Studio Team System (very good), Visual Source Safe (not good) and Merant Version Manager a while back. There are also Open-Source source control, but the only ones I know make the source-code publically available.

Once you have source control you can create a repository for each team, when they check in, build their dlls and redistibute to the other teams repositories.

Espen Harlinn · Answer 2 · 2011-02-06T03:32:00

Solution 3

Sounds like you don't trust your developers - if that's the case, hire somebody you can trust, even if it will cost you four or five times as much on an hourly basis.

Good people thrive in a trusting and supporting environment - good developers are usually far more productive, and will save you both money and grief, even if they initially seem to cost far more.

Apart from that I think you should seriously consider Keith Barrows answer :)

Regards
Espen Harlinn

Posted 6-Feb-11 3:32am

Espen Harlinn

Comments

Jamal Seyedi 6-Feb-11 9:56am

i am sure you are kidding.
the problem is not about not trusting developers.
the first problem the site is growing and huge.
and as i mentioned i want every developer cosider on own part.
and whenever the site is needed a versin we could publish a version which is just related to that part.

Espen Harlinn 6-Feb-11 10:14am

"I dont want each developer to have access to all the project files " - seemed to indicate something in that direction. and as I wrote "if that's the case" - I tried to indicate that the rest only had relevancy limited to that scenario.

Now, since this obvoiusly, and happily, is not the case, I advice you to use a revision contol system, as Keith Barrows suggested.

You may want to set up a test and development site too, helping to ensure that anything that is put into production works smoothly.

Good luck

Jamal Seyedi 6-Feb-11 10:18am

Thanks for answering and mentioning.
"I dont want each developer to have access to all the project files " it is for biggners.
BTW thanks a lot for your time.

Keith Barrow 6-Feb-11 10:27am

Also a good answer, I wouldn't advocate splitting the website down in the first place, just allocating responsibilities should be enough.

Abhinav S · Answer 3 · 2011-02-05T21:05:00

Solution 2

A design approach like the Composite UI Block may help you out. See here[^].

Posted 5-Feb-11 21:05pm

Abhinav S