Nuget Hell. Again.
-
Uninstalled old version: Check. Cleared all nuget caches and temp folders: Check. Installed new version: Check Clean and build the project: Check, no errors. Run the app: blows up when calling the package, no error caught, no warnings, nothing written to App Insights, nothing useful in Event Viewer. Argh!
If you think 'goto' is evil, try writing an Assembly program without JMP.
-
Uninstalled old version: Check. Cleared all nuget caches and temp folders: Check. Installed new version: Check Clean and build the project: Check, no errors. Run the app: blows up when calling the package, no error caught, no warnings, nothing written to App Insights, nothing useful in Event Viewer. Argh!
If you think 'goto' is evil, try writing an Assembly program without JMP.
fuslogvw (fusion* log viewer) may help you. Open your Visual Studio Developer command prompt as admin.
c:\dev>fuslogvw
This will start an app which can tell you which assembly is failing to bind. NOTE: Make sure you turn it off afterwards because their is s heavy penalty for leaving it running See Fuslogvw.exe (Assembly Binding Log Viewer) - .NET Framework | Microsoft Docs[^] for details. And, oh yeah, it ain't a pretty tool, but it can help you where nothing else can in these situations. *Fusion was the original code name for .NET Framework
-
fuslogvw (fusion* log viewer) may help you. Open your Visual Studio Developer command prompt as admin.
c:\dev>fuslogvw
This will start an app which can tell you which assembly is failing to bind. NOTE: Make sure you turn it off afterwards because their is s heavy penalty for leaving it running See Fuslogvw.exe (Assembly Binding Log Viewer) - .NET Framework | Microsoft Docs[^] for details. And, oh yeah, it ain't a pretty tool, but it can help you where nothing else can in these situations. *Fusion was the original code name for .NET Framework
Odd. It is filled with multiple entries like: LOG: Attempting download of new URL file:///C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/MSBuild/Current/Bin/NuGet.Frameworks/NuGet.Frameworks.EXE. But also for a gazillion Microsoft DLLs like C:/Users//AppData/Local/Programs/Microsoft Azure Storage Explorer/resources/app/ServiceHub/MSAL-Services/IdentityService/Microsoft.VisualStudio.Telemetry.DLL And each group is followed by: LOG: All probing URLs attempted and failed. I see nothing related to the package I'm having issues with.
If you think 'goto' is evil, try writing an Assembly program without JMP.
-
Odd. It is filled with multiple entries like: LOG: Attempting download of new URL file:///C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/MSBuild/Current/Bin/NuGet.Frameworks/NuGet.Frameworks.EXE. But also for a gazillion Microsoft DLLs like C:/Users//AppData/Local/Programs/Microsoft Azure Storage Explorer/resources/app/ServiceHub/MSAL-Services/IdentityService/Microsoft.VisualStudio.Telemetry.DLL And each group is followed by: LOG: All probing URLs attempted and failed. I see nothing related to the package I'm having issues with.
If you think 'goto' is evil, try writing an Assembly program without JMP.
what are you going to do then? what are your options?
-
Uninstalled old version: Check. Cleared all nuget caches and temp folders: Check. Installed new version: Check Clean and build the project: Check, no errors. Run the app: blows up when calling the package, no error caught, no warnings, nothing written to App Insights, nothing useful in Event Viewer. Argh!
If you think 'goto' is evil, try writing an Assembly program without JMP.
I have never had any issue with NuGet that I was not able to resolve. I hope you find a way to resolve your issues. :thumbsup:
-
Odd. It is filled with multiple entries like: LOG: Attempting download of new URL file:///C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/MSBuild/Current/Bin/NuGet.Frameworks/NuGet.Frameworks.EXE. But also for a gazillion Microsoft DLLs like C:/Users//AppData/Local/Programs/Microsoft Azure Storage Explorer/resources/app/ServiceHub/MSAL-Services/IdentityService/Microsoft.VisualStudio.Telemetry.DLL And each group is followed by: LOG: All probing URLs attempted and failed. I see nothing related to the package I'm having issues with.
If you think 'goto' is evil, try writing an Assembly program without JMP.
Yeah the tool is quite cryptic. There should be a way to set it to only track a specific exe. Also try clearing it then only running the target app and you may see it more clearly. It’s weird how you start & stop it also. It’s kinda terrible but once you get it, it should be clear.
-
what are you going to do then? what are your options?
-
Yeah the tool is quite cryptic. There should be a way to set it to only track a specific exe. Also try clearing it then only running the target app and you may see it more clearly. It’s weird how you start & stop it also. It’s kinda terrible but once you get it, it should be clear.
That, and it seems to log everything, even when nothing is running. And you can't make the window bigger or do a search. Obviously the tool is something someone threw together with minimal effort and they never used it again.
If you think 'goto' is evil, try writing an Assembly program without JMP.
-
I have never had any issue with NuGet that I was not able to resolve. I hope you find a way to resolve your issues. :thumbsup:
I've been able to resolve two issues before, but this one is causing all kinds of strange behavior, such as Visual Studio suddenly insisting that
Microsoft.Azure.WebJobswas not installed and/or referenced when it most certainly was, or at least NuGet insists it was installed. Then after a half hour of searching for a solution and handling unrelated issues I come back and VS is all happy again, it concedes thatWebJobsis indeed there. But the other package still fails. :wtf: Any hints you can give me? What actions do you take to resolve NuGet problems?If you think 'goto' is evil, try writing an Assembly program without JMP.
-
That, and it seems to log everything, even when nothing is running. And you can't make the window bigger or do a search. Obviously the tool is something someone threw together with minimal effort and they never used it again.
If you think 'goto' is evil, try writing an Assembly program without JMP.
-
Yeah, it's ugly & probably from 2002 and it's a tough nut to crack. But if you get it right, it should show you the missing assembly. HOpefully.
I suspect there is no missing assembly, in spite of the myriad "All probing URLs attempted and failed." messages. The package runs, but causes the app to exit when it attempts to execute one of the package's main functions. No errors, no log entries, no event logs, just exits from Debug mode.
If you think 'goto' is evil, try writing an Assembly program without JMP.