I dont believe that VS2003 compiles its projects into a single DLL.
I think you'd be able to create a VS solution with containing several
WebSite projects and Class library projects and each class library will
compile into a single dll that can be referenced by the other projects.
Each WebSite projects with ASP.NET generally result with the the source
code being placed on the web site and ASP.NET compiling it up on the fly as
the page is hit for the first time.
I'd recommend that you investigate VS's Visual Source Safe - this is a
source code and control system (check out
http://www.learnvisualstudio.net/videos/Visual_Source_Safe_Series.htm)
I hope this of some help and wish you the best of luck with you project.
Mike
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm --------------------
|
| Can someone please refer me to books, articles, websites where I can
obtain
| information on how to set up VS2003 for team development.
|
| I am a project manager for a non-trivial military software project that
is
| migrating from ASP to ASP.NET. I have a team of 9 developers using
VS2003.
|
| Of concern to me is that VS2003 compiles its projects into a single DLL.
| This will not work for our environment as our architecture is SOA based
and
| as such the application consists of multiple DLLs.
|
| Additionally, there needs to be the ability for different developers to
work
| on different files and once done, be able to send the file for testing
and
| promotion to production.
|
| I am looking for resources providing in depth knowledge on the
capabilities
| of team based enterprise development using VS2003 enterprise.
|
| Thanks
|
