vasuphq.blogg.se

1. #Visual studio remote debugging web application software
2. #Visual studio remote debugging web application code

NET framework project, but you're like me and have started to appreciate a simpler environment that you can get just about everything done in without having much in the way of features that are adding what feels like clutter when you don't need them. The assumption underpinning this blog is you have on hand some. It's no doubt installed on your machine already, because who doesn't have Visual Studio if you're working with Framework. Which is where we get to some of your BYO tooling. What they don't tell you on the back of the box, is that it is actually possible to run and work with.

#Visual studio remote debugging web application code

However, support for C# in VS Code is pretty much dedicated exclusively for. I think both serve their purpose in my workflow. I develop using both, but my "Daily Driver" as it were is VS Code. It's a simpler concept, and you're not inundated with hundreds of features that you're just not going to need all that often. This means most of your tools will be BYO. A very fancy, extremely powerful, super feature reach text editor that blurs the line between text editor and IDE, but still, a text editor.

#Visual studio remote debugging web application software

It's something that combines a lot of tools into one, super dense software package. Actually, maybe we mostly just think about text, but that's another topic. As a developer, we mostly edit text, that's it. However, there's a fundamental difference in purpose that makes me prefer VS Code, at least for most of what I do on the daily. But seriously, there are lots of reasons to love Visual Studio, especially with the Community option available as that version is an extremely robust environment.