Multiple projects, one web application

  • Thread starter Thread starter David Hodges
  • Start date Start date
D

David Hodges

Here's what I want to do:
I want to divide my huge asp.net application into about 5 separate
projects, so that a different developer can work on each. My vision is
that the "bin" folder will contain a dll from each project and that
updates to one project won't require rebuilding the others. Users of
the site will see it as a whole.

The only way Visual Studio 2003 will let me add a project to a web
solution is by creating a subfolder for the new project. But when I
compile, it puts the dll in a bin folder in that subfolder, not on the
root. But when I go to retrieve the web page, it looks for the dll in
the root and gives an error.

And anyway, I'd rather not have subfolders at all
Is this going to be possible or is it a wild goose chase?

Thanks,
David
 
David Hodges said:
Here's what I want to do:
I want to divide my huge asp.net application into about 5 separate
projects, so that a different developer can work on each. My vision is
that the "bin" folder will contain a dll from each project and that
updates to one project won't require rebuilding the others. Users of
the site will see it as a whole.

The only way Visual Studio 2003 will let me add a project to a web
solution is by creating a subfolder for the new project. But when I
compile, it puts the dll in a bin folder in that subfolder, not on the
root. But when I go to retrieve the web page, it looks for the dll in
the root and gives an error.

And anyway, I'd rather not have subfolders at all
Is this going to be possible or is it a wild goose chase?
Click to expand...

You are just starting a new application, and you're already looking for
ways to work around VS.NET. Think about that for a moment.

Ok, now, can you split your application such that one developer each can
work on http://localhost/site/one/, http://localhost/site/two/, etc? You
would also have a project for http://localhost/site/. There would be
multiple dlls, but you probably don't really care about dlls, but rather web
sites.
 
No, I didn't just start the new application. It was started nearly two
years ago and has grown and grown to the point where we want to
subdivide it to make development more manageable.

And you are right, I don't care about multtiple dll's.

I know I can achieve the result with multiple folders. But that seems
like more of a limitation of the vs.net sets up projects than of the
underlying architecture of .net.
 
David Hodges said:
No, I didn't just start the new application. It was started nearly two
years ago and has grown and grown to the point where we want to
subdivide it to make development more manageable.

And you are right, I don't care about multtiple dll's.

I know I can achieve the result with multiple folders. But that seems
like more of a limitation of the vs.net sets up projects than of the
underlying architecture of .net.
Click to expand...

It's certainly a limitation, but I haven't found it to be much of a burden.
 
Back
Top