Using asp.net website and its associated class library through visual source safe.
-
Hi, we have a team of 5 to 7 programmers working on a single asp.net project. And we are using visual source safe for team management here. We have one asp.net website and one associated class library whose dll is added as a reference in the website. The problem is when i want to debug i can debug pages from website very easily but when i come a point where i m accessing some routine through object of a class library it does not allow me to debug into that class of class library although i have added its dll as a reference in the website. Second thing is when i make any change in any of the classes of class library it does not allow me to update or re-build the dll again through source safe. Does anyone have any suggestions on it? am i missing something here or going wrong somewhere ? Pls answer as this is the first time we are implementing source safe and that too for a very critical project.
-
Hi, we have a team of 5 to 7 programmers working on a single asp.net project. And we are using visual source safe for team management here. We have one asp.net website and one associated class library whose dll is added as a reference in the website. The problem is when i want to debug i can debug pages from website very easily but when i come a point where i m accessing some routine through object of a class library it does not allow me to debug into that class of class library although i have added its dll as a reference in the website. Second thing is when i make any change in any of the classes of class library it does not allow me to update or re-build the dll again through source safe. Does anyone have any suggestions on it? am i missing something here or going wrong somewhere ? Pls answer as this is the first time we are implementing source safe and that too for a very critical project.
Hi Dont add dll to source safe only add classes on source safe and let others to take latest version at their end and than build at their end. We also went through same problem
-
Hi Dont add dll to source safe only add classes on source safe and let others to take latest version at their end and than build at their end. We also went through same problem