The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
7 March: A great day. Everyone in the company i'm currently working for, was happy as they released a new Visual Studio. The great tool that is our daily bread and we are working with some years for now, the announced pretty cool features like the Xaml Edit and Continue ( my personal favorite ), continues testing, a new setup they even included the redgate tools for SQL devloper, that made our sql guy very happy because they can now show everyone why he need that licence Smile | . The IT said that we should not install it to break anything, i know they are right but who cares in the worst case we have to uninstall it.
9 March: I just tested the Xaml E-C feature and its very cool, it makes small changes much more easy. But after i installed i saw more then just the redgate tools installed on my machine like Incredibuild. The TSVN is now always active and shows its menus all the time even when no source control is installed. A bit annoying, both. As i forgot to check the Continues testing feature is just in the enterprise edition, not even for professionals. Good what ever, i have to switch back to my Resharper-DotCover.
10 March: I am at home and loading my Personal-Webpage where i present myself as an Freelancer. VS now talks to Chrome which is AWESOME and i have to admit i tried to bring VS and Chrome to some time ago but failed miserable. Unfortunately i soon understood that the feature is not fully ... lets say sophisticated, its very very laggy and missing some good tools to explore the DOM properly, yes i am aware of the VS DOM explorer ( Debug -> Windows -> Dom Explorer ) but its just not the same as the Chrome debugger. Also it pushes the Starttime of my asp.net application from 4-6 seconds to 10-15, thats just not worth it.
13 March - Today: I am completely pissed of. One of my C# open source projects used file Links a LOT to have an shared code base. The simply forgot! to implement "Add as Link" and when I have opened the project in VS17 i had to upgrade it, now its not even possible to load it in VS15 and i have to dig through the xproj file the revert the changes to work on it! not cool.
Later that same day - Now: my Personal Webpage is a mess. Every time i refresh my Webpage in Chrome, VS lags and Freezes, every time i restart the project it takes 20 seconds to start it, every time i click inside VS from chrome it lags, from my point of view it lags more then it works, even my whole pc is now lagging when debugging the asp project. This is unacceptable. And of course i have to submit that with that tiny button right next to the quick launch ... i did so and tried to record that behavior, but as i did so and started the integrated recording everything went worse! my pc was barley responding i just manged to click on the stop button, as i did so and the data was collected most of my pc froze for 30! minutes! i just let the collector do his thing and after that it was not even possible to SEE what i am Transmitting to MS! that's a NO GO! You want me to help you and collect EVERYTHING from my pc ok but then just let me see what i am giving to you!
For my opinion i will uninstall VS2017 tomorrow and wait for the SP 1. For now, VS is just another Release Candidate.
#SupportHeForShe Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
The "funny" thing was i did not download any RC, i wanted a full VS to use ... i simply did not expected ... that there are a LOT posts down the internet that are full of this opinions, for WPF they made good improvements but with asp it was just a step in the wrong direction ... but take it with a smile, this has to happen some time^^
I seem to have more issues with the final version than I had with RC. Maybe you should go into reverse and try the RC version? Nothing too serious with the final version, but for one it will spontaneously decide that I don't need both the design window and the XAML code window, when I look at XAML files. I suddenly only get the design window or the code window, but not both. In one or two instances I had to restart VS to even get the ability to show both windows at the same time.