microsoft visual studio 2017 how to change target drive

This isn't just important to me personally, but I think this is a vital requirement for moving much of the support libraries that exist for. NET Core 2.0 it really looks like most code will migrate pretty easily. Nobody wants to rewrite code they already have just to get back to square one, but with.

NET Core is actually pretty important factor to overcoming my reluctance to move into. Being able to bring some of the tools I use to be productive over to. NET Core really has been a deciding factor for me to start moving some of my existing full framework libraries that I've been using for as long as I have been using. NET Core 2.0 with their much bigger base library foot print and the real possibility of porting the majority of existing library code over to. In fact, to date I have yet to build anything 'real' for customers beyond a few internal infrastructure projects and quite a few sample applications.įor me personally. NET Core have been on my mind for a long time now - years really, but the reality is while I've been using the technology quite a bit, I've not jumped in with both feet.

Microsoft visual studio 2017 how to change target drive