Changing Visual Studio workspace directories (HELP!)

[James Kimble]

I've inherited a program that was developed in Visual Studio and I'm
having a problem with build times. The program is about 250,000 lines
and I'm storing the entire project on a network drive. We've got
gigabyte ethernet and it's a high speed raid array but it still takes
about 5
minutes to do the smallest recompile and about 1 hour and 15 minutes
to do a full rebuild (pretty annoying).

I'd like to move the object and binary files to my local drive in the
hopes of speeding things up. The problem is, I don't have any idea how
you change the workspace to make that happen. Can anyone tell me where
in Visual Studio (ver 6.0) you can change the workspace directories
around? Or do I have to create a new project and configure it at that
time?

Thanks for any help,

James Kimble

[J French]

On 9 Dec 2003 06:22:35 -0800, jk*****@one.net (James Kimble) wrote:

I've inherited a program that was developed in Visual Studio and I'm
having a problem with build times. The program is about 250,000 lines
and I'm storing the entire project on a network drive. We've got
gigabyte ethernet and it's a high speed raid array but it still takes
about 5
minutes to do the smallest recompile and about 1 hour and 15 minutes
to do a full rebuild (pretty annoying).

I'd like to move the object and binary files to my local drive in the
hopes of speeding things up. The problem is, I don't have any idea how
you change the workspace to make that happen. Can anyone tell me where
in Visual Studio (ver 6.0) you can change the workspace directories
around? Or do I have to create a new project and configure it at that
time?

Have a good look inside your Project's .VBP file
- all will become obvious

I once wrote a 'Noddy' for moving them
- but it is too primitive (and dependent) to post

[Steve Gerrard]

"J French" <er*****@nowhere.com> wrote in message
news:3f***************@news.btclick.com...

On 9 Dec 2003 06:22:35 -0800, jk*****@one.net (James Kimble) wrote:

I once wrote a 'Noddy' for moving them
- but it is too primitive (and dependent) to post

Do tell, what is a Noddy?

[Steve Gerrard]

"James Kimble" <jk*****@one.net> wrote in message
news:ed**************************@posting.google.c om...

I've inherited a program that was developed in Visual Studio and I'm
having a problem with build times. The program is about 250,000 lines
and I'm storing the entire project on a network drive. We've got
gigabyte ethernet and it's a high speed raid array but it still takes
about 5
minutes to do the smallest recompile and about 1 hour and 15 minutes
to do a full rebuild (pretty annoying).

I'd like to move the object and binary files to my local drive in the
hopes of speeding things up. The problem is, I don't have any idea how
you change the workspace to make that happen. Can anyone tell me where
in Visual Studio (ver 6.0) you can change the workspace directories
around? Or do I have to create a new project and configure it at that
time?

Thanks for any help,

James Kimble

Is that a VB program (doesn't sound like it)?

If so, and if all the forms, modules, classes, etc. are stored in a
single folder, along with the .vbp file, the .vbp file will have stored
only the file names, not the paths. You would then be able to get a copy
put on your C: drive to work without much trouble at all.

[J French]

On Tue, 9 Dec 2003 20:48:10 -0800, "Steve Gerrard"
<no*************@comcast.net> wrote:

"J French" <er*****@nowhere.com> wrote in message
news:3f***************@news.btclick.com...

On 9 Dec 2003 06:22:35 -0800, jk*****@one.net (James Kimble) wrote:

I once wrote a 'Noddy' for moving them
- but it is too primitive (and dependent) to post

Do tell, what is a Noddy?

A trivial little App
- 'trivial' being the operative word

[J French]

On Tue, 9 Dec 2003 20:55:18 -0800, "Steve Gerrard"
<no*************@comcast.net> wrote:
<snip>

Is that a VB program (doesn't sound like it)?

If so, and if all the forms, modules, classes, etc. are stored in a
single folder, along with the .vbp file, the .vbp file will have stored
only the file names, not the paths. You would then be able to get a copy
put on your C: drive to work without much trouble at all.

Careful ...

It stores relative paths in the .VBP