CSC error (CS2001) for prev. successful build

reg's Avatar


12 Aug, 2015 11:14 PM

For example:

Last successful build here (~8-9 days ago):


3>CSC : error CS2001: Source file 'Version.cs' could not be found [C:\projects\vssolutionbuildevent\Bridge\Bridge.csproj]
         The command exited with code 1.
       Done executing task "Csc" -- FAILED.
     3>Done building target "CoreCompile" in project "Bridge.csproj" -- FAILED

The 'Version.cs' above should be generated with our script:

#[File write("#[var pDirBridge]Version.cs"):#[var cs]]

and with diagnostic key you can see this here:

[TRACE]: FileComponent: successful stWrite - 'C:\projects\vssolutionbuildevent\Bridge/Version.cs'

File should exist...
a new improvements :) ?

  1. Support Staff 1 Posted by Feodor Fitsner on 13 Aug, 2015 01:17 AM

    Feodor Fitsner's Avatar

    This is the most recent change and it was mostly VS 2015 image:

    Your account is still on Azure where VS 2013 is only installed. I don't know the specifics of your project, so it's hard to say what's broken or what change is affecting your build.

    I can move your account to a new faster environment, so you can have faster turnaround (and RDP) while fixing the build. Though that environment has VS 2015 installed too.

  2. Support Staff 2 Posted by Feodor Fitsner on 13 Aug, 2015 02:30 AM

    Feodor Fitsner's Avatar

    So, basically on that Azure image there were only 2 changes affecting VS 2013 IDE: SSDT and CodeContracts updates. Hope that helps.

  3. 3 Posted by reg on 13 Aug, 2015 10:09 AM

    reg's Avatar

    For this project used 'Ignore appveyor.yml' and selected the Windows Server 2012 R2 as worker image
    But I also checked yesterday: Previous Windows Server 2012 R2 and Default Azure

    I can move your account to a new faster environment, so you can have faster turnaround (and RDP) while fixing the build.

    it will be useful for debugging... any variant for accessing to shell or to project directory

    but it's strange, this problem should be with writing into selected folder:

    • This requires a standard mscorlib.dll from .NET and used StreamWriter for this - a new some restrictions ? o_O
    • Script tried this path: C:\projects\vssolutionbuildevent\Bridge/Version.cs and I can't see any messages about exception for this operation, i.e. it also successfully finished.

    • The project file contains simply:

        <Compile Include="Version.cs" />

    Most problems I also see with naming projects on bitbucket. All names has been automatically converted to lowercase and we have a next differences:

    but as I wrote above, I can't see any exception for this operation.

    ok, I will also try manually checking this file etc.

  4. 4 Posted by reg on 13 Aug, 2015 12:58 PM

    reg's Avatar

    well, I don't know - all exists.. problem not with scripts

    maybe it's really problem with case sensitivity for part of path as vssolutionbuildevent etc. after new changes ? or simply, any problem with paths for msbuild tool

  5. Support Staff 5 Posted by Feodor Fitsner on 14 Aug, 2015 06:51 AM

    Feodor Fitsner's Avatar

    I've moved your account to a faster build environment. You can look into build worker VM via RDP:

  6. 6 Posted by reg on 14 Aug, 2015 02:23 PM

    reg's Avatar

    This reproduced on PC where installed the new VS2015 & MSBuild\14.0 !
    problem with new changes from there...

    the our core with scripts engine is also works through msbuild.exe, so need to look new changes.

    Temporarily, this problem has been resolved is very simply with key to msbuild: /m:1

    Thank you Feodor!

    rdp for manually building it's a great way to finding all problems

  7. reg closed this discussion on 14 Aug, 2015 02:24 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac

Recent Discussions

07 Jul, 2020 06:21 PM
07 Jul, 2020 03:15 PM
05 Jul, 2020 02:33 AM
03 Jul, 2020 07:29 PM
03 Jul, 2020 03:53 AM


02 Jul, 2020 09:09 PM
02 Jul, 2020 03:24 PM
01 Jul, 2020 01:12 PM
30 Jun, 2020 04:26 PM
25 Jun, 2020 05:54 PM
24 Jun, 2020 08:11 AM