App does not compile in X64 (but correctly in X86) after Toolkit.UWP update to V5.0











up vote
2
down vote

favorite












After update of Toolkit (and Windows 10 SDK) app does not compile in X64 (but works correctly in X86). Here are the errors:




ILT0005: 'C:Program Files (x86)Microsoft SDKsUWPNuGetPackagesruntime.win10-x64.microsoft.net.native.compiler2.2.1toolsx64ilcToolsrhbind.exe @"C:UserspierrsourcereposMon Gestionnaire de PhotosMon Gestionnaire de Photosobjx64Debugilcintermediaterhbindargs.Mon Gestionnaire de Photos.rsp"' returned exit code 7




and




RHBIND : error RHB0007: Could not load input file 'Microsoft.Toolkit.Uwp.UI.srclink'.











share|improve this question
























  • Hello, I am having exactly the same problem. Have you found a solution?
    – Hong
    Nov 19 at 14:44






  • 1




    No; tried reinstalling everything VS, SDK, Toolkit problem remains
    – Pierresa
    Nov 20 at 15:28










  • Thank you for the information. FYI, I posted a thread: social.msdn.microsoft.com/Forums/windowsapps/en-US/…
    – Hong
    Nov 20 at 16:08










  • I think it is a bug in the compiler that it trips when the name of the app contains a space. Can we try remove the space in the path and see if it compiles?
    – Andrew Au
    8 hours ago










  • 6.2.2 is no longer available from nuget
    – under
    7 hours ago















up vote
2
down vote

favorite












After update of Toolkit (and Windows 10 SDK) app does not compile in X64 (but works correctly in X86). Here are the errors:




ILT0005: 'C:Program Files (x86)Microsoft SDKsUWPNuGetPackagesruntime.win10-x64.microsoft.net.native.compiler2.2.1toolsx64ilcToolsrhbind.exe @"C:UserspierrsourcereposMon Gestionnaire de PhotosMon Gestionnaire de Photosobjx64Debugilcintermediaterhbindargs.Mon Gestionnaire de Photos.rsp"' returned exit code 7




and




RHBIND : error RHB0007: Could not load input file 'Microsoft.Toolkit.Uwp.UI.srclink'.











share|improve this question
























  • Hello, I am having exactly the same problem. Have you found a solution?
    – Hong
    Nov 19 at 14:44






  • 1




    No; tried reinstalling everything VS, SDK, Toolkit problem remains
    – Pierresa
    Nov 20 at 15:28










  • Thank you for the information. FYI, I posted a thread: social.msdn.microsoft.com/Forums/windowsapps/en-US/…
    – Hong
    Nov 20 at 16:08










  • I think it is a bug in the compiler that it trips when the name of the app contains a space. Can we try remove the space in the path and see if it compiles?
    – Andrew Au
    8 hours ago










  • 6.2.2 is no longer available from nuget
    – under
    7 hours ago













up vote
2
down vote

favorite









up vote
2
down vote

favorite











After update of Toolkit (and Windows 10 SDK) app does not compile in X64 (but works correctly in X86). Here are the errors:




ILT0005: 'C:Program Files (x86)Microsoft SDKsUWPNuGetPackagesruntime.win10-x64.microsoft.net.native.compiler2.2.1toolsx64ilcToolsrhbind.exe @"C:UserspierrsourcereposMon Gestionnaire de PhotosMon Gestionnaire de Photosobjx64Debugilcintermediaterhbindargs.Mon Gestionnaire de Photos.rsp"' returned exit code 7




and




RHBIND : error RHB0007: Could not load input file 'Microsoft.Toolkit.Uwp.UI.srclink'.











share|improve this question















After update of Toolkit (and Windows 10 SDK) app does not compile in X64 (but works correctly in X86). Here are the errors:




ILT0005: 'C:Program Files (x86)Microsoft SDKsUWPNuGetPackagesruntime.win10-x64.microsoft.net.native.compiler2.2.1toolsx64ilcToolsrhbind.exe @"C:UserspierrsourcereposMon Gestionnaire de PhotosMon Gestionnaire de Photosobjx64Debugilcintermediaterhbindargs.Mon Gestionnaire de Photos.rsp"' returned exit code 7




and




RHBIND : error RHB0007: Could not load input file 'Microsoft.Toolkit.Uwp.UI.srclink'.








compilation 64bit windows-community-toolkit






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 15 at 19:39









RangerRanger

1,0491922




1,0491922










asked Nov 15 at 18:14









Pierresa

111




111












  • Hello, I am having exactly the same problem. Have you found a solution?
    – Hong
    Nov 19 at 14:44






  • 1




    No; tried reinstalling everything VS, SDK, Toolkit problem remains
    – Pierresa
    Nov 20 at 15:28










  • Thank you for the information. FYI, I posted a thread: social.msdn.microsoft.com/Forums/windowsapps/en-US/…
    – Hong
    Nov 20 at 16:08










  • I think it is a bug in the compiler that it trips when the name of the app contains a space. Can we try remove the space in the path and see if it compiles?
    – Andrew Au
    8 hours ago










  • 6.2.2 is no longer available from nuget
    – under
    7 hours ago


















  • Hello, I am having exactly the same problem. Have you found a solution?
    – Hong
    Nov 19 at 14:44






  • 1




    No; tried reinstalling everything VS, SDK, Toolkit problem remains
    – Pierresa
    Nov 20 at 15:28










  • Thank you for the information. FYI, I posted a thread: social.msdn.microsoft.com/Forums/windowsapps/en-US/…
    – Hong
    Nov 20 at 16:08










  • I think it is a bug in the compiler that it trips when the name of the app contains a space. Can we try remove the space in the path and see if it compiles?
    – Andrew Au
    8 hours ago










  • 6.2.2 is no longer available from nuget
    – under
    7 hours ago
















Hello, I am having exactly the same problem. Have you found a solution?
– Hong
Nov 19 at 14:44




Hello, I am having exactly the same problem. Have you found a solution?
– Hong
Nov 19 at 14:44




1




1




No; tried reinstalling everything VS, SDK, Toolkit problem remains
– Pierresa
Nov 20 at 15:28




No; tried reinstalling everything VS, SDK, Toolkit problem remains
– Pierresa
Nov 20 at 15:28












Thank you for the information. FYI, I posted a thread: social.msdn.microsoft.com/Forums/windowsapps/en-US/…
– Hong
Nov 20 at 16:08




Thank you for the information. FYI, I posted a thread: social.msdn.microsoft.com/Forums/windowsapps/en-US/…
– Hong
Nov 20 at 16:08












I think it is a bug in the compiler that it trips when the name of the app contains a space. Can we try remove the space in the path and see if it compiles?
– Andrew Au
8 hours ago




I think it is a bug in the compiler that it trips when the name of the app contains a space. Can we try remove the space in the path and see if it compiles?
– Andrew Au
8 hours ago












6.2.2 is no longer available from nuget
– under
7 hours ago




6.2.2 is no longer available from nuget
– under
7 hours ago












1 Answer
1






active

oldest

votes

















up vote
2
down vote













I had a similar issues, Downgrading Microsoft.NETCore.UniversalWindowsPlatform from 6.2.2 to 6.1.9 resolves the issues.



The real issue was from a dependent package of Microsoft.NETCore.UniversalWindowsPlatform 6.2.2 : "Microsoft.Net.Native.Compiler/2.2.1" whereas the Microsoft.NETCore.UniversalWindowsPlatform 6.1.9 depends on "Microsoft.Net.Native.Compiler/2.1.8"






share|improve this answer





















    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53325579%2fapp-does-not-compile-in-x64-but-correctly-in-x86-after-toolkit-uwp-update-to-v%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    2
    down vote













    I had a similar issues, Downgrading Microsoft.NETCore.UniversalWindowsPlatform from 6.2.2 to 6.1.9 resolves the issues.



    The real issue was from a dependent package of Microsoft.NETCore.UniversalWindowsPlatform 6.2.2 : "Microsoft.Net.Native.Compiler/2.2.1" whereas the Microsoft.NETCore.UniversalWindowsPlatform 6.1.9 depends on "Microsoft.Net.Native.Compiler/2.1.8"






    share|improve this answer

























      up vote
      2
      down vote













      I had a similar issues, Downgrading Microsoft.NETCore.UniversalWindowsPlatform from 6.2.2 to 6.1.9 resolves the issues.



      The real issue was from a dependent package of Microsoft.NETCore.UniversalWindowsPlatform 6.2.2 : "Microsoft.Net.Native.Compiler/2.2.1" whereas the Microsoft.NETCore.UniversalWindowsPlatform 6.1.9 depends on "Microsoft.Net.Native.Compiler/2.1.8"






      share|improve this answer























        up vote
        2
        down vote










        up vote
        2
        down vote









        I had a similar issues, Downgrading Microsoft.NETCore.UniversalWindowsPlatform from 6.2.2 to 6.1.9 resolves the issues.



        The real issue was from a dependent package of Microsoft.NETCore.UniversalWindowsPlatform 6.2.2 : "Microsoft.Net.Native.Compiler/2.2.1" whereas the Microsoft.NETCore.UniversalWindowsPlatform 6.1.9 depends on "Microsoft.Net.Native.Compiler/2.1.8"






        share|improve this answer












        I had a similar issues, Downgrading Microsoft.NETCore.UniversalWindowsPlatform from 6.2.2 to 6.1.9 resolves the issues.



        The real issue was from a dependent package of Microsoft.NETCore.UniversalWindowsPlatform 6.2.2 : "Microsoft.Net.Native.Compiler/2.2.1" whereas the Microsoft.NETCore.UniversalWindowsPlatform 6.1.9 depends on "Microsoft.Net.Native.Compiler/2.1.8"







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 20 at 17:18









        Shubhan

        25329




        25329






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53325579%2fapp-does-not-compile-in-x64-but-correctly-in-x86-after-toolkit-uwp-update-to-v%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            404 Error Contact Form 7 ajax form submitting

            How to know if a Active Directory user can login interactively

            TypeError: fit_transform() missing 1 required positional argument: 'X'