Needs for vim-ming

I've been playing around with ideas in my head. Crazy stuff. Linux... vim...

DHH is mostly to thank/blame, but he's not the sole influence.

Vim sounds super cool, especially relative to the way I like to work: ultra-lean, intentional, simple, hard.

It has a sexy hacker allure. Raw. Elite. Exclusive. Everything in the terminal. Low memory and CPU footprint.

However, I'm a dotnet guy. Visual Studio is the single greatest piece of software ever built by Microsoft, and one of the greatest pieces of software to ever exist. If I switched to Vim, what would I be giving up?

What would make it worth it?

These are the things I use in VS often:

• Debugging
• Intellisense
• Tests (especially NCrunch real-time tests)
• Refactoring tools (especially renaming, but also extract method and occasionally extract interface or file)
• Code snippets
• File and Solution explorer (obviously)
• Red and green squiggles for errors and warnings
• Autoformat and other quick actions via Ctrl+.

But that's probably it.

What would I need in Vim to make it worth switching? Keeping in mine that the experience in Vim should be different to a degree, especially seeking greater simplicity and focus on intentionality.

This might be a flow:

• File explorer (can forgo solution explorer)
• Auto test runner in another pane
• Intellisense is a must
• Debugger feels essential, but could maybe be below essential priorities
• Refactoring and code snippets should be reproducible via plugins, third party or custom
• Error and warning highlighting could be handled by linting plugins and build messages
• Theoretically, same for autoformatting (do we have things that already hook into .editorconfig files?)

So the big question marks are the following: debugging, intellisense, and auto test runner.

Anybody know good setups for these?