Hi there,

We have run into a problem where two programmers want to work on the same
project (different forms) at the same time from a network share.

First Programmer opens the project and all is fine,

Second Programmer opens the project and is ground to a halt, clicking on
things in visual studio takes about 5 seconds per click and it is not
practical,

Does anyone know of a way this can be achieved, due to the fact that there
is only two of us and we sit side by side we can visually make sure we are
not editing the same form, are there some settings we need to enable /
disable?

We are both using Visual Studio 2005 SP1

Regards

Simon Anderson
Software Developer
Newline Computing

Google for "Source Control" and IMHO "Subversion"

Sourcecontrol allows you to get copies of the code which you edit locally
You can then Check these changes into a central repository where they are
merged with said repository.

This typically allows you to make mistakes and resolve them locally without
getting in the way of the other developers on your team.

--
Rory

[quoted text, click to view]

Please do not crosspost .NET questions to non-.NET groups. The *.vb.* groups
are for VB6 and earlier.

[quoted text, click to view]

Then.... you'll want to remove "vb.general.discussion" from your crosspost
list. All groups on the ms server that start with "microsoft.public.vb" are
here to support pre-dotNet versions of VB.

--
Ken Halter - MS-MVP-VB - Please keep all discussions in the groups..
In Loving Memory - http://www.vbsight.com/Remembrance.htm

[quoted text, click to view]

Does that then mean that microsoft.public.vstudio.general is for Visual
Studio 6 and earlier, with microsoft.public.vsnet.general is for .Net
versions? I ask this because both groups seem to only contain .Net
discussions.

[quoted text, click to view]

IMHO that was likely the intent.

Visual Studio 6 and earlier was a collection of language products, each with
their own IDEs and libraries, and so there were few areas of common
interest. It was usually more expedient to post to a newsgroup dedicated to
a specific product - VB, VC, VisualJ++, ... As a result "vstudio.general"
was never that popular. Especially with VB programmers. Frequented, if at
all, by mostly VC programmers.

With Visual Studio .Net there is a common IDE and a common library and
therefore a great deal of common ground. "vstudio.general" became the
logical place to ask IDE questions separate from language issues.
"vstudio.general" is readily identifiable while "vsnet.general" is more
obscure.

There is also a .dotnet.general newsgroup that essentially covers the same
topics as vstudio.general and vsnet.general.

-ralph