team dev

  • Thread starter Thread starter Tom Gao
  • Start date Start date
T

Tom Gao

hi guys

currently I am working with another developer doing c# but the problem is
when he is debugging I can not run the code or debug as a result we have to
constantly wait on each other.. thus reducing productivity

is there another solution to this ?

Thanks
Tom
 
Hello Tom,

This is a matter of how you architect your software. For example, if you
were developing a Windows Form application and all the business logic is
within the form, you'd very much likely to have the problem you are having
right now. Separation of business logic and UI logic will enable you to have
separate files, which means multiple developers can work on different files.
 
Hi scott

yes ASP.NET the issue is developer A starts debugging on the project then
the rest of us can not compile or debug. Or when he has an error the rest of
us can not compile either

Thanks
Tom
 
Have you thought about all developing on a local virtual directory on your own machines and using a source control system to make sure you don't override eachother's changes?

Regards

Richard Blewett - DevelopMentor
http://www.dotnetconsult.co.uk/weblog
http://www.dotnetconsult.co.uk

Hi scott

yes ASP.NET the issue is developer A starts debugging on the project then
the rest of us can not compile or debug. Or when he has an error the rest of
us can not compile either

Thanks
Tom
 
if you don't understand then why answer ?

does source safe allow you 3 developers to debug applications at the same
time ? I don't think so...
 
Tom Gao said:
if you don't understand then why answer ?

does source safe allow you 3 developers to debug applications at the same
time ? I don't think so...
Click to expand...

You're not being very clear in what you mean. SourceSafe does indeed
allow 3 developers to be developing and each debug the application on
their own box at the same time.

I suspect you mean something different by "debug applications at the
same time" but it's not very clear. Being sarcastic at those who are
trying to help you usually isn't a particularly good way of getting
more help, by the way.
 
Yes, Source Safe is a tool that gives you the ability to have multiple
people working on the same project. This is accomplished by allowing each of
the developers to have a local copy of the whole project in their own
machines, in other words, it would be like if you were the only developer
working on the project locally in your computer.

Since multiple developers make changes to the files, source safe keeps track
of all these changes for you. So one developer can "Check Out" a certain
file form source safe and modify it, once the modifications are completed,
the developer would "Check In" the file so that other developers can "Get
Latest Version" of the file so that everybody's computer has the newest
code.

Like Rechard Blewtt told you, instead of working from a server you will have
to make some modification so that you host IIS in your local computer. Also,
like Jon Skeet told you, don't be so quick to say what on your mind, I know
these things can be frustrating and some time we say thing we did not mean
to so I have no problem letting this one go.

Source safe is nice but you still have to do some research to figure out how
the software works, further more, Microsoft source safe des not work
seamlessly with .Net, there are some things that may annoy you. (Like if you
ever need to rename a file).

You don't have to use Microsoft Source Safe, there are other source controls
tools other that will allow you to do essentially the same thing.
 
rene, you're right :) sorry about that.. I was frustrated and angry that the
project was going so slowly.

Sorry again
 
Back
Top