I've honestly most ever only built Windows software from Makefiles and the like. So basically ports of Linux stuff. And then I just edit with vi or whatever.
Some video game mods have come as VS projects, and I open them on Windows, but I ended up editing the xml manually anyways to make the build-test-debug cycle work.
Visual Studio project files and solutions are easy and work great, until they don't. Everyone I know that develops on Windows eventually has to go and tweak those xml files when something automagical did the auto part but not the magic part.
XML make files / dependency trees are a good way to do it. IDK if Microsoft thought of that. I haven't spent a lot of time on build systems, other than simple make and VS, though I have used the systems that people have already setup for a project. Usually I just hope it works, and I don't have to mess with it too much.
But yeah when you end up dumping xcopy commands in your XML files, which is what I had to do, something isn't working ideally.
Yeah, and nothing ever goes wrong with makefiles, CMake, or Gradle setups.
I'm talking about features like built-in profiling, extremely flexible memory inspection, edit-and-continue, and .natvis customization just to name a few.
Visual Studio Code is not Visual Studio. It's not bad;
I disagree but that's because I'm an opinionated motherfucker who's tired of having idiot sysadmins tell me that Powershell ISE is deprecated as if that means it isn't still the superior environment in which to write my code when VSCode keeps sperging out on me every time I try to use it whereas ISE has always just fucking worked without requiring any coaxing or configuration.
And yes I am stubborn and mad enough about this that I have managed to make Powershell 7 work with ISE because goddammit it's my preferred environment but that doesn't even matter because Powershell 5 does everything I need.
Visual Studio is nice though. I need to get back to brushing up on my C# one of these days so I can make the jump to more dev focused work.
Visual Studio Code is not Visual Studio. It's not bad; I use it almost daily for non-C++ projects, but it's not Visual Studio.
Yep. Visual Studio has way more functionality than VSC can provide. Nearest Visual Studio replacement would be jetbrains Rider
I've honestly most ever only built Windows software from Makefiles and the like. So basically ports of Linux stuff. And then I just edit with vi or whatever.
Some video game mods have come as VS projects, and I open them on Windows, but I ended up editing the xml manually anyways to make the build-test-debug cycle work.
Visual Studio project files and solutions are easy and work great, until they don't. Everyone I know that develops on Windows eventually has to go and tweak those xml files when something automagical did the auto part but not the magic part.
XML make files / dependency trees are a good way to do it. IDK if Microsoft thought of that. I haven't spent a lot of time on build systems, other than simple make and VS, though I have used the systems that people have already setup for a project. Usually I just hope it works, and I don't have to mess with it too much.
But yeah when you end up dumping xcopy commands in your XML files, which is what I had to do, something isn't working ideally.
Yeah, and nothing ever goes wrong with makefiles, CMake, or Gradle setups.
I'm talking about features like built-in profiling, extremely flexible memory inspection, edit-and-continue, and .natvis customization just to name a few.
I disagree but that's because I'm an opinionated motherfucker who's tired of having idiot sysadmins tell me that Powershell ISE is deprecated as if that means it isn't still the superior environment in which to write my code when VSCode keeps sperging out on me every time I try to use it whereas ISE has always just fucking worked without requiring any coaxing or configuration.
And yes I am stubborn and mad enough about this that I have managed to make Powershell 7 work with ISE because goddammit it's my preferred environment but that doesn't even matter because Powershell 5 does everything I need.
Visual Studio is nice though. I need to get back to brushing up on my C# one of these days so I can make the jump to more dev focused work.