2 ms·

Despite the down votes I stand by what I said. I would be far more impressed with a stable version of vs 2013 than a preview of 2014. There are too many glitc

Despite the down votes I stand by what I said. I would be far more impressed with a stable version of vs 2013 than a preview of 2014. There are too many glitches to document here, but I am using it every day and constantly finding bugs, some of which I have reported via Connect, some I can't be bothered with.

frozenport 12y ago
I tried to up-vote, but I think the folks from MS are getting home. I got the same problem, and it killed my migration plans and inheriting constructors.
- adamconroy 12y ago
  Thank you. And don't get me started on vs2013 update 2. I wasted a day putting up with it but eventually had to uninstall out of frustration. After that experience I can't see myself ever installing update 2 unless there is a showstopper bug in update 1.
  - cpayne 12y ago
    What's your dev environment? If I've ever had a problem with Visual Studio it always is some type of add-on. I've been using it for years and have never had a problem.
WorldWideWayne 12y ago
You deserve the down votes because all you've added is emotion with zero content. Why haven't you mentioned a single specific bug? If there are too many, tell us about the ones that you think are show-stoppers.
- adamconroy 12y ago
  I don't have much time, but firstly : http://connect.microsoft.com/VisualStudio/feedback/details/800178/cannot-load-mymodel-edmx-specified-cast-is-not-valid-when-clicking-edmx-file-in-project http://connect.microsoft.com/VisualStudio/feedback/details/8... 2. I use ctl-shift-f a lot where I double click the matches and it takes you to the code windows. That always stops working after a few hours. 3. Web service in a solution no longer spin up automatically. I have to start them manually everytime I open VS. Combined with point 2 is extra annoyance. 4. Connecting to Azure via Server Explorer -> Windows Azure -> Connect to Windows Azure requires me to first go do some other random thing otherwise I get a non-nondescript 'network error' 5. I upgraded to update 2 and it quietly turned a number of crucial references to 'Copy local = false', which didn't stop the app working on my machine because I had the sdk installed of the relevant library, it only broke on test machines. 6. Not that I use it much, but yesterday I noticed the WPF designer randomly stops me from changing simple properties such as margins. It works for some properties and not the others.
- deleted 12y ago
  [deleted]

frozenport 12y ago

I tried to up-vote, but I think the folks from MS are getting home. I got the same problem, and it killed my migration plans and inheriting constructors.

adamconroy 12y ago
Thank you. And don't get me started on vs2013 update 2. I wasted a day putting up with it but eventually had to uninstall out of frustration. After that experience I can't see myself ever installing update 2 unless there is a showstopper bug in update 1.
- cpayne 12y ago
  What's your dev environment? If I've ever had a problem with Visual Studio it always is some type of add-on. I've been using it for years and have never had a problem.

WorldWideWayne 12y ago

You deserve the down votes because all you've added is emotion with zero content. Why haven't you mentioned a single specific bug? If there are too many, tell us about the ones that you think are show-stoppers.

adamconroy 12y ago
I don't have much time, but firstly : http://connect.microsoft.com/VisualStudio/feedback/details/800178/cannot-load-mymodel-edmx-specified-cast-is-not-valid-when-clicking-edmx-file-in-project http://connect.microsoft.com/VisualStudio/feedback/details/8... 2. I use ctl-shift-f a lot where I double click the matches and it takes you to the code windows. That always stops working after a few hours. 3. Web service in a solution no longer spin up automatically. I have to start them manually everytime I open VS. Combined with point 2 is extra annoyance. 4. Connecting to Azure via Server Explorer -> Windows Azure -> Connect to Windows Azure requires me to first go do some other random thing otherwise I get a non-nondescript 'network error' 5. I upgraded to update 2 and it quietly turned a number of crucial references to 'Copy local = false', which didn't stop the app working on my machine because I had the sdk installed of the relevant library, it only broke on test machines. 6. Not that I use it much, but yesterday I noticed the WPF designer randomly stops me from changing simple properties such as margins. It works for some properties and not the others.
deleted 12y ago
[deleted]