2016_3 batch build in Visual Studio 2017

7 posts, 0 answers
  1. Craig
    Craig avatar
    114 posts
    Member since:
    Nov 2011

    Posted 27 Sep 2018 Link to this post

    Hi

    I'm currently fixed to version 2016_3_1024 of UI for WPF.

    I'd like to build a protected set of assemblies using the batch build targetting .NET 4.0.

    My computer has VS 2017 Community and I have installed the Windows 10 SDK and Windows 8.1 SDK.

    If I try to build the Telerik assemblies using the Build_WPF40.Bat file I get errors:-

    C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(2863,5): error MSB3086: Task could not find "AL.exe" using the SdkToolsPath "" or the registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v8.0A\WinSDK-NetFx40Tools-x86". Make sure the SdkToolsPath is set and the tool exists in the correct processor specific location under the SdkToolsPath and that the Microsoft Windows SDK is installed

    I've tried setting the MSBUILD environment in the batch file to use Visual Studio's MSBUILD but that fails too.

    AL.EXE is in the Windows 10 SDK folders.

    Any suggestions how I can resolve this?

     

     

     

  2. John Schroedl
    John Schroedl avatar
    27 posts
    Member since:
    Sep 2010

    Posted 30 Sep 2019 in reply to Craig Link to this post

    Did you ever figure this one out Craig?

    I'm hitting the same errors when trying to build from a "Developer Command Prompt for VS 2019".

  3. Craig
    Craig avatar
    114 posts
    Member since:
    Nov 2011

    Posted 30 Sep 2019 Link to this post

    Hi John,

    No, sorry. If I recall, I built them interactively in VS.

     

  4. John Schroedl
    John Schroedl avatar
    27 posts
    Member since:
    Sep 2010

    Posted 30 Sep 2019 in reply to Craig Link to this post

    Thanks for the reply Craig. I'll give that a go too...
  5. Martin Ivanov
    Admin
    Martin Ivanov avatar
    2444 posts

    Posted 03 Oct 2019 Link to this post

    Hello,

    This error usually appears when the .NET 4.5 SDK is not installed on the machine. This is available with the Windows 8 SDK. You can try install this SDK version and see how it goes.

    Regards,
    Martin Ivanov
    Progress Telerik

    Get quickly onboarded and successful with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.
  6. John Schroedl
    John Schroedl avatar
    27 posts
    Member since:
    Sep 2010

    Posted 03 Oct 2019 in reply to Martin Ivanov Link to this post

    Interesting. I had the much newer .NET SDKs but not 4.5 specifically. So, I followed the link in the documentation for building from source and installed the .NET 4.5 SDK from the Windows 8 SDK.

    My first attempt at building (Build_WPF45.bat) failed with even more messages but I think that's because I launched it from a "x64 Native Tools Command Prompt for VS 2019" shell. That's my normal shell since I do mainly C++/CLI work.

    When I opened "Developer Command Prompt for VS 2019" and ran the build from there.. Success!!  Thank you both for the help.

    Martin, do you know if there's a plan to make a .NET 4.8 build since that's the last .NET Framework version and we'll need that for a long time to come?  (Obviously, we'll look into .NET Core but currently, that does not work with C++/CLI)

    John

  7. Martin Ivanov
    Admin
    Martin Ivanov avatar
    2444 posts

    Posted 08 Oct 2019 Link to this post

    Hello John,

    Currently, we don't have plans to introduce a .NET 4.8 build. However, it is possible to plan such build in the future.

    Regards,
    Martin Ivanov
    Progress Telerik

    Get quickly onboarded and successful with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.
Back to Top