Did they finally add local history? NO.
Did they finally fix the projects to not reference EVERY SINGLE (&(&*(( FILE to prevent daily conflicts? NO.
FAIL.
Visual Studio 2013
51–60 of 201 posts
Re: Visual Studio 2013
#52Earlier quoted context omitted.
How hard would it be to create stub apps that really just call out to clang/llvm?
Not hard. But how hard would it be to make large existing codebases which have always been built by VC++ compile against them? Very. Let alone the institutional aversion to admitting their competitors have done something better than them...
Personally I've wanted a project type without a "compile" in VS for a while... mainly for other environments that serve as a client/service for the VS stuff... I often use a "website" project and uncheck it from "build" but that's not quite what is needed.
Mainly, as an example, I want to be able to have my NodeJS webservice project in the same solution as my MVC website project, and the C# dll client project. The NodeJS solution doesn't need all the assembly folders, or a .Net compile... but it does need the configured prebuild step, that's it. People say to use a "Website" project, but that brings my entire node_modules tree into source control. It's a pain.
Re: Visual Studio 2013
#53As someone who uses reharper to make the IDE cool, git for source control, teamcity for builds, nunit for C# tests, mocha and testacular for js tests, and a goddamn whiteboard, cards, pens, and blue-tack for "agile portfolio management", I'm not seeing a lot here that interests me. I'm underwhelmed with the desire to suck all activities into the one tool to rule them all. Especially when it rules them from bleh TFS.…
I want VS to let me write code. I want to find and manipulate text. I want it to compile fast and produce relevant warnings. I want a debugger. I want it to host duiverse plugins. That's mostly it.
That's all I want Visual Studio for, too. Fortunately those things will continue to work and we can continue to ignore things like TFS and mstest.
Re: Visual Studio 2013
#54And yet, still no formalized C99 support.
I know everybody is hot and bothered about C++11, but honestly I'd suggest just getting proper support for things we've needed for a decade or so before chasing the new shiny.
Re: Visual Studio 2013
#55Earlier quoted context omitted.
If you've ever had to maintain a large, legacy .net app that has been around since 1.0 or even has some ASP 'classic' code in it, upgrading is a major nightmare. I know at least two shops right now 'stuck' on 2005 because various problems upgrading to 2008, let alone to 2012 or 2013 now. They are more likely to re-write the whole thing in Ruby at this point. I'm actually running 2012 personally, not such a big deal o…
You can install several versions of Visual Studio side by side - keep an old version for maintaining legacy projects, use a new version for new projects.
Except you cannot have .NET 4.0 and 4.5 on the same machine, given the way 4.5 overwrites 4.0.
Re: Visual Studio 2013
#56And yet, still no formalized C99 support. I know everybody is hot and bothered about C++11, but honestly I'd suggest just getting proper support for things we've needed for a decade or so before chasing the new shiny.
Have you missed the news? C is dead on Microsoft tooling, they have deprecated it.
http://herbsutter.com/2012/05/03/reader-qa-what-about-vc-and...
Re: Visual Studio 2013
#57Way way way way, WAY too soon Microsoft... most shops, including my current employer aren't even on 2012 yet... Honestly I prefer VS to be tied to desktop OS releases or SQL release or something other than yearly. This is not a Madden game, nobody is asking for yearly updates for Visual Studio.
Seriously! My company has been keeping up with the latest stuff but I have hard time understanding what the justification was behind releasing a whole new Visual Studio version. Are there new features that won't be available in VS 2012? I guess we'll see at the Build conference.
Update 3 was the last one.
Maybe Microsoft is tight on money. :)
Re: Visual Studio 2013
#58Earlier quoted context omitted.
ex-VS person here (from 5 years ago though). It is never an either-or. It is always a complex mix of what customers ask for, what the strategic priorities/market realities are. Often the problem with these queries is that there are not enough devs complaining to MSFT. No PM/engg manager is going to ignore a bug/problem if it shows up high in customer requests. On promotions - I think it's the reverse problem. People…
> Often the problem with these queries is that there are not enough devs complaining to MSFT. No PM/engg manager is going to ignore a bug/problem if it shows up high in customer requests. Note that you switch between "devs" and "customer" there. I argue that the real problem is that for VS those demographics are different. Devs in "Microsoft shops" don't go out and decide on a complier, they use VS because that's all…
> ... they use VS because that's all there is
On Windows there are lots of compilers to choose from.
Re: Visual Studio 2013
#59Yet another Visual Studio, yet another truckload of "features" that do nothing to help day-to-day, heavy-lifting programmers. (And which probably help by adding bugs or just bloating the system). Sigh. I am hoping they have made substantial improvements that are not mentioned in this blog post.
Try R# with VS.
Re: Visual Studio 2013
#60I wish they would dedicate more time to improving cl.exe and link.exe in terms of performance and language support and less time with these hokey team visualization gimics. Every release since 2008 has been getting slower and slower for C++, the C compiler is awful, PGO instrumentation in Win8 is less capable, and there's no equivalents in the Windows ecosystem to gcc's likely/unlikely, oprofile, or valgrind. It's at…
C is officially deprecated. Personally I would like to see proper C++11 support instead of playing around with C++/CX and while they are at it, either provide a native compiler for .NET or improve NGEN's optimizer for C++ performance level. Given that Microsoft had .NET native compilers for Singularity and Windows Phone 8 .NET apps are compiled to native code, it isn't as if they don't have the tooling already availa…
honest question, is the Windows kernel written in C++? If not, what does that team use to build it if "C is deprecated"?