-
Notifications
You must be signed in to change notification settings - Fork 654
ArgumentNullException in node issue with beta0014 #1458
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
Comments
I'm getting the same problem:
|
This happens as soon as I build for more than one target framework, i.e. if I have a line like |
@asbjornu ideas? |
Hm, no. This makes no sense to me. |
Are you compiling against .net SDK 2.1.401 while having 2.1.400 installed? |
I don't think .NET SDK is the problem. Same thing happens after I installed 2.1.401. I created a minimal solution to repro: https://gist.github.com/ermshiperete/fd8baae02180f2156dc0c5bbf166b29d Interestingly, it works when I build from the command line (in a VS2017 command line: The output of both a failed build from within VS2017, and a successful build from the command line can be seen in this gist: https://gist.github.com/ermshiperete/9b951afbc340686951610459e7c64608 |
Does this work if you add a global.json locking sdk version to 2.0.0 |
Sorry, I have since spotted your PR #1459 |
I have repro this where I'm going to see if I can repro this with VS 15.7 |
I uninstalled VS2017 15.8.2 and installed VS2017 15.7.6 from here: https://docs.microsoft.com/en-us/visualstudio/productinfo/installing-an-earlier-release-of-vs2017 After that I was able to build fine from VS2017. So it seems to me that the VS Update to 15.8.X broke something. Update: I did the same thing on aanother machine (downgraded from 15.8.1 to 15.7.6) and the issue still repros in 15.7.6.. So now I am confused. |
Had confirmation over here: #1399 (comment) from someone successfully building from VS2017 15.8.1. So I am now wondering if this is just a VS2017 15.8.2 issue. |
For me it's failing with VS2017 community 15.8.1. Note that you'll have to look at the "Output" tab to see the failure - the "Error List" tab won't show anything in this case. |
A
|
@ermshiperete this is weird. As per #1399 (comment) this user is also using 15.8.1 and says everything is working fine. Im wondering what the difference is between their build environment and yours. Or perhaps they didnt check the output tab like you said. |
@ermshiperete can you delete gitversion from your local nuget cache to force redownload. I can see that ' |
That was with beta14. But with beta15 I get the same result. |
@ermshiperete I rolled back to 15.7.6 (on another machine since yesterday) and this time it still repros using the beta15 package. However when I rolled the package version back from beta0015 to beta0014 (and killed msbuild.exe) - then unloaded / reloaded the project and rebuilt - it works. Here is my csproj:
I then upgraded VS to 15.8.2 and built again. After the upgrade, both the beta14 and beta15 packages have the same error. |
Did another downgrade to vs2017 15.7.6. Now, all of the packages are working fine (beta14, beta15, and my netstandard PR one) and I am unable to repro the issue at all. |
We had some help, see the linked msbuild issue - just need to try the workaround suggested there. |
This should now be fixed in #1470 |
fixes #1458 - msbuild null ref issue
Tested the new beta0014 version and got the following error message while building a .net standard library after adding the package. It compiles with the beta0012 version tho.
1>------ Neues Erstellen gestartet: Projekt: TestProject, Konfiguration: Debug Any CPU ------ 1>[NuGet Minimal]: Restoring packages for C:\Users\li0nsar3c00l\AppData\Local\Temp\0vdgm03o.fg3\dummy... 1>MSBUILD : error MSB4166: Der untergeordnete Knoten "2" wurde vorzeitig beendet. Vorgang zum Herunterfahren wird durchgeführt. Diagnoseinformationen finden Sie in den Dateien namens "MSBuild_*.failure.txt" unter "C:\Users\li0nsar3c00l\AppData\Local\Temp\". Dieser Speicherort kann geändert werden, indem Sie die Umgebungsvariable MSBUILDDEBUGPATH auf ein anderes Verzeichnis festlegen. ========== Alles neu erstellen: 0 erfolgreich, 1 fehlerhaft, 0 übersprungen ==========
Content of the referred file:
Any ideas?
The text was updated successfully, but these errors were encountered: