Re: VS2005 crashing when trying to Build a solution stored on a network drive

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

In your case, it may be that your home directory (My Documents) was NOT
mapped to the H: drive at the time you installed VS (?), in this case,
VS2005 will have seen your local hard drive as the home directory.

My Documents is not mapped to my H: drive, I'm not sure where you got the
impression that it was. However, my H: drive was mapped at the time I
installed VS 2005. My H: drive has been mapped for the 2+ years I've been
working here.

I'm still not sure how that has anything to do with it though. I'm
transferring entire Project folders including all supporting files. Why is
it I can transfer these Project folders to any local drive/folder and they
work correctly if it has something to do with relative paths? I can
transfer them from C:\...\...\My Documents to C:\MyVSProjects to
F:\Data\VS2005 (providing F: is a local drive) and no matter where I
transfer these folders my projects always compile and work correctly. But
once I put the project folder on a network drive, be that H:\ or
\\myserver\VSProjects or \\myOtherServer\VSProjects, or G:\share\, it fails
to work once I make any modifications (be aware it works as long as I don't
make any modifications to any part of the project).

As a general rule, instead of "copying", you just create a project at the
new CORRECTLY CONFIGURED location, then import all your code into the new
project, then build, and it should work.

I get the same error even if I start a project from scratch at ANY network
location.

Ryan

"Gerry Hickman" <gerry666uk@xxxxxxxxxxx> wrote in message
news:evAH9oKlGHA.896@xxxxxxxxxxxxxxxxxxxxxxx
Hi Ryan,

I don't think it can be a bug, because hundreds of people would be posting
about it and my own developers would be complaining every five minutes
that it was crashing.

I notice you said you "copied" some files to the network drive? This could
be a cause of the problem. The way it usually works in VS2003/VS2005 is
that when you install it and run for the first time, it will map itself
into your home directory. On a big network, this will be a drive mapped to
a share corresponding to your sAMAccountName residing on the DATA
partition of the file server.

After that, each time you create new solutions, projects and WebSites,
they will be correctly added into this structure below it's root. Relative
paths (e.g. in the VSPROJ files) will therefore be correct and everything
will work.

In your case, it may be that your home directory (My Documents) was NOT
mapped to the H: drive at the time you installed VS (?), in this case,
VS2005 will have seen your local hard drive as the home directory.

There's no rule that says you can just copy solutions, projects and
WebSites to a new location and expect them to work, although there are
procedures you can follow to "publish" or "deploy" to a new location.

On my own network, it was set up to work from the network drive from the
very moment it was installed, but on your's who knows?

It looks like you can alter the locations for solutions, projects and
WebSites by using Tools:Options:Projects and Solutions, and you may be
able to reset it to point to a network drive, but I don't know - it might
break existing projects.

As a general rule, instead of "copying", you just create a project at the
new CORRECTLY CONFIGURED location, then import all your code into the new
project, then build, and it should work.

Ryan wrote:
Kevin,

Just for some more info.. if I copy the entire folder directly to the
nextwork drive and then build (F5), it will work fine. It's once I make
changes to any of those files (say I change some properties on one of my
forms), then try to build (after saving all files), that is when I get
the error.

Thanks for the contact info.

Ryan

"Kevin Yu [MSFT]" <v-kevy@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:q7HhscBlGHA.764@xxxxxxxxxxxxxxxxxxxxxxxx
Hi Ryan,

I tried it on my machine, but seems that I cannot reproduce it. For
further
troubleshooting on this issue, I suggest you try to contact Microsoft
PSS.
If this is a bug you can also report through them and they might work
out a
hotfix for you.

Please visit the following link for contact information of your local
PSS.

http://support.microsoft.com/common/international.aspx?rdpath=gp;en-us;offer
prophone

Kevin Yu
Microsoft Online Community Support

============================================================================
==========================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
============================================================================
==========================

(This posting is provided "AS IS", with no warranties, and confers no
rights.)





--
Gerry Hickman (London UK)


.

Relevant Pages

  • Re: download ubuntu8.04 iso
    ... well you cant really download the *.iso file from synaptic..you will ... ownership of your home directory. ... I recently downloaded updates for my Archlinux install, ... going to be upgraded to KDE4. ...
    (Ubuntu)
  • Re: What I do for a new machine?
    ... On Sat, Dec 3, 2011 at 7:42 AM, Avi Greenbury wrote: ... you really have plans to install 10GB worth of stuff in /opt? ... /home and the / are the partitions. ... I also store my backup of my home directory there ...
    (Ubuntu)
  • Re: How to determine the file type of a file passed as an input to the perl program ?
    ... keep using few CPAN modules from my home directory like PerlTidy etc. ... However the reason for which I want to use an inbuilt module because I ... into how to do an install in your home directory. ... I have already installed some Perl modules in my home directory using the ...
    (perl.beginners)
  • Re: VS2005 crashing when trying to Build a solution stored on a network drive
    ... That's what I'm saying, it was NOT mapped to your home directory. ... OK, in that case I agree, it doesn't look like it's related to the home directory mapping not being in place at install time. ... You have to wonder about the competency of your network Admin team though? ... Did they set up auditing of file access and file locking on both client and server and watch it carefully as you bit "build"? ...
    (microsoft.public.vsnet.general)