Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-25421

Create Ansible script for MSVC 2017 and build tools for Mobile Lite Core 2.0 window-lite-net

    XMLWordPrintable

Details

    • Task
    • Resolution: Fixed
    • Major
    • None
    • master
    • build
    • 3
    • Build Team 2017 week 43, Build Team 2017 week 44

    Description

      Get MSVC 2017 added to CBL mobile-litecore-windows.
      Install 2017 community version window manually to test the build first.  Will create separate ticket to track these tools in ansible work.

      List of tools from Jim B

      Tools for net window build

      Here is a list of all the components included in those two:

      Blend for Visual Studio
      .NET Native
      NuGet package manager
      Universal Windows Platform tools
      Windows 10 SDK (10.0.15063.0) for C#, VB, JS
      .NET desktop development tools
      .NET Framework 4.6.1 development
      C# and Visual Basic

      Also I realize you also need:
      Xamarin
      Android SDK / NDK

      Also a manual step is possibly needed for linking the machine to a mac for iOS builds (but possibly not necessary because at this step no "app" is being generateD)

      [5:17 PM] Jim Borden: Oh dear I've forgotten something important on that list:
      .NET Core 1.0 - 1.1 development tools
      [5:17 PM] Jim Borden: C# and Visual Basic Roslyn compilers
      MSBuildalso sounds important, though I can't imagine why it would let you install without those....especially the second one
      [5:19 PM] Jim Borden: And here is a relevant quote from the MSDN forums about unattended install of VS2017
      [5:19 PM] Jim Borden:
          |  To deploy Visual Studio in unattended mode, you must modify the AdminDeployment.xml file. To do this, you must first create the AdminDeployment.xml file by using the /CreateAdminFile <file location> command-line parameter. Then, you can use this file to either push a deployment of Visual Studio to your network or pull it into an installation if you put that file in the Drive:\IDEinstall\packages directory. The AdminDeployment.xml file is not unique to an operating system, architecture, edition of Visual Studio, or operating-system language.Now, there is no the latest documentation of creating and running an unattended installation of visual studio for visual studio 2017, you could refer to the documentation for visual studio 2015: https://msdn.microsoft.com/en-us/library/ee225237.aspx?f=255&MSPPError=-2147217396

      Actually ignore that..further down the forum it says "this doesn't work at all" -> https://social.msdn.microsoft.com/Forums/en-US/e2a583d4-a5b8-44d9-a7a2-0b845e410fe3/vs-2017-unattend...

      https://docs.microsoft.com/en-us/visualstudio/install/workload-component-id-vs-enterprise <-- Helpful for getting IDs to use for automated installation

      Using it as a reference I believe these IDs should do:

      Microsoft.VisualStudio.Workload.ManagedDesktop
      Microsoft.VisualStudio.Workload.NetCoreTools
      Microsoft.VisualStudio.Workload.NetCrossPlat
      Component.Android.NDK.R13B
      Component.Android.SDK23
      Component.JavaJDK
      Component.Xamarin
      Microsoft.VisualStudio.Workload.Universal

      Attachments

        Issue Links

          Activity

            People

              kim.trang Kim Trang (Inactive)
              kim.trang Kim Trang (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                PagerDuty