Centralized Package Management is a NuGet feature that allows you to manage NuGet package dependencies for multiple projects from a single location. This is particularly useful for large solutions with many projects, as it simplifies the process of keeping package versions consistent across the entire solution. After enabling Central Package Management for an existing solution and committing those changes, one of our build pipelines started to fail. When we took a look at the logs we encountered the following error message: ##[error]The nuget command failed with exit code(1) and error(NU1008: Projects that use central package version management should not define the version on the PackageReference items but on the PackageVersion items: Dapper;Microsoft.Data.SqlClient;Microsoft.Extensions.Configuration;Microsoft.Extensions.Configuration.Binder;Microsoft.Extensions.Configuration.Json;Microsoft.Extensions.Http;Spectre.Console;Spectre.Console.Json. What is happening? The reason we...
After writing a post about the GitHub Copilot code review feature in Visual Studio last week, I got a question if the same functionality was available in VSCode. Hence this post to show you how to use this feature in VSCode as well. Before you can use this feature, make sure that Editor preview features are enabled in your GitHub settings: Review changes Reviewing your changes works quite similar to Visual Studio: Go to the Source Control tab in VSCode. Hover over Source Control in the sidebar, and then click on the Copilot code review – Uncommited Changes button: Copilot will now review your changes (this can taken some time so be patient). When it has comments, they are shown inline in the file: When no remarks are found during review, you get a pop up message. You can also see the comments in the Problems tab: Remark: Although this is a nice new feature, I had some mixed results when applying it. Sometimes it gave very good feedback, but o...