![]() We are basically going to be using it just to pull in packages currently configured for the project. I will have some details on how to use the Nuget CLI, but that is a deep topic that if there's enough interest in I will tackle later. In fact, generally speaking if you're trying to work on a Framework project, a lot of what you would need the Nuget Package Manager for is already done. It's not a deal breaker for many, but for some, it's not for you and that's fine. It's not a dealbreaker for me, and I'm going to try to find some ways around that, but these are just not going to be things you have Visual Studio hold your hand through. sln files or manually managing your NuGet packages you are. And whether or not they're dealbreakers for you will really depend on how into working with. If you get stuck, I've got the basic working version up on Git, don't worry about what the application, it's basically just a stubbed out project from one of Visual Studio's templates. 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. ![]() 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. 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. ![]()
0 Comments
Leave a Reply. |