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'.
compilation 64bit windows-community-toolkit
add a comment |
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'.
compilation 64bit windows-community-toolkit
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
add a comment |
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'.
compilation 64bit windows-community-toolkit
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
compilation 64bit windows-community-toolkit
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
add a comment |
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
add a comment |
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"
add a comment |
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"
add a comment |
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"
add a comment |
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"
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"
answered Nov 20 at 17:18
Shubhan
25329
25329
add a comment |
add a comment |
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
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