-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Build error GenerateDepFiles with .net core 2.1.602 #2540
Comments
|
Same here with current dotnet 2.2.202 on MacOS Mojave 10.14.4 with Mono 5.18.1.3 |
UPDATE: Downgraded net core from 2.2.202 to 2.2.104 and build started working again. This seems to confirm the issue is directly caused by the latest dotnet update and not VS. |
@alvaroemmanuel i agree with you. |
I am a bit confused. Can someone please clarify with reasonable amount of detail - what happens after what? cc @mhutch |
Sorry, no hello world possible. Then make your updates,, and you'll get Version: 2.1.602 or Version: 2.2.202 at the moment. Steps to Reproduce (maybe:) Take a clean installation of Ubuntu 18.04 Then: Install dotnetcore Version: 2.1.602 or Version: 2.2.202 you will not be able to build your projects anymore, neither with monodevelop nor with msbuild. if you downgrade to eg. dotnetcore 2.2.104 , everything is fine again. hope it helped |
I have the same problem. Had a Xamarin.Forms project in VS2017 for Mac. Updated to the latest .NET Core 2.2.202 last week, but I failed to check if it compiled. Yesterday I installed VS2019 for Mac and I get the same error building my project. So I decided to create a new project based on the Xamarin.Forms template project. That throws the same error. So hopefully you can repro that... |
Same problem here...
|
Yes, that fixed it for my template project and regular project as well. |
same problem with rider on ubuntu 18.04 |
seems this error is discussed here too: |
Been having the exact same issue for a week now on Ubuntu 18.04. Is there any fix in sight? downgraded to 105 for now but we can't stay on a stale version for ever. Does anybody have a solution? thanks |
Same issue. Using Linux Mint 19.1 Not even sure how to get to the older build versions mentioned above. |
Signed-off-by: Sachin Shah <zakaff@gmail.com>
* Jupyter extensions in Docker image Adds Jupyter extension to Docker image for #199 * Docker update for dotnet/core#2540 Signed-off-by: Sachin Shah <zakaff@gmail.com>
@daerogami Try: |
This is also reproducing with the following version combination:
|
Link to an Azure DevOps build with a consistent repro: https://dev.azure.com/dotnet/IronLanguages/_build/results?buildId=16441 |
same error with update to .net core 2.1.604 , nothing changed |
I update .NET SDK to 2.2.203 and .NET Core to 2.2.4 and the issue resolved for me... |
@jkoritzinsky can you please help me understand what is wrong where and who should take care of it? |
@karelz I followed the chain down through the various referenced issues and ended up finding the solution for my case by following this chain: NuGet/Home#7956 and then to the internal ticket. Looks like a combination of a .NET SDK that uses NuGet 5 and a VS for Mac or MonoDevelop that uses NuGet 4 causes a weird type-load issue since NuGet moved a type in 5 and didn't correctly add a type forward. Based on the versions, it seems to be the VS for Mac side of dotnet/sdk#3124. The next version of VS for Mac should fix it. |
OK, nothing left to track here then. Thanks @jkoritzinsky! (and I really hope I did not misunderstand your reply :)) |
I just had this issue this morning after installing 2.1.603 so I can compile for 2.1.10 for AWS Lambda functions. Found a solution online which was to upgrade to VS for Mac 8.1 preview 2. That worked until VS for Mac started crashing. Reinstalled VS for Mac stable (8.0.9) I noticed it installed 2.1.506. Build fails. Uninstalled 2.1.603, build now works. I don't get what the difference is between 506 and 603, why they were both released not the same day, and why 603 does things with nuget 5. But at least I am able to work again. |
506 and 603 target different VS version: https://github.com/dotnet/core/blob/master/release-notes/2.1/2.1.603-SDK/2.1.603-SDK-download.md |
Ah yep, that makes sense @karelz. When I was looking at the download page 506 says it supports Visual Studio 2017 (v15.9) and 603 says it supports Visual Studio 2017 (v16). I now realise that VS for Mac is neither of these. I'll be sure to dig around more in the release notes in future to be sure I get the correct version. |
Fails as well for mono 5.20.1.19 and dotnet 2.2.203 on Ubuntu 19.04, with MonoDevelop and Rider.
|
Here is a help article which explains the problem, lists all incompatible configurations, and shows possible ways to resolve the problem: https://rider-support.jetbrains.com/hc/en-us/articles/360004180039 @ststeiger in Rider, you should get a notification which redirects you to this article. |
@AndreyAkinshin: Just checked: not in 2019.1.1, but updated to 2019.2, and there, yes. Solved, built mono 6 from source. |
What's 2019.1.1 and 2019.2?
Are you saying that mono version 6.x doesn't have this bug? If yes, can you try with packages instead of building from source? In NuGet/Home#7956 (comment) we determined that this is caused by the version of nuget being bundled. |
It's versions of Rider. In Rider 2019.2, we significantly improved our diagnostics: once you hit this problem, Rider will notify you about it and tell you how to fix it. Rider 2019.1 also knows how to detect this problem, but it doesn't cover all the possible misconfiguration cases.
Actually, it's not a bug, it's an incompatible configuration. Mono 5.x uses NuGet 4.x; Mono 6.x uses NuGet 5.x. So, Mono 5.x is compatible with versions of .NET Core SDK that use NuGet 4.x (e.g., 2.1.505 or 2.2.108), and Mono 6.x is compatible with versions of .NET Core SDK that use NuGet 5.x (e.g., 3.0.100-preview6). You can find all the details (including the list of bundled NuGet in each version of Mono and .NET Core SDK) in this help article: https://rider-support.jetbrains.com/hc/en-us/articles/360004180039 |
I disagree. Even if you identified what dotnetCore versions are compatible with what mono versions, it's not acceptable that both versions that are considered stable at this moment are incompatible (preview being incompatible with stable would be more understandable). |
@AndreyAkinshin: I've now also entirely removed the HtmlAgilityPack nuget package, and added it as netstandard 2.0 project, but the problem persists now. Hmmm, somehow, it seems like the project file is screwed up now. Hmm, it's not that either. |
@AndreyAkinshin: Why can this setting not be set on a per-project base ? |
kUbuntu, 19.04 (disco dingo) It might have something todo with that /usr/lib/mono/msbuild contains subfolders like 15.0 That is, assuming Rider's autodetect lists folders and expects numbers to auto-detect.
Ah, I see. Anyway, for the moment I'm satisfied if I can manually change that per solution. |
@ststeiger thanks for the feedback! I created the corresponding issue: https://youtrack.jetbrains.com/issue/RIDER-30143 |
@AndreyAkinshin I am having the same issue on Rider 2019.2 on OSX while having Mono 6.0 (rider auto detects msbuild 15 as latest). I also get the same build error while using msbuild 16 in command line. |
just installed latest .Net Core SDK (v2.2.402) and build succeeds. Note that If also want to build .net framework with Rider, need to use MSBuild version 15, and not 16, as it throws compile errors. |
I had .net standard project built on .net standard 2.0. Yesterday I updated my Visual Studio 2019 to 16.3.0 to leverage .Net Core 3.0. But all of sudden build of project targeting on standard 2.0 started throwing "GenerateDepsFile" task failed unexpectedly error. I was able to resolve this issue by changing the target framework to 2.1. |
Heave same error and find -" C:\Microsoft\Xamarin" folder has changed security rules and i heave no right to this folder. Change rights and all works ! |
Issue Title
after update to .net core 2.1.602, the following error occurs:
nothing worked on my system after the .net core - update last night
even the projects targeting the mono / .net framework dont't't compile any more - all with the same error.
i completely removed all .net-core runtimes, sdks etc., deleted the directories manually (of course, uninstalling the .net core stuff left some slack everywhere), did: nuget locals all -clear
removed all references to .net-core projects in my solution
and now i can work at least with projects targeting mono/.net framework again.
what a mess!!!!!
see also:
#2460 (comment)
#2460 (comment)
General
dotnet --info
.NET Core SDK (gemäß "global.json"):
Version: 2.1.602
Commit: 04475eb7cf
Laufzeitumgebung:
OS Name: ubuntu
OS Version: 18.04
OS Platform: Linux
RID: ubuntu.18.04-x64
Base Path: /usr/share/dotnet/sdk/2.1.602/
Host (useful for support):
Version: 2.1.9
Commit: dcedc87d22
.NET Core SDKs installed:
2.1.602 [/usr/share/dotnet/sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.9 [/usr/share/dotnet/shared/Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.9 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.1.9 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
mono --version
Mono JIT compiler version 5.18.1.0 (tarball Fri Mar 15 20:41:32 UTC 2019)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
TLS: __thread
SIGSEGV: altstack
Notifications: epoll
Architecture: amd64
Disabled: none
Misc: softdebug
Interpreter: yes
LLVM: yes(600)
Suspend: preemptive
GC: sgen (concurrent by default)
=== MonoDevelop ===
Version 7.7 (build 1869)
Installation UUID: bde482dd-6fcb-4a4d-9bcc-e49461c3ecfe
GTK+ 2.24.32 (Adwaita theme)
=== Mono Framework MDK ===
Runtime:
Mono 5.18.1.0 (tarball Fri Mar 15 20:41:32 UTC 2019) (64-bit)
=== NuGet ===
Version: 4.7.0.5148
=== Build Information ===
Release ID: 707001869
Git revision: f0f3d1d931d44682f076dde486ecec835f705b8d
Build date: 2018-11-29 14:54:14-05
The text was updated successfully, but these errors were encountered: