Home → Questions →

Visual Studio SDK

• Edit

Irdis

11 Dec, 2013 05:07 PM

Hello,
Thank you for a great service. It works perfectly, however I cannot build the whole solution assemblies because of missing Visual Studio SDK targets.
d:\Builds\rod0amcgiu\src\trunk\VSTalk\VSTalk.Extension\VSTalk.Extension.csproj(308,3): error MSB4019: The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\VSSDK\Microsoft.VsSDK.targets" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.
Could you please install them to your build server? It's just 11Mb update available on the official visual studio page.
Thank you in advance!

1. Support Staff 1 Posted by Feodor Fitsner on 11 Dec, 2013 05:33 PM

   

   Hi,

   Thanks for your interest in AppVeyor!

   VS SDK requires full Visual Studio SKU, but at the moment we have only Express versions of VS installed on build machines. That works for many projects, but not for VS SDK and VSTO ones, sorry.

   We still have to figure out how to support these kinds of projects. Stay tuned.

   -Feodor

   • Edit

2. Support Staff 2 Posted by Feodor Fitsner on 11 Dec, 2013 05:41 PM

   

   Hey, I've just copied VS SDK target files on build machines. For the sake of experiment could you please try building and see if it works? If it doesn't then we'll try something else next time.

   • Edit

3. 3 Posted by jorge costa on 18 Mar, 2014 05:45 PM

   

   Hi,

   Have you remove the target files?

   I still get some issues

   278"C:\projects\vssonarqubeextension\VSSonarQubeExtension.sln" (default target) (1) ->
   279"C:\projects\vssonarqubeextension\VSSonarExtension.Test\VSSonarExtension.Test.csproj" (default target) (3) ->
   280"C:\projects\vssonarqubeextension\VSSonarExtension\VSSonarExtension.csproj" (default target) (2:2) ->
   281 C:\projects\vssonarqubeextension\VSSonarExtension\VSSonarExtension.csproj(322,3): error MSB4019: The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\VSSDK\Microsoft.VsSDK.targets" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.
   282
   283 4 Warning(s)
   284 2 Error(s)

   • Edit

4. Support Staff 4 Posted by Feodor Fitsner on 18 Mar, 2014 06:01 PM

   

   There are new build server images that do not contain VS SDK files yet.

   I will update the image and let you know.

   • Edit

5. Support Staff 5 Posted by Feodor Fitsner on 18 Mar, 2014 07:36 PM

   

   OK, give it another try and let me know how it goes.

   • Edit

6. 6 Posted by jorge costa on 19 Mar, 2014 04:32 PM

   

   apparently there is still something going on here.

   293"C:\projects\vssonarqubeextension\VSSonarQubeExtension.sln" (default target) (1) ->
   294"C:\projects\vssonarqubeextension\VSSonarExtension\VSSonarExtension.csproj" (default target) (2) ->
   295(FindSDKInstallation target) ->
   296 C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\VSSDK\Microsoft.VsSDK.Common.targets(74,5): error VSSDK1036: Can not find the installation for VS SDK. [C:\projects\vssonarqubeextension\VSSonarExtension\VSSonarExtension.csproj]
   297 C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\VSSDK\Microsoft.VsSDK.Common.targets(76,7): error MSB4018: The "FindVsSDKInstallation" task failed unexpectedly. [C:\projects\vssonarqubeextension\VSSonarExtension\VSSonarExtension.csproj]
   298C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\VSSDK\Microsoft.VsSDK.Common.targets(76,7): error MSB4018: System.ArgumentNullException: Value cannot be null. [C:\projects\vssonarqubeextension\VSSonarExtension\VSSonarExtension.csproj]
   299C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\VSSDK\Microsoft.VsSDK.Common.targets(76,7): error MSB4018: Parameter name: path1 [C:\projects\vssonarqubeextension\VSSonarExtension\VSSonarExtension.csproj]
   300C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\VSSDK\Microsoft.VsSDK.Common.targets(76,7): error MSB4018: at System.IO.Path.Combine(String path1, String path2) [C:\projects\vssonarqubeextension\VSSonarExtension\VSSonarExtension.csproj]
   301C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\VSSDK\Microsoft.VsSDK.Common.targets(76,7): error MSB4018: at Microsoft.VsSDK.Build.Tasks.FindVsSDKInstallation.get_IncludesPath() [C:\projects\vssonarqubeextension\VSSonarExtension\VSSonarExtension.csproj]
   302 C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\VSSDK\Microsoft.VsSDK.Common.targets(76,7): error MSB4028: The "FindVsSDKInstallation" task's outputs could not be retrieved from the "IncludesPath" parameter. Value cannot be null. [C:\projects\vssonarqubeextension\VSSonarExtension\VSSonarExtension.csproj]
   303C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\VSSDK\Microsoft.VsSDK.Common.targets(76,7): error MSB4028: Parameter name: path1 [C:\projects\vssonarqubeextension\VSSonarExtension\VSSonarExtension.csproj]
   304

   • Edit

7. Support Staff 7 Posted by Feodor Fitsner on 19 Mar, 2014 04:41 PM

   

   I see. It means simple throwing SDK target files and assemblies won't make it work.
   OK, we have to find another way...

   • Edit

8. 8 Posted by jorge costa on 19 Mar, 2014 04:53 PM

   

   i think you have your solution here:
   http://blogs.msdn.com/b/aaronmar/archive/2011/05/10/visual-studio-e...

   • Edit

9. Support Staff 9 Posted by Feodor Fitsner on 19 Mar, 2014 05:26 PM

   

   wow, impressive guide :)

   I will try to follow it in the meantime to see if it works, thanks!

   • Edit

10. Support Staff 10 Posted by Feodor Fitsner on 19 Mar, 2014 05:30 PM

    

    Is your project public?

    • Edit

11. 11 Posted by jorge costa on 19 Mar, 2014 05:38 PM

    

    yep, https://github.com/jmecosta/VSSonarQubeExtension

    • Edit

12. Support Staff 12 Posted by Feodor Fitsner on 20 Mar, 2014 01:22 AM

    

    OK, I have some progress.

    I was able to build a simple VSIX extension:
    https://ci.appveyor.com/project/feodorf1/vs-extension-test/build/1.0.4

    Sources are here: https://github.com/FeodorFitsner/vs-extension-test

    Let me know if it works for your project.

    • Edit

13. 13 Posted by Jorge Costa on 20 Mar, 2014 06:31 AM

    

    Its compiling now, thanks. Tests are now failing but its because I have
    some messed up references.

    • Edit

14. Support Staff 14 Posted by Feodor Fitsner on 20 Mar, 2014 06:41 AM

    

    Nice, thanks for the update!

    • Edit

15. 15 Posted by Mike Fourie on 01 Jun, 2014 10:33 AM

    

    How about the VS 2013 SDK?

    I'm getting

    MyHistory -> C:\projects\myhistory\Main\MyHistory\bin\VS2012_Debug\Microsoft.ALMRangers.Samples.MyHistory.vsix 14C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\VSSDK\Microsoft.VsSDK.targets(400,5): error MSB4018: The "GetDeploymentPathFromVsixManifest" task failed unexpectedly. [C:\projects\myhistory\Main\MyHistory\MyHistory.csproj]
    15C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\VSSDK\Microsoft.VsSDK.targets(400,5): error MSB4018: System.Runtime.InteropServices.COMException (0x80030002): could not be found.

    • Edit

16. 16 Posted by Jorge Costa on 01 Jun, 2014 02:00 PM

    

    Maybe you can try to disable the deployment of the vsix in release. My
    builds uses vssdk 13 already and it works

    • Edit

17. Support Staff 17 Posted by Feodor Fitsner on 01 Jun, 2014 03:12 PM

    

    Exactly, deployment must be disabled to make it work on AV.

    • Edit

18. 18 Posted by Mike Fourie on 01 Jun, 2014 05:18 PM

    

    Thanks guys!

    • Edit

19. 19 Posted by Steve Cadwallad... on 24 Jul, 2014 12:16 PM

    

    VS SDK compilation support is fantastic and I appreciate how well it worked. :)

    Microsoft provides an integration tests framework as part of the default extension project that lets you simulate user actions within an experimental instance of Visual Studio. The deployment setting referenced above ties into that. Not knowing what all is involved behind the scenes, any thoughts around supporting the ability to run integration tests?

    Even without CI testing, having CI builds up and running is wonderful - thanks. :)

    • Edit

20. Support Staff 20 Posted by Feodor Fitsner on 25 Jul, 2014 05:42 AM

    

    That's a good question. We could look into that at some point. In general, it's always a pain to run something interactively on a build server. Do you have any previous experience of running these tests on other CI solutions?

    • Edit

21. 21 Posted by Jorge Costa on 25 Jul, 2014 05:58 AM

    

    There are 2 ways, first you enable auto login of the build agent and
    disable any screensaver. The other is to run the build client as a service
    and set the allow interact with desktop.

    We found that the second is not as good when you want to use frameworks
    like white or sikuli. We mostly use the first and we have the agent with a
    vnc server there and we use a remote client to establish the vnc connection
    once you close the vnc client you can choose to leave the desktop open. And
    it works.

    But for the vssdk integration test I think you only need to run as a
    service and enable the allow imteraction

    • Edit

22. Support Staff 22 Posted by Feodor Fitsner on 25 Jul, 2014 01:14 PM

    

    I see, thanks!

    • Edit

23. 23 Posted by steve.cadwallad... on 25 Jul, 2014 02:38 PM

    

    I haven't had it working in a CI (headless) environment before.  I see there's some other thoughts below.  I would be interested in doing some of the leg work to prove it out in azure if you think it's something you'd be open to integrating?

    • Edit

24. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:46 AM.