This time, we’re taking a look at an annoying situation where your previous debugging session, or perhaps your dotnet serve, somehow locks-up your dlls or other important files that you kind of need to overwrite when rebuilding. And that, well, causes your build or debugging session to fail. So, let’s take a closer look at the actual errors we’ve run ourselves into! Problem Build complains about retrying something and failing afterward, and something like this is either in the console or in your build output…Continue reading How to kill the process causing the “MSB3021 Unable to copy file — The process cannot access the file because it is being used by another process.” error?
This post describes the easiest way to debug the issues that may stop your Seed-method in Configuration.cs from going through. This problem concerns typically your ASP.NET MVC projects, either on .NET Framework or .NET Core – the same basic idea should work for both situations. The solution here shows you, how you can get a little bit more information out of the process, without attaching the debugger (there’s another blog post for that: How to launch the visual studio debugger from code/) Description Entity Framework’s…Continue reading Easiest way to debug Seed-method in Code-first migrations in Entity Framework
This post describes a quick solution to launching a new Visual Studio instance for debugging the code. There are a lot of applications for this, but where I’ve found it exceptionally useful, has been in debugging the Entity Framework’s code-first migration (one of the ways for database initialization) Seed-method. It is by default undebuggable, as when you are running Update-Database you can’t really use a -debug switch or anything, and there’s really no way to launch the debugger. Hence the best you can do is…Continue reading Launching a new debugger instance from code in Visual Studio
Every now and then comes the time when you’d actually need to debug something, and then you’ll likely be using your Visual Studio to attach the debugger to one or more processes. Using CKSDev to attach to all IIS worker processes (w3wp.exe), or if you don’t use CKSDev, just pressing ctrl+p and selecting the processes from the list, is often a good enough solution. However, sometimes that makes your dev box sluggish, or maybe catches exceptions from code you’re not wishing to debug at the…Continue reading Attaching the Visual Studio debugger to the right IIS worker process