Getting DotNet Core on your computer – Part 1/3: Clean Environment

I’m almost impressed with how difficult of a time I’ve had with using DotNet Core on my windows machine.

I’m not a regular .NET developer, but I have built a number of different tools, functions, PoCs with C#.

While I’m at it, this is one of the main reasons I’ve struggled grokking .NET to help people. The versioning and naming convention issues. C# is an incredibly robust and articulate language, with an incredible diverse set of tools and services. Once your over the hurdles the potential to be productive at Common Enterprise Scale is supes appealing. But before that, I need to get the stuff working in a flexible manner on my computer because I work in many different environments.

Maybe I’m approaching it the wrong way, maybe I should create a VM and do all my work on that? Maybe I should reimage my computer everytime I start a new project? This seems rather silly though. The ability to build, debug, test, and release projects from your own computer seems like one of the compelling reasons to use C#. In some ways, it’s design aligns with the Operating System of windows. Most specifically .dll files. Learning .NET has been a slow process some of the books I’ve read include: “The Yellow Book of C#” and “Functional Programming in C#”. One of the things I struggle with is the stuff in between. I want to move beyond class declaration but not quite all the way into Functional Programming.

So… here I am wanting to learn more and many projects I’ve been working on include a Web components, so ASP.NET Core stand out to me right away. The tough thing here is that to practice writing production code you should design your projects and solutions in a way that optimizes for testing and deployment pipelines. Following best practices from the get go with C# is a bit tricky. So I found this course about testing with ASP.NET Core MVC Unit Testability.

Now I’m stoked to go through this content, but before I do I’d like my dev environment to be similar or at lease working int he same way as Benjamin Day, the author of this course.

Okay, so to begin, I have a couple versions of .NET installed on my computer. But I’m going to uninstall everything to start. I’m also going to uninstall VS Code and all extensions because things were acting weird there as well.

First I uninstalled VS code from the Apps and Features page of the settings in Windows 10!
Then, I found this post for uninstalling VS Code extensions:
And this one from Scott Hanselman for uninstalling Dotnet Core:
Then I went into my Apps and Features and uninstalled them again…
I even checked my paths, both User and System variables.
I’m also deleting “.omnisharp”, “.nuget”, “.vscode” from my user folders.

And then restart your computer, because that may have been the solution all along \__0__/

So, should have a nice clean environment

Okay have you done all that???
That should take an hour to make sure everything is gone…

Now let’s install dotnet core…

But first a photo:

Picasso’s got me inspired

Leave a Reply

Your email address will not be published. Required fields are marked *