I had the preview installed, and I had really grown to love the navigation bar for Javascript.
After installing the professional edition from MSDN... my navigation bars are gone. WTF?
Visual Studio 2013 released to web
111–120 of 162 posts
Re: Visual Studio 2013 released to web
#112http://visualstudio.uservoice.com/forums/121579-visual-studi... Apparrently there is a requirement to have IE10 installed. Dealbreaker for many in the corp world. These should be developed independently.
we're still on Windows 7. On XP, until April.
Re: Visual Studio 2013 released to web
#113Earlier quoted context omitted.
> pander to web monkeys Really? How exactly does VS2012 pander to "web monkeys" at the expense of others?
It's not necessarily "monkeys", but, disturbingly, Microsoft developer tools are becoming more and more oriented towards "wizard-and-designer-clickety-clickery" type development. There are a few exceptions to this rule (think EF Code-First), but that's a drop in the ocean.
It's not necessarily "monkeys", but, disturbingly, Microsoft developer tools are becoming more and more oriented towards "wizard-and-designer-clickety-clickery" type development.
The term "wizard" came about because of the AppWizard and ClassWizard features in Visual C++.
Clickety-clickety has been a goal of Visual Studio since before it was Visual Studio.
Re: Visual Studio 2013 released to web
#114I got a free copy of 2010 by attending a launch event, and 2012 from the (now defunct) websitespark program. Anyone know of any freebies for 2013?
Re: Visual Studio 2013 released to web
#115I got a free copy of 2010 by attending a launch event, and 2012 from the (now defunct) websitespark program. Anyone know of any freebies for 2013?
one cool freebie imho is "PTVS-Integrated". it's VisualStudio 2013 + Python Tools bundled together. It's perpetually free.
link: http://pytools.codeplex.com
video overview: https://www.youtube.com/watch?v=JNNAOypc6Ek
(disclaimer, etc).
Re: Visual Studio 2013 released to web
#116Earlier quoted context omitted.
That's a great feature which will actually help avoid creating local bindings just to easily see the value.
You can also reference register values (e.g. rax) in quickwatch and cast them to the appropriate type.
and the fact that you've had to do that since I was using VC6 in 1995 is the indictment.
Re: Visual Studio 2013 released to web
#117Earlier quoted context omitted.
That's such a horrible practice I don't even. You're forcing yourself to stay on an older, potentially less maintained version of the OS so you don't "jinx it"?
I heard many complaints about SP1 slow starting and getting stuck in 'Shutting Down'. On top of that SP1 has zero new features. Bunch of so called security updates. From my perpective i'm using the stable version. If thing go awry i would need to waste a day or two reinstalling the OS again. It's very easy to resist installing this update.
Zero new features is not true. AVX support for newer processors is one new feature. But more importantly Win7 RTM support ended April 2013.
Re: Visual Studio 2013 released to web
#118And finally we should be able to see function return values in debugger: http://blogs.msdn.com/b/visualstudioalm/archive/2013/06/27/s...
You could see this in the Autos window in earlier versions, too. Although maybe only immediately after shift-F11'ing out of a function, and not of multiple levels of function calls like the linked article shows.
Re: Visual Studio 2013 released to web
#119In VS 2012 MSFT removed the color for the icons in the UI. Everybody complained on the web. Now the color icons are back. MSFT's spin: "Visual Studio 2013 includes many user interface improvements based on customer feedback and Microsoft’s core design principle of keeping the focus on the content to deliver an improved user experience. You may notice the more than 400 modified icons with greater differentiation and i…
Thanks for your uselessly dramatic comment.
Re: Visual Studio 2013 released to web
#120This rant has been brewing for many years... Everything's been downhill since VS6. I'm only joking, but seriously, does anyone remember how lightning fast VS6 was? That was over 15 years ago with much slower computers. I guess application 'snappiness' has not been a priority for the Visual Studio decision makers. I've used VS since the late 90s (writing node.js in ST2 now) and honestly appreciate the hard work and co…
Chromium is an extreme case of this. When we started we wanted to live the VS way of life (IDE tools and the like), so we had a Chrome.sln and various projects. Eventually it became too much. It would take minutes to load the sln, and woe to you if you synced your source tree while msvs was open, as you'd receive a neverending slew of modal prompts asking you to reload each of hundreds of projects. I think we still h…
What is the argument for keeping it all in the same solution?