Compile fails on network drive

Hot Topic

Absolute Value
installation problems... can't install Visual Studio Express
How to Set ListViewItem Height?
'NullReferenceException' with blank picture boxes
"File 'c:\...XXX.resx' already exists in the project"
getting vb and sql 'express' editions to work..together...
Uninstalling Pre-RTM Visual Studio Express builds (CTPs or Betas)
Registration
Dataset Question
sendkeys and focus

VS Express Editions

Visual C# Keeps asking for Registration
How do I select multiple items in a list box
Stupidest error message ever
Exception during open Form
Call <STRING AS COMMAND>
UserDeletingRow in Datagridview
Platform SDK??
Nplot.dll - Free .NET chart plotter component - How to implement?
Installation of VB
newbie auto installer project

Compile fails on network drive

I installed VCX (VC++ Express) on my local drive, but my project files are on a network drive mounted as S:  I created a simple HelloWorld Win32 Console App and the compile fails due to:

1>cl : Command line error D8022 : cannot open 's:\project\TestExpress\TestExpress\Debug\RSP0000024283524.rsp'

However, it works fine on a local drive.  I read about this problem with other products but I can no longer find the reference.

Anyone know how to fix this

Thanks

Answer this question

Compile fails on network drive

  • Chackowsky

    Please don't rush in making assumptions about explicitly ignoring your question because I can assure you 100% that this is not the case. If you look carefully at the forums, you will see that there are a lot harder questions being answered by the VC team. Members of the VC++ can never answer every single question by themselves. We depend on the community as well including yourself and similar folks to contribute their valuable experience in solving each other's problems.

    Nevertheless, I understand your frustration and I have sent an email to the person owning this forum concerning your post.

    Thanks in advance for your patience! We really appreciate you using such forums and contributing to the success of VC2005.

    Thanks,
      Ayman Shoukry
      Program Manager
      VC++ Team

  • Josh Christie

    Please e-mail the entire file to me at:
       donbrinn (at) microsoft (dot) com

    Thanks for your help in tracking down this problem.  I will look into the log file in more detail tomorrow (Thursday).

    Thanks,
    Don Brinn

  • SammyF

    What, no one has done this before   Doesn't Microsoft read these forums   This is such a "grasshopper" thing for them to break!  They should have, or know of, a fix for this.

  • Rob Washo

    Unfortunately, we are unable to reproduce this problem. Using VC++ Express to build a project from a mapped network drive on a Win2K machine is successful under our tests.

    I would appreciate any help you can give in reproducing this problem.

    First, I recommend checking the permissions of the network drive to ensure your account has sufficient privileges that are required to conduct a build.  Also, ensure that any anti-virus or similar applications that may be detecting the creation of the temporary response files are not interfering with the build (by exclusively locking the files so that they can't be read or deleted).

    If you still have this problem after making these checks, you can use the filemon tool, available free form Sysinternal's web site: http://www.sysinternals.com/FileAndDiskUtilities.html  By running this tool on the remote machine, where the project files are stored, you should be able to see exactly when and how the .rsp file is accessed.  If you could send us this information, it would be very helpful in tracking down this problem.

    Thank you,

    Don Brinn

  • Ashwin Purohit

    I have emailed the entire log file.

    Thanks.

  • Matt Walter

    Thank you for your responses.  I appreciate them, especially the one from the VC++ Team Member.

    Martin, I did indeed find that post referred to by your last link.  Note that I had responded (several days ago) to that post too.  Microsoft stated that they may have fixed the problem in the Beta, and I stated that since I assumed the Express Edition was based on the Beta, that they had indeed NOT fixed the problem.  It's interesting to note that I got no response to that either, but I'm still watching.

    My network arrangement has Express Edition installed on my WinXP-Pro client machine where I do all of my work, and my project files (which are the really important "Thou shalt not lose!" files) are housed on my Win2000-Pro (not Server) machine because it has the RAID redundancy protection.  Both machines have all the latest updates applied.  This works fine for all other development tools.

    There was a similar problem and solution with the Windows Driver Foundation Beta package back in late July, but now I can't find the solution reference for the life of me.  I think it involved removing one of the Windows Hotfixes on my XP machine, which was safe for me to do because my client is not exposed to the WAN.  The solution worked, but I believe I've probably reapplied the update since then, as I haven't referenced the WDF package lately.  However, I don't know if this Express problem is the same issue.

    Still looking for the solution.

  • Kevinbe

    We used to just have a general VCExpress forums and we just recently switched to having a VC++ specific express forum and hence that caused some confusion.

    Glad Tarek is already on the issue.

    Thanks,
      Ayman Shoukry
      VC++ Team

  • buragohain

    I am still using 2005 Beta 2 on my laptop (didn't had time to reinstall the final version). And I share all my demo projects with my desktop over a network drive.
    Compiling from my desktop with 2003 and from the laptop with 2005.

    I have no problems at all. But I found that different people had and the problem is not reproducible:
    http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx feedbackid=d5af2fc6-af32-4826-bfcb-86ed0591ed0d
    http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=147563&SiteID=1


  • Rick Strahl

    From your log, it looks like for some reason the CL.exe process doesn't have permission to access the file on the remote machine, but the VCExpress process does.

    One possibility is that this is because CL.exe was spawned by the other process, and the security settings on your XP machine and/or Win2K machine are setup to limit the permissions of processes spawned by other processes.  To get more information to test this theory, could you please do the following:

    Create two batch files:
    C:\mytest.bat:
       cmd /c "c:\mytest2.bat"
      exit 0
    C:\mytest2.bat:
        type foo.txt > bar.txt
        exit 0

    In your project, add a pre-build event.  (You can do this by opening the Project Properties page, and looking on the Configuration Properties --> Build Events --> Pre-Build Events pane.)
       dir > foo.txt
      cmd /c "c:\mytest.bat"

    Then please rebuild your project while FileMon monitors.  The FileMon log from this, allowing us to see the errors (if any) that these batch files encounter while trying to access files on the remote drive, should be helpful.

    Thanks.



  • dnenadd

    I am truly humbled by your responses, and I have completely retracted (deleted) my previous negative post.  Microsoft has definitely earned some cudos here.  On to business...

    Don:  You said you could not reproduce the problem, but I want to be clear and concise: I'm executing Express on an XP-Pro machine but the mounted network drive is located on a Win2K-Pro machine.  Both machines are fully updated as per the online Microsoft Update utility.  I think that's significant.  You did not indicate that you duplicated that specific environment.

    I am the sole developer, therefore I have full control of all priviledges, and everything else for that matter.  I am at Admin privilege level since there are no other users on my LAN.  I think you can rest assured that the privileges, anti-virus settings, etc., are all configured correctly to the best of my double-checked knowledge.  I think those items are a red herring in this case.

    Visual C++ 6.0 Pro builds my projects just fine with the same arrangement.
    Dreamweaver builds my web pages just fine with the same arrangement.
    Paint Shop Pro edits my images just fine with the same arrangement.

    I will try the filemon tool that you referred to.  I've never used it before (never needed it before) so I'll have to get back to you with that info.

    April:  Sorry but I disagree with your narrow interpretation of what is and is not supported by VS products.  "Support" in your context, refers to "by design" and I think you are just plain wrong.  I truly doubt that Microsoft "designed out" network-drive access fundamentals from their product-line.  There is no technical reason why it should not work as we have been discussing, other than due to a bug.

    Tarek:  You are correct in that I am a single user.  File-access times are not an issue as they are always set by the same machine.  Again please note that ONLY the project files are on the network drive

    The following is a link to another user with the exact same problem:
    http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=147563&SiteID=1

    Were you able to locate the Windows Driver Foundation item that I referenced in my last post   It involved removing one of the HotFixes.

    Anyways, here's the text from my Express output window:

    1>------ Build started: Project: TestExpress, Configuration: Debug Win32 ------

    1>Compiling...

    1>cl : Command line error D8022 : cannot open 's:\project\TestExpress\TestExpress\Debug\RSP00000215921192.rsp'

    1>Build log was saved at "file://s:\project\TestExpress\TestExpress\Debug\BuildLog.htm"

    1>TestExpress - 1 error(s), 0 warning(s)

    ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

    I looked in the referenced directory and there is no .rsp file.  Below is the content of the resulting BuildLog.htm file:
    Build Log
        
    Build started: Project: TestExpress, Configuration: Debug|Win32
    Command Lines
        
    Creating temporary file "s:\project\TestExpress\TestExpress\Debug\RSP00000115921192.rsp" with contents [ /Od /D "WIN32" /D "_DEBUG" /D "_CONSOLE" /D "_UNICODE" /D "UNICODE" /Gm /EHsc /RTC1 /MDd /Yu"stdafx.h" /Fp"Debug\TestExpress.pch" /Fo"Debug\\" /Fd"Debug\vc80.pdb" /W3 /c /Wp64 /ZI /TP .\TestExpress.cpp ] Creating command line "cl.exe @s:\project\TestExpress\TestExpress\Debug\RSP00000115921192.rsp /nologo /errorReport:prompt" Creating temporary file "s:\project\TestExpress\TestExpress\Debug\RSP00000215921192.rsp" with contents [ /Od /D "WIN32" /D "_DEBUG" /D "_CONSOLE" /D "_UNICODE" /D "UNICODE" /Gm /EHsc /RTC1 /MDd /Yc"stdafx.h" /Fp"Debug\TestExpress.pch" /Fo"Debug\\" /Fd"Debug\vc80.pdb" /W3 /c /Wp64 /ZI /TP .\stdafx.cpp ] Creating command line "cl.exe @s:\project\TestExpress\TestExpress\Debug\RSP00000215921192.rsp /nologo /errorReport:prompt"
    Output Window
        
    Compiling... cl : Command line error D8022 : cannot open 's:\project\TestExpress\TestExpress\Debug\RSP00000215921192.rsp'
    Results

        
    Build log was saved at "file://s:\project\TestExpress\TestExpress\Debug\BuildLog.htm" TestExpress - 1 error(s), 0 warning(s)

    Thanks for your responses.
     

  • nuno_donato

    Okay, I ran Filemon.  What a NICE TOOL!  I set a filter to capture only accesses to the S:\project directory, and then I fired up Express, opened the Solution, and did a Build which resulted in the error at issue here.

    The output of Filemon is very revealing, and I think the problem has indeed been captured (it's pretty obvious), but I'm not sure how to interpret what I'm looking at.

    So... the log file is a text file 1.4 MBytes in size.  I can email the whole thing to someone but I have no email address to send it to.  Below is an excerpt of the interesting lines, with a whole bunch of "SUCCESS" lines omitted before and after this block.  It looks like a problem with cl.exe:

    20420 9:26:09 PM VCExpress.exe:172 DIRECTORY S:\project\testexpress\testexpress NOTIFY ENUM DIR Change Notify 
    20421 9:26:09 PM VCExpress.exe:172 WRITE  S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp SUCCESS Offset: 2 Length: 392 
    20422 9:26:09 PM VCExpress.exe:172 WRITE  S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp SUCCESS Offset: 2 Length: 392 
    20423 9:26:09 PM VCExpress.exe:172 DIRECTORY S:\project\testexpress\testexpress NOTIFY ENUM DIR Change Notify 
    20424 9:26:09 PM VCExpress.exe:172 DIRECTORY S:\project\testexpress\testexpress NOTIFY ENUM DIR Change Notify 
    20425 9:26:09 PM VCExpress.exe:172 CLOSE S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp SUCCESS  
    20426 9:26:09 PM VCExpress.exe:172 CLOSE S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp SUCCESS  
    20427 9:26:09 PM VCExpress.exe:172 DIRECTORY S:\project\testexpress\testexpress NOTIFY ENUM DIR Change Notify 
    20428 9:26:09 PM VCExpress.exe:172 DIRECTORY S:\project\testexpress\testexpress NOTIFY ENUM DIR Change Notify 
    20429 9:26:09 PM VCExpress.exe:172 OPEN S:\project\TestExpress\TestExpress\ SUCCESS Options: Open  Access: All 
    20430 9:26:09 PM VCExpress.exe:172 OPEN S:\project\TestExpress\TestExpress\ SUCCESS Options: Open  Access: All 
    20431 9:26:09 PM VCExpress.exe:172 QUERY INFORMATION S:\project\TestExpress\TestExpress\ SUCCESS FileBasicInformation 
    20432 9:26:09 PM VCExpress.exe:172 QUERY INFORMATION S:\project\TestExpress\TestExpress\ SUCCESS FileBasicInformation 
    20433 9:26:09 PM VCExpress.exe:172 CLOSE S:\project\TestExpress\TestExpress\ SUCCESS  
    20434 9:26:09 PM VCExpress.exe:172 CLOSE S:\project\TestExpress\TestExpress\ SUCCESS  
    20435 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\ SUCCESS Options: Open Directory  Access: Traverse 
    20436 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\ SUCCESS Options: Open Directory  Access: Traverse 
    20437 9:26:09 PM cl.exe:1384 QUERY INFORMATION S:\project\TestExpress\TestExpress\ SUCCESS FileFsDeviceInformation 
    20438 9:26:09 PM cl.exe:1384 QUERY INFORMATION S:\project\TestExpress\TestExpress\ SUCCESS FileFsDeviceInformation 
    20439 9:26:09 PM csrss.exe:536 OPEN S:\project\TestExpress\TestExpress\cl.exe NOT FOUND Options: Open  Access: All 
    20440 9:26:09 PM csrss.exe:536 OPEN S:\project\TestExpress\TestExpress\cl.exe NOT FOUND Options: Open  Access: All 
    20441 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\\mspdb80.dll NOT FOUND Options: Open  Access: All 
    20442 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\\mspdb80.dll NOT FOUND Options: Open  Access: All 
    20443 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\\mspdb80.dll NOT FOUND Options: Open  Access: All 
    20444 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\\mspdb80.dll NOT FOUND Options: Open  Access: All 
    20445 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp ACCESS DENIED BOBCAT\jjones 
    20446 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp ACCESS DENIED BOBCAT\jjones 
    20447 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp ACCESS DENIED BOBCAT\jjones 
    20448 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp ACCESS DENIED BOBCAT\jjones 
    20449 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp ACCESS DENIED BOBCAT\jjones 
    20450 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp ACCESS DENIED BOBCAT\jjones 
    20451 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp ACCESS DENIED BOBCAT\jjones 
    20452 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp ACCESS DENIED BOBCAT\jjones 
    20453 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp ACCESS DENIED BOBCAT\jjones 
    20454 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp ACCESS DENIED BOBCAT\jjones 
    20455 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp ACCESS DENIED BOBCAT\jjones 
    20456 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp ACCESS DENIED BOBCAT\jjones 
    20457 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp ACCESS DENIED BOBCAT\jjones 
    20458 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp ACCESS DENIED BOBCAT\jjones 
    20459 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp ACCESS DENIED BOBCAT\jjones 
    20460 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp ACCESS DENIED BOBCAT\jjones 
    20461 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp ACCESS DENIED BOBCAT\jjones 
    20462 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp ACCESS DENIED BOBCAT\jjones 
    20463 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp ACCESS DENIED BOBCAT\jjones 
    20464 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp ACCESS DENIED BOBCAT\jjones 
    20465 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp ACCESS DENIED BOBCAT\jjones 
    20466 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp ACCESS DENIED BOBCAT\jjones 
    20467 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp ACCESS DENIED BOBCAT\jjones 
    20468 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp ACCESS DENIED BOBCAT\jjones 
    20469 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp ACCESS DENIED BOBCAT\jjones 
    20470 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp ACCESS DENIED BOBCAT\jjones 
    20471 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp ACCESS DENIED BOBCAT\jjones 
    20472 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp ACCESS DENIED BOBCAT\jjones 
    20473 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp ACCESS DENIED BOBCAT\jjones 
    20474 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp ACCESS DENIED BOBCAT\jjones 
    20475 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\\rsaenh.dll NOT FOUND Options: Open  Access: All 
    20476 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\\rsaenh.dll NOT FOUND Options: Open  Access: All 
    20477 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp ACCESS DENIED BOBCAT\jjones 
    20478 9:26:09 PM cl.exe:1384 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp ACCESS DENIED BOBCAT\jjones 
    20479 9:26:09 PM VCExpress.exe:172 OPEN S:\project\TestExpress\TestExpress\cl NOT FOUND Options: Open  Access: All 
    20480 9:26:09 PM VCExpress.exe:172 OPEN S:\project\TestExpress\TestExpress\cl NOT FOUND Options: Open  Access: All 
    20481 9:26:09 PM cl.exe:1384 CLOSE S:\project\TestExpress\TestExpress\ SUCCESS  
    20482 9:26:09 PM cl.exe:1384 CLOSE S:\project\TestExpress\TestExpress\ SUCCESS  
    20483 9:26:09 PM VCExpress.exe:172 WRITE  S:\project\TestExpress\TestExpress\Debug\BuildLog.htm SUCCESS Offset: 0 Length: 4096 
    20484 9:26:09 PM VCExpress.exe:172 WRITE  S:\project\TestExpress\TestExpress\Debug\BuildLog.htm SUCCESS Offset: 0 Length: 4096 
    20485 9:26:09 PM VCExpress.exe:172 OPEN S:\project\TestExpress\TestExpress\Debug\vc80.idb NOT FOUND Options: Open  Access: All 
    20486 9:26:09 PM VCExpress.exe:172 OPEN S:\project\TestExpress\TestExpress\Debug\vc80.idb NOT FOUND Options: Open  Access: All 
    20487 9:26:09 PM VCExpress.exe:172 OPEN S:\project\TestExpress\TestExpress\Debug\stdafx.obj NOT FOUND Options: Open  Access: All 
    20488 9:26:09 PM VCExpress.exe:172 OPEN S:\project\TestExpress\TestExpress\Debug\stdafx.obj NOT FOUND Options: Open  Access: All 
    20489 9:26:09 PM VCExpress.exe:172 OPEN S:\project\TestExpress\TestExpress\Debug\TestExpress.obj NOT FOUND Options: Open  Access: All 
    20490 9:26:09 PM VCExpress.exe:172 OPEN S:\project\TestExpress\TestExpress\Debug\TestExpress.obj NOT FOUND Options: Open  Access: All 
    20491 9:26:09 PM VCExpress.exe:172 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000011721348.rsp SUCCESS Options: Open  Access: All 
    20492 9:26:09 PM VCExpress.exe:172 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000011721348.rsp SUCCESS Options: Open  Access: All 
    20493 9:26:09 PM VCExpress.exe:172 QUERY INFORMATION S:\project\TestExpress\TestExpress\Debug\RSP0000011721348.rsp SUCCESS FileAttributeTagInformation 
    20494 9:26:09 PM VCExpress.exe:172 QUERY INFORMATION S:\project\TestExpress\TestExpress\Debug\RSP0000011721348.rsp SUCCESS FileAttributeTagInformation 
    20495 9:26:09 PM VCExpress.exe:172 DELETE  S:\project\TestExpress\TestExpress\Debug\RSP0000011721348.rsp SUCCESS  
    20496 9:26:09 PM VCExpress.exe:172 DELETE  S:\project\TestExpress\TestExpress\Debug\RSP0000011721348.rsp SUCCESS  
    20497 9:26:09 PM VCExpress.exe:172 CLOSE S:\project\TestExpress\TestExpress\Debug\RSP0000011721348.rsp SUCCESS  
    20498 9:26:09 PM VCExpress.exe:172 CLOSE S:\project\TestExpress\TestExpress\Debug\RSP0000011721348.rsp SUCCESS  
    20499 9:26:09 PM VCExpress.exe:172 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp SUCCESS Options: Open  Access: All 
    20500 9:26:09 PM VCExpress.exe:172 OPEN S:\project\TestExpress\TestExpress\Debug\RSP0000021721348.rsp SUCCESS Options: Open  Access: All 

  • DesiGUY

    Hello -

    I am sorry to hear that you are having a problem using the Express product.  The Visual Studio products, including the Express Edition line, do not support building projects over a network.  You indicate that you have mounted it as S, and I assume that you mean this is a mapped drive, which is still a network location (e.g. the processes would have to run over the network).  The environment is only designed to support building projects locally.

    Hearing that this is an important scenario to you is definitely feedback we can and will take into consideration as we plan future releases and build system changes.  If I have misunderstood the scenario that you are working, please do let me know.

    Thank you,
    April Reagan, Visual C++ Program Management


  • Paul Cronk

    I've edited this post (deleted my own negativity) because it was not constructive.  Well, it was, but not in the way you may think. Tongue Tied

  • Keith D

    The build system has very few differences between the Express and Professional editions. My guess is that, if this is a bug (which it looks like it is), it will probably be one in the Professional editions as well.

    The scenario you describe should work. Building off network drives is generally unreliable if you have multiple people (with machine times set differently)  working on it. For your single use, things should be OK though.

    I'll have a member of our test team who owns this area investigate this further and get back to you within a day.

    p.s. Apologies for the delayed responses from the VC++ team. Many of our product team members did not know that we have a specific forum dedicated to VC++ Express and were only monitoring the general VC++ forums (assuming it encompassed more issues). We'll advertise the VC++ Express specific ones better within our team to improve the response rate in the future :) It's really not about ignoring you or any other customers. We love all our customers :)

    Thanks.

  • Compile fails on network drive
Answer this question