J
J.Marsch
Hello all:
I am trying to create a multi-project solution in VS 2005, and I'm having
some problems with Source Control. I am running into 2 very vexing
problems. Can anyone give me a pointer?
Some layout information:
I have one Web Site, and several class library projects in the solution (all
C#).
The web site is configured to use local IIS via an HTTP location
http://localhost/MyWebSite
1. If I create the solution and check everything in, it seems to work fine
for me. However, if another developer tries to perform an "Open from source
control" to pull the code onto their machine, the web site files land in a
directory that the IIS account has no access to, so when you attempt to run
the site in the debugger, you get an exception. It seems that by default
all web sites that are opened from source control start out broken. This
worked perfectly in Visual Studio 2003 (web projects went below
inetpub\wwwroot), but with 2005, the aspx filesend up below my default
project folder.
2. I have project references from the Web Site to the class libraries.
When the Class Libraries build, the dlls are copied into the bin directory
under the web site. That part is ok -- same behavior as in 2003, but more
obvious. However, the IDE wants to automatically add these dlls (the
binaries) to source control. That's really _not_ ok. How can I configure
the IDE to use the project references without trying to check in the dlls?
(basically, similar behavior as '2003)
I am trying to create a multi-project solution in VS 2005, and I'm having
some problems with Source Control. I am running into 2 very vexing
problems. Can anyone give me a pointer?
Some layout information:
I have one Web Site, and several class library projects in the solution (all
C#).
The web site is configured to use local IIS via an HTTP location
http://localhost/MyWebSite
1. If I create the solution and check everything in, it seems to work fine
for me. However, if another developer tries to perform an "Open from source
control" to pull the code onto their machine, the web site files land in a
directory that the IIS account has no access to, so when you attempt to run
the site in the debugger, you get an exception. It seems that by default
all web sites that are opened from source control start out broken. This
worked perfectly in Visual Studio 2003 (web projects went below
inetpub\wwwroot), but with 2005, the aspx filesend up below my default
project folder.
2. I have project references from the Web Site to the class libraries.
When the Class Libraries build, the dlls are copied into the bin directory
under the web site. That part is ok -- same behavior as in 2003, but more
obvious. However, the IDE wants to automatically add these dlls (the
binaries) to source control. That's really _not_ ok. How can I configure
the IDE to use the project references without trying to check in the dlls?
(basically, similar behavior as '2003)