This situation occurred to me after opening an existing solution but instead of Warnings, they were Errors. I opened the YourAwesomeApp.csproj file and went through the “Detected package downgrade” errors one-by-one and manually changed the version of that line item from the existing version to the specified version that was shown in the error itself. … Read more
I Just ran through this page on Roslyn which describes the following steps to get this working: Start a C# project Add a reference to the System.ValueTuple package from NuGet (pre-release) Following those steps, it is now working. But it is really very weird that we need to do that for every single project that … Read more
The problem was that I had some other normal error messages in my project, and apparently after I fixed those and when I cleaned and built my project AGAIN, then all .dlls succeeded. Make sure you don’t have any other error messages in your project and if you do, fix those first!
To get all packages from all projects in the solution use Get-Package. To get all packages from a specific project use Get-Package -ProjectName “YourProjectName”. Remove all packages from all projects in the solution Be careful: This will uninstall ALL packages in the solution. If -Force parameter is used, packages are removed even if dependencies exist. … Read more
Its a new configurable feature, if you go to Tools → Options → Text Editor → Your language (I did C#) → Code Style → Naming In there I went to Manage Styles add camel Case (its in there but you need to add it to your selectable): go to the “+” sign, then add … Read more
I don’t know if there is a menu option, but there are keyboard shortcuts to set the zoom level. ctrl+shift+. to Zoom In ctrl+shift+, to Zoom Out
According to the Microsoft blog (which, bizarrely, my account doesn’t have permissions to post in), this isn’t a bug, and is entirely caused by ReSharper. If you disable this, the problem goes away. Errr, one problem: I’m getting this error, and I don’t have ReSharper. After a lot of hunting around, I found the reason … Read more
Visual Studio reads NuGet.Config files from the solution root. Try moving it there instead of placing it in the same folder as the project. You can also place the file at %appdata%\NuGet\NuGet.Config and it will be used everywhere. https://learn.microsoft.com/en-us/nuget/schema/nuget-config-file
Core issue 2313 changed the standard so that structured bindings are never names of variables, making them never capturable. P0588R1’s reformulation of lambda capture wording makes this prohibition explicit: If a lambda-expression […] captures a structured binding (explicitly or implicitly), the program is ill-formed. Note that this wording is supposedly a placeholder while the committee … Read more
It sounds like installing the VS2017 update for that specific version didn’t also install the .NET Core 2.0 SDK. You can download that here. To check which version of the SDK you’ve already got installed, run dotnet –info from the command line. Note that if there’s a global.json file in either your current working directory … Read more