Home → Problems →

VC2008 project solutions build failure

• Edit

bill auger

10 Oct, 2014 01:35 PM

of the four windows projects i tried to build - only one of them seems to start building

three of the projects exit with

    "Exception has been thrown by the target of an invocation."

the fourth project begins building but only the VC2013 solution - the VC2008 solution exits with:

    "MSBUILD : warning MSB4078: The project file "LinJam.vcproj" is not supported by MSBuild and cannot be built. "

possibly related to this unsolved discussion: --> http://help.appveyor.com/discussions/problems/675-exception-has-been-thrown-by-the-target-of-an-invocation

1. 1 Posted by bill auger on 10 Oct, 2014 01:42 PM

   

   as a side note - the one with the "cannot be built" error then proceeds to end with

       "Discovering tests...Done"
       "Build success"

   • Edit

2. Support Staff 2 Posted by Feodor Fitsner on 10 Oct, 2014 01:46 PM

   

   Hi Bill,

   Do you also get this error during clone operation?

   -Feodor

   • Edit

3. 3 Posted by bill auger on 10 Oct, 2014 02:04 PM

   

   no i do not see that error - in all cases the first three lines are of the form:

       1 Build started
       2 git clone -q --branch=master ......
       3 git checkout ...........

   and line 4 is one of the errors above

   • Edit

4. Support Staff 4 Posted by Feodor Fitsner on 10 Oct, 2014 02:08 PM

   

   Hm, could you drop a screenshot please?

   -Feodor

   • Edit

5. 5 Posted by bill auger on 10 Oct, 2014 02:16 PM

   

   np - they are all public repos - these links will suffice yes ?

   this is one of them that ends with the "Exception" error
       https://ci.appveyor.com/project/bill-auger/libninjam

   and this is the project that appears to build the VC2013 solution but ends with the "cannot be built" error for the VC2008 solution

       https://ci.appveyor.com/project/bill-auger/linjam

   • Edit

6. Support Staff 6 Posted by Feodor Fitsner on 10 Oct, 2014 02:19 PM

   

   Thanks, will take a look.

   -Feodor

   • Edit

7. Support Staff 7 Posted by Feodor Fitsner on 14 Oct, 2014 07:28 PM

   

   Hi Bill,

   Are you still able to reproduce that Exception has been thrown by the target of an invocation.?

   Re: second project - there is MSBuild 12.0 in PATH by default. Maybe you need the one from .NET 2.0.

   • Edit

8. 8 Posted by Bill Auger on 14 Oct, 2014 08:26 PM

   

   i have not tried since that day - has something changed that may produce
   different results now ?

   regarding your statement about .NET im not to clear on what that entails -
   are you implying that this service only works for .NET apps? - to be clear
   both projects are not a.NET applications they are both cross-platform C++99
   and were made to build on windows using VS2008 express with the standard MS
   compiler

   i cant remember exactly which was the 'second project' - if you mean the
   one that has targets for both VS2008 and VS2013 those sln files were both
   auto-generated simulteneously by the JUCE framework and i dont think it
   requires anything of .NET - but if that is the issue i would need to know
   very explicitly which modifications to make by hand

   • Edit

9. Support Staff 9 Posted by Feodor Fitsner on 14 Oct, 2014 08:56 PM

   

   The only thing that changed since that time is URL to clone public GitHub repo - from https:// to git://

   Regarding this project: https://ci.appveyor.com/project/bill-auger/linjam - msbuild command it's MSBuild 12.0 which in PATH. I'm not sure why it complains on .vcproj (which is obviously supported by MSBuild 12.0), so I meant you may try running it with msbuild.exe which is a part of .NET 2.0 framework (C:\Windows\Microsoft.NET\Framework\v2.0.50727\MSBuild.exe)

   • Edit

10. 10 Posted by Bill Auger on 14 Oct, 2014 10:53 PM

    
    sorry perhaps i have not read enough documentation but i do not see any place to specify (C:\Windows\Microsoft.NET\Framework\v2.0.50727\MSBuild.exe)

    
    

    i tried changing some settings - upon selecting some target explicitly i was able to get a different error tho

    
    

    this was the result specifying Release/x86 -->

    
    1Build started
    2git clone -q --branch=master git://github.com/linjam/linjam.git C:\projects\linjam
    3git checkout -qf d66f1d27f3edcef4338c4e96e49fe0eb1fbf9b8d
    4msbuild "Builds\VisualStudio2008\LinJam.sln" /verbosity:detailed /logger:"C:\Program Files\AppVeyor\BuildAgent\Appveyor.MSBuildLogger.dll"
    5Microsoft (R) Build Engine version 12.0.30723.0
    6[Microsoft .NET Framework, version 4.0.30319.34209]
    7Copyright (C) Microsoft Corporation. All rights reserved.
    8 
    9Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
    10Build started 10/14/2014 10:38:53 PM.
    11Using the MSBuild v3.5 solution wrapper generator with a tools version of 3.5 because the solution file format was version 10 and no tools version was supplied.
    12Project "C:\projects\linjam\Builds\VisualStudio2008\LinJam.sln" on node 1 (default targets).
    13Building with tools version "2.0".
    14Target "ValidateSolutionConfiguration" in file "" from project "C:\projects\linjam\Builds\VisualStudio2008\LinJam.sln" (entry point):
    15Using "Error" task from assembly "Microsoft.Build.Tasks.v3.5, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a".
    16Task "Error"
    17MSBUILD : error MSB4126: The specified solution configuration "Release|x86" is invalid. Please specify a valid solution configuration using the Configuration and Platform properties (e.g. MSBuild.exe Solution.sln /p:Configuration=Debug /p:Platform="Any CPU") or leave those properties blank to use the default solution configuration. [C:\projects\linjam\Builds\VisualStudio2008\LinJam.sln]
    18Done executing task "Error" -- FAILED.
    19Done building target "ValidateSolutionConfiguration" in project "LinJam.sln" -- FAILED.
    20Done Building Project "C:\projects\linjam\Builds\VisualStudio2008\LinJam.sln" (default targets) -- FAILED.
    21 
    22Build FAILED.
    23 
    24"C:\projects\linjam\Builds\VisualStudio2008\LinJam.sln" (default target) (1) ->
    25(ValidateSolutionConfiguration target) -> 
    26  MSBUILD : error MSB4126: The specified solution configuration "Release|x86" is invalid. Please specify a valid solution configuration using the Configuration and Platform properties (e.g. MSBuild.exe Solution.sln /p:Configuration=Debug /p:Platform="Any CPU") or leave those properties blank to use the default solution configuration. [C:\projects\linjam\Builds\VisualStudio2008\LinJam.sln]
    27 
    28    0 Warning(s)
    29    1 Error(s)
    30 
    31Time Elapsed 00:00:09.73
    32Command exited with code 1
    

    
    

    much the same result specifying default/anyCPU -->

    
    

    
    

    26  MSBUILD : error MSB4126: The specified solution configuration "Debug|Any CPU" is invalid. Please specify a valid solution configuration using the Configuration and Platform properties (e.g. MSBuild.exe Solution.sln /p:Configuration=Debug /p:Platform="Any CPU") or leave those properties blank to use the default solution configuration. [C:\projects\linjam\Builds\VisualStudio2008\LinJam.sln]

    
    

    
    

    On Tue, Oct 14, 2014 at 4:56 PM, Feodor Fitsner <[email blocked]> wrote:
    

    // Please reply above this line ================================================== From: Feodor Fitsner (Support staff) The only thing that changed since that time is URL to clone public GitHub repo - from https:// to git:// Regarding this project: https://ci.appveyor.com/project/bill-auger/linjam - msbuild command it's MSBuild 12.0 which in PATH. I'm not sure why it complains on .vcproj (which is obviously supported by MSBuild 12.0), so I meant you may try running it with msbuild.exe which is a part of .NET 2.0 framework (C:\Windows\Microsoft.NET\Framework\v2.0.50727\MSBuild.exe) On Tue, Oct 14 at 08:26 PM, Bill Auger wrote: i have not tried since that day - has something changed that may produce different results now ? regarding your statement about .NET im not to clear on what that entails - are you implying that this service only works for .NET apps? - to be clear both projects are not a.NET applications they are both cross-platform C++99 and were made to build on windows using VS2008 express with the standard MS compiler i cant remember exactly which was the 'second project' - if you mean the one that has targets for both VS2008 and VS2013 those sln files were both auto-generated simulteneously by the JUCE framework and i dont think it requires anything of .NET - but if that is the issue i would need to know very explicitly which modifications to make by hand

    Having trouble reading this? View this discussion online: VC2008 project solutions build failure. Reply with #ignore to stop receiving notifications for this discussion.

    
    
    • Edit

11. 11 Posted by Bill Auger on 12 Apr, 2015 06:22 PM

    

    i have still no resolution to this problem - i have just tried again and
    still none of my apps will build on your servers - i am willing to give
    your service another try but i must say i am not yet impressed

    i am still not clear as to your last reply - i mentioned back then that i
    do not see any way to specify "msbuild.exe" in appveyor settings - are you
    suggesting that i try compling locally from the command line ?

    these are the current build failures of interest to me

    one project https://ci.appveyor.com/project/bill-auger/linjam/ gives the
    following error

        "The specified solution configuration "Release|x64" is invalid."

    but i get a similar error with every combination ive tried of Debug/Release
    and Any/x86/x64 - i have tried also with both VC2008 and VC2013 .sln
    project files

    the other project https://ci.appveyor.com/project/bill-auger/linjam gives
    the following error:

        "The project file "libninjam-static.vcproj" is in the ".vcproj" file
    format, which MSBuild no longer supports."

    • Edit

12. 12 Posted by Bill Auger on 12 Apr, 2015 06:31 PM

    

    to be clear on the last point regarding the .vcproj file - the project file
    specified in appveyor settings is the .sln

    both of these projects are public on github btw - if you would like to see
    the .sln files and/or clone the repos

    • Edit

13. Support Staff 13 Posted by Feodor Fitsner on 12 Apr, 2015 07:52 PM

    

    OK, let's see what's going on. First of all, let's clarify which branch are you trying to build?

    • Edit

14. 14 Posted by Bill Auger on 12 Apr, 2015 11:24 PM

    

    the branch at first was set to master and then i changed it to winxp - i
    did the same for both repos

    • Edit

15. 15 Posted by Bill Auger on 13 Apr, 2015 12:47 AM

    

    oh sry i just realized i posted the same link twice above - the project
    with the error that mentions the .vcproj file is at
    https://ci.appveyor.com/project/bill-auger/libninjam
    <https://ci.appveyor.com/project/bill-auger/linjam>

    • Edit

16. Support Staff 16 Posted by Feodor Fitsner on 16 Apr, 2015 01:12 AM

    

    OK, got linjam running, but seems like some files are missing or there is path issue: https://ci.appveyor.com/project/FeodorFitsner/linjam

    appveyor.yml: https://github.com/FeodorFitsner/linjam/blob/linux/appveyor.yml

    • Edit

17. Support Staff 17 Posted by Feodor Fitsner on 16 Apr, 2015 01:20 AM

    

    libninjam is running too, but there are missing headers too: https://ci.appveyor.com/project/FeodorFitsner/libninjam

    appveyor.yml: https://github.com/FeodorFitsner/libninjam/blob/winxp/appveyor.yml

    If that's DirectX issue take a look at this post: http://help.appveyor.com/discussions/questions/400-is-it-possible-t...

    Hope that helps.

    • Edit

18. 18 Posted by Bill Auger on 16 Apr, 2015 06:17 PM

    

    yes i knew there would be dependency issues but i am very happy now that at
    least the build starts up

    thanks you so much for getting me started

    • Edit

19. 19 Posted by Bill Auger on 17 Apr, 2015 09:01 PM

    

    though i am still unclear as to why Feodor's solutions solved my issues,
    (e.g. if these were proper solutions or kludges - or if my problem is
    specific to VC2008 or 32bit projects), i have noticed that a least part of
    the issue seems to be with the 'platform' parameter - ill mention this here
    in case it may be useful to others

    as best as i can tell Feodor got past the error ".... the '.vcproj' file
     format, which MSBuild no longer supports." by adding to PATH and calling
    msbuild explicitly in the build_script: step

    appveyor.yml ----->
    ```
    build_script:
    - set path=C:\Windows\Microsoft.NET\Framework\v3.5;%path%
    - msbuild path\to\the.sln
      test: off
    ```

    and the error "The specified solution configuration .... is invalid." was
    resolved by explicitly setting 'platform' to 'Win32' in appveyor.yml
    although the documentation at http://www.appveyor.com/docs/appveyor-yml
    line 135 states that this should be one of 'x86', 'x64', or 'Any CPU'.

    appveyor.yml ----->
    ```
    configuration: Release
    platform: Win32
     build:
      project: path\to\the.sln
     test: off
    ```

    i had originally configured via the website where the platform selection
    must be 'x86', 'x64', 'Any CPU', or 'ARM' if not 'Project Default'. this
    was presumably the cause of at least one of my failures because when
    'platform: x86' is specified in appveyor.yml the original error "invalid
    configuration Release/x86" returns.

    • Edit

20. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:55 AM.