Home → Problems →

CSC error (CS2001) for prev. successful build

• Edit

reg

12 Aug, 2015 11:14 PM

For example:

• 67ec8876 - https://ci.appveyor.com/project/3Fs/vssolutionbuildevent/build/buil...
• and new build for 67ec8876 - https://ci.appveyor.com/project/3Fs/vssolutionbuildevent/build/buil...

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

• https://ci.appveyor.com/project/3Fs/vssolutionbuildevent/build/buil...

Details

https://ci.appveyor.com/project/3Fs/vssolutionbuildevent/build/buil...

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:
https://ci.appveyor.com/project/3Fs/vssolutionbuildevent/build/buil...

[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

   

   This is the most recent change and it was mostly VS 2015 image: http://www.appveyor.com/updates/2015/08/09

   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.

   • Edit

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

   

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

   • Edit

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

   

   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:

     <ItemGroup>
       ....
       <Compile Include="Version.cs" />
     </ItemGroup>
   

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

   • vssolutionbuildevent & vsSolutionBuildEvent (current project on github: https://github.com/3F/vsSolutionBuildEvent)

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

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

   • Edit

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

   

   https://ci.appveyor.com/project/3Fs/vssolutionbuildevent/build/buil...

   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

   • Edit

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

   

   I've moved your account to a faster build environment. You can look into build worker VM via RDP: http://www.appveyor.com/docs/how-to/rdp-to-build-worker

   • Edit

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

   

   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

   • https://ci.appveyor.com/project/3Fs/vssolutionbuildevent/build/buil...
     • the old build of this commit: https://ci.appveyor.com/project/3Fs/vssolutionbuildevent/build/buil...

   Thank you Feodor!

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

   • Edit

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