![visual studio extensions add file visual studio extensions add file](https://nordiccoder.com/app/uploads/2020/07/show-popular-extensions.png)
You have to specify the right XML in the vsct file of the project: Turns out that adding keybindings are pretty easy.
Visual studio extensions add file full#
You can check out the full source on Github - here's the gist of what I have learnt with this project: Adding keybindings I already have some extensions in the Visual Studio marketplace (and I have a couple more coming the next few weeks, so stay tuned), so I was familiar with most of the API. Should display the deleted folders or any error messages in the "General" pane of the output window.The one for the projects probably won't be used that often, I let that go. The one for the solution should have a key binding.Should add a new option to delete the bin and obj folders of every project and the packages folder of the solution to the solution context menu.Should add a new option to delete the bin and obj folders of projects for the project context menu.So here are my key points for the extension: But if you are interested what I have actually created and the most important points of how, read on.
Visual studio extensions add file download#
You can go ahead and download it from the marketplace or check out the Github repo for the source. So I came up with my own implementation as a fun weekend-project. I wanted to have something as a context menu option for my solution and my projects. This one and this one are kinda good, but I'm not sure if they have keybindings set up and I also don't want to have a menu option, it's hard enough to find anything in the menus as they are.I just wanted something simple that deletes the unnecessary build outputs. But to be honest, this is a bit too much for me. This one by Mads Kristensen is (like everything else by Mads Kristensen) is super awesome.Unfortunately, I didn't like most of them: That is, it doesn't delete the bin and obj folders.Īnd he was entirely right, and he was not alone with his frustration, so there are extensions in the marketplace to solve this problem. During one of my C#-.NET courses, one of the participants was complaining how the "Clean solution" option of Visual Studio doesn't actually clean the solution.