Recently whilst working on a C# solution in Visual Studio 2022, I encountered an unusual issue whereby VS would fail to build my project according to the build log, however, VS did not report any errors in the “Error List” panel.
If you too have encountered the same error, then you are in luck, because I’ll explain the solution that worked for me.
Recently whilst trying to enable GitHub CoPilot within VSCode in a corporate enterprise environment, I encountered the following warning when trying to authenticate with GitHub:
[certificates] failed to read root certificates
Often in a corporate enterprise IT environment, IT will install a self-signed root certificate, which all devices must trust before they can access the internet via a central proxy server. This was indeed the case in my situation. However, the above error message indicated that VS Code didn’t recognise or trust this self-signed certificate, preventing it from properly authenticating with GitHub.
Recently, whilst trying to run the following command in a GitHub Actions workflow script to create a new Release in my GitHub Repository:
gh release create XXXX --generate-notesHowever, strangely I encountered the following workflow error:
HTTP 403: Resource not accessible by integrationIf you’ve faced the same error, then you’re in luck – because I’ll be sharing the solution that worked for me to resolve this issue.
Continue readingRecently whilst using Cmder on Windows 11, I encountered the below error while running command ‘ls’ to list the files, and in this post I’ll explain the solution that worked for me.
‘ls’ is not recognized as an internal or external command, operable program or batch file.
Whilst recently installing Specflow on a new Windows PC, I ran into an unexpected error after running the below command:
dotnet tool install --global SpecFlow.Plus.License --version 3.9.7This is the error I encountered whilst running the above command:
C:\Users\XXXX\AppData\Local\Temp\cd1e38b3-c92a-436d-b439-f1535d848adc\restore.csproj : error NU1101: Unable to find package specflow.plus.license. No packages exist with this id in source(s): C:\Program Files\dotnet\library-packs, Microsoft Visual Studio Offline Packages The tool package could not be restored.
Tool ‘specflow.plus.license’ failed to install. This failure may have been caused by:
You are attempting to install a preview release and did not use the –version option to specify the version.
A package by this name was found, but it was not a .NET tool.
The required NuGet feed cannot be accessed, perhaps because of an Internet connection problem.
You mistyped the name of the tool.
For more reasons, including package naming enforcement, visit https://aka.ms/failure-installing-tool
You may have come across situations where you need to identify duplicate lines contained in a text file. I recently had to do this within a large CSV data extract file.
While there are several ways to do this, I was specifically looking for a way to do this using Notepad++, which I already had installed. So in this blog article, I’ll show you how to find duplicate lines using Notepad++.
The ‘dotnet ef’ CLI command enables developers to work with Entity Framework Core (EF Core) database operations from the standard dotnet command line.
Recently I came across the below error whilst trying to run the ‘dotnet ef’ CLI commands:
$ dotnet ef
Could not execute because the specified command or file was not found.
Possible reasons for this include:
* You misspelled a built-in dotnet command.
* You intended to execute a .NET program, but dotnet-ef does not exist.
* You intended to run a global tool, but a dotnet-prefixed executable with this name could not be found on the PATH.If you have also encountered this error whilst using the Entity Framework commands via the dotnet CLI, then you’re in luck because I’ll be sharing the fix in this article.
Continue readingHave you ever found yourself in a situation where you’ve modified a local code file and needed to revert back to a previously saved local version that was not committed to your Git repo?
If you’re a user of Visual Studio Code you’re in luck because I’ll show you how to do just that …
Moving from Windows 10 to Windows 11 was largely a painless experience for me however like any new major Windows release it has its share of interesting quirks however there was one particular quirk that I’ll show you how to fix in this post.
Windows 11 by default will show a slimmed-down Windows Explorer context menu, with an option to expand the menu to “Show more options”. While at first, I did welcome the change, over time it became a bit of an annoyance and a real productivity killer because it meant I had to perform an extra click for no tangible benefit.
In this post, I’ll show you how to disable the “Show more options” feature of Windows 11.
Recently I came across an unusual issue where Google Drive was continually getting stuck uploading files on my Android Samsung Galaxy S20 smartphone device.
In this article, I’ll share the solution that worked for me, plus other possible solutions.
© 2024 Shane Bartholomeusz
Theme by Anders Noren — Up ↑