-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't run GenerateResource Task #346
Comments
From @livarcocc on November 1, 2016 5:30 cc @nguerrera |
From @piotrpMSFT on November 1, 2016 5:38 This likely belongs in the SDK repo. @nguerrera do you want me to move it? |
@livarcocc @piotrpMSFT BTW as @NTaylorMullen said, we think this is a dup, but we just can't find it. This is the "resources don't seem to work properly" issue I mentioned at today's 4:30pm standup/sync. |
From @nguerrera on November 1, 2016 16:24 Go ahead and create a new issue on the SDK. Please provide complete repro steps. |
@NTaylorMullen can you add repro steps to this? E.g. upload a project to GitHub? |
So I tried to get the most minimal project possible. Looks like it's related to resx files and desktop. Swapped from TargetFrameworks => TargetFramework and I get an additional explosion after the
Anyways, here's the repro. Run test.ps1 (does restore3/builid3) to see explosions. 💥 |
Workaround: define this property <GenerateResourceMSBuildArchitecture>CurrentArchitecture</GenerateResourceMSBuildArchitecture> in your project. The problem is that I think setting that property in an SDK .props/.targets is the right fix for this. .NET Core builds should use the One wrinkle: I'm not entirely sure what differs when a different resgen runs. I think it's ok to just use the one that works, but I don't understand it deeply. |
Yes, I had just hit this |
Putting in a workaround in SDK and will file bug on msbuild to fix for RC2. |
@rainersigwald Where do you recommend putting this? I'm trying to build git://libvirt.org/libvirt-csharp.git, and adding the node you suggested to the first, unconditional |
@masaeedu What version of VS or CLI are you using. This issue should be fixed. |
@nguerrera Thanks for the quick response. I'm using the CLI, version 1.0.0-rc3-004530. I don't see this issue building from Visual Studio 2017 (version 15.0.0-RC.3+26127.3). If you have the same version of the CLI, could you try cloning the repo I linked, cd-ing to |
I see this is closed, but just FYI. WPF app that was originally built with VS 2015 .NET 4.5.2, opened it up and built with VS 2017: When building with "Microsoft (R) Build Engine version 15.1.1012.6693" it fails with the OP error. This is not using .NET Core, though please excuse me if I misunderstand that part, still getting a hold on .NET Standard, Core, CLI, etc. If there is a better place to put this information let me know and I'd be happy to copy this comment there. |
I had the same Error (in version 16.9.3) but By Repairing Visual Studio 2019, Updating last version of windows 10, close VS, delete .vs hidden folder (under solution folder) ,bin and obj folder then restart your VS . Fortunately My problem was solved. |
Co-authored-by: Vlada Shubina <vshubina@microsoft.com>
From @NTaylorMullen on November 1, 2016 0:30
After
dotnet migrate
ing Microsoft.AspNetCore.Razor.Design attempting to restore3/build3 results in the following error:C:\Users\nimullen\AppData\Local\Microsoft\dotnet\sdk\1.0.0-preview3-003892\Microsoft.Common.CurrentVersion.targets(2801,5): error MSB4216: Could not run the "GenerateResource" task because MSBuild could not create or connect to a task host with runtime "CLR4" and architecture "x86". Please ensure that (1) the requested runtime and/or architecture are available on the machine, and (2) that the required executable "C:\Users\nimullen\AppData\Local\Microsoft\dotnet\sdk\1.0.0-preview3-003892\MSBuild.exe" exists and can be run. [C:\Users\nimullen\Documents\GitHub\RazorTooling\src\Microsoft.AspNetCore.Razor.Design\Microsoft.AspNetCore.Razor.Design.csproj]
I thought I recalled seeing an issue associated with GenerateResource task being unable to run but I can no longer find it. Feel free to move or close this issue as a duplicate.
Dotnet info:
Copied from original issue: dotnet/cli#4556
The text was updated successfully, but these errors were encountered: