search

TysonMN / tysonmn.github.io

Blog of Tyson Williams about software engineering and functional programming
https://tysonwilliams.coding.blog/
MIT License
3 stars 7 forks source link

2020-07-11_systematic_cleaning #4

Closed utterances-bot closed 4 years ago

utterances-bot commented 4 years ago

Systematic Cleaning

https://tysonwilliams.coding.blog/2020-07-11_systematic_cleaning

dharmaturtle commented 4 years ago

Sometimes my Intellisense gets corrupted and a git clean -fdx is the fastest way to get it working again. I think the "official" solution is to delete the .vs folder, but I'm too lazy to target it specifically. Delete all the things! For web developers, that command will also delete npm packages 'n stuff, so you'll need to npm install.

wendallmartin commented 4 years ago

Running git clean -fdx fixed a referencing problem I was having with my current project today. Thanks a lot for this helpful blog!

cmeeren commented 3 years ago

I have had head-scratching problems that require even more cleaning than the repo. It's easy once you know it, though: I have several times had corrupt packages in my NuGet cache, causing all kinds of weird compilation and runtime problems. Solution? Just delete %USERPROFILE%\.nuget\packages. (Assuming you use the global package cache; that is the default, after all.)

cmeeren commented 3 years ago

Example: https://github.com/dotnet/SqlClient/issues/801

(I wish it was possible to edit comments here)

TysonMN commented 3 years ago

I am glad you were able to solve that problem with your NuGet cache. Deleting that cache is indeed another good troubleshooting step. Thanks for sharing a specific example of where that helped you.

Only the first commenter on each post needs to authorize utterances and comment from the blog post. Everyone else also has the option to follow the link at the top of the comments that says how many there are and comment on GitHub, which of course supports comment editing. Many of the issues for utterances are of the form "Add ability to directly do X from the blog". I fully expect there to be an issue with X = "comment editing".