Home → Problems →

error MSB8008: Specified platform toolset (v110) is not installed or invalid

• Edit

amaitland

19 Jan, 2015 05:16 AM

Hi,

I know this is somewhat a duplicate of http://help.appveyor.com/discussions/problems/1291-error-msb8008-sp.... I do have some additional information to add.

Now the interesting thing is that we've previously been using AppVeyor with great success, it's only just recently that builds broken without any changes in the scripts. The error is exactly the same as issue 1291

"C:\projects\cefsharp\CefSharp.Core\CefSharp.Core.vcxproj" (default target) (6:5) ->
(PlatformPrepareForBuild target) ->
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\Win32\Microsoft.Cpp.Win32.Targets(518,5): error MSB8008: Specified platform toolset (v110) is not installed or invalid. Please make sure that a supported PlatformToolset value is selected. [C:\projects\cefsharp\CefSharp.Core\CefSharp.Core.vcxproj]

https://ci.appveyor.com/project/cefsharp/cefsharp/build/39.0.0-CI627

CefSharp is a mixture of c#/c++ for which we target VC++ 2012 Redist. The project solution is VS 2012.

Has anything changed in the build environment? The builds stopped working a little over three weeks ago.

Regards,
Alex

1. 1 Posted by amaitland on 19 Jan, 2015 06:25 AM

   

   Our yml file https://github.com/cefsharp/CefSharp/blob/master/appveyor.yml

   • Edit

2. Support Staff 2 Posted by Feodor Fitsner on 19 Jan, 2015 05:42 PM

   

   On December 25 there was VS 2010 SP1 installed to all build worker images. Though I'm not sure how that could affected VS 2012.

   Is there any reason you are staying on VS 2012? There is VS 2013 Community Edition on unstable image which works perfectly for C++ stuff.

   • Edit

3. 3 Posted by amaitland on 20 Jan, 2015 12:36 AM

   

   Interesting to know VS 2012 SP1 was installed, possibly changed some environment variables? I'll look into it further. Thanks!

   Currently our releases are compiled for .Net 4.0 and VC++ 2012, it's not specifically VS 2012 that we need.

   • Edit

4. 4 Posted by amaitland on 20 Jan, 2015 12:40 AM

   

   That should have been VS 2010 SP1

   • Edit

5. Support Staff 5 Posted by Feodor Fitsner on 20 Jan, 2015 12:49 AM

   

   Yeah, it was 2010 SP1, not 2012.

   • Edit

6. 6 Posted by amaitland on 20 Jan, 2015 01:35 AM

   

   That was just a typo on my behalf. I'm still thinking it's probably environment variable related. Will let you know what I find.

   • Edit

7. 7 Posted by amaitland on 20 Jan, 2015 03:54 AM

   

   Looks like I have a resolution, I started looking into the environment variables and it appears that the default msbuild was the version from VS 2013 ( C:\Program Files (x86)\MSBuild\12.0\Bin\MSBuild.exe ). Once I specified the path of the .Net 4.0 version (C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe) everything started to work again.

   I'm guessing something changed somewhere along the lines. Not the problem I was expecting. Possibly relevant to issue 1291

   • Edit

8. Support Staff 8 Posted by Feodor Fitsner on 20 Jan, 2015 04:08 AM

   

   Right, there is MSBuild 12.0 in PATH. Anyway, thanks for update - glad you managed to make it work!

   • Edit

9. amaitland closed this discussion on 22 Jan, 2015 10:18 PM.