M
MC
Hi all,
I've read the various posts concerning file access on mapped drives--I
think problem is different:
The problem: Open a VB Winforms project from a mapped drive and all
files open fine except form files. Their code opens fine but trying
to open them in the form designer I get (for instance)
"The item 'MainForm.vb' does not exist in the project directory. It
may have been moved, renamed, or deleted."
However, if I open the same project without using the mapped drive to
access it, everything opens fine. I've already set the Intranet
security level for .NET to Full and I've done
caspol -security off
Until recently, I was successfully using Windows 2000, SP4, VS.NET
2003, Framework 1.1, and I was able to open projects located on a
mapped drive. I open projects very frequently and they are located on
a local drive, but *deep* in the directory tree, so I like to map them
to a drive letter. Recently, I went to a new machine, using XP Pro
SP2, VS.NET 2003, Framework 1.1, and I think opening projects on
mapped drives was working fine until I teaked something (I've been
trying to figure out what for a time now). I did a VS.NET repair, to
no avail.
I'd like to avoid reinstalling VS.NET, so I'm hoping to first get some
suggestions here.
Thanks!
Craig
I've read the various posts concerning file access on mapped drives--I
think problem is different:
The problem: Open a VB Winforms project from a mapped drive and all
files open fine except form files. Their code opens fine but trying
to open them in the form designer I get (for instance)
"The item 'MainForm.vb' does not exist in the project directory. It
may have been moved, renamed, or deleted."
However, if I open the same project without using the mapped drive to
access it, everything opens fine. I've already set the Intranet
security level for .NET to Full and I've done
caspol -security off
Until recently, I was successfully using Windows 2000, SP4, VS.NET
2003, Framework 1.1, and I was able to open projects located on a
mapped drive. I open projects very frequently and they are located on
a local drive, but *deep* in the directory tree, so I like to map them
to a drive letter. Recently, I went to a new machine, using XP Pro
SP2, VS.NET 2003, Framework 1.1, and I think opening projects on
mapped drives was working fine until I teaked something (I've been
trying to figure out what for a time now). I did a VS.NET repair, to
no avail.
I'd like to avoid reinstalling VS.NET, so I'm hoping to first get some
suggestions here.
Thanks!
Craig