61–70 of 201 posts
Earlier quoted context omitted.
I don't mind it. It's not like it's high-contrast, large font, or bold, it just serves as a heading for the menus they show without making the font large or bold. It's definitely nowhere near as annoying as intellisense randomly breaking and putting a red line underneath half your statements.
> intellisense randomly breaking and putting a red line underneath half your statements There's a reasonably simple solution with which you can solve the red line problem, if you're talking about the C and C++ projects: http://connect.microsoft.com/VisualStudio/feedback/details/5... "Posted by JoeWoodbury on 25/02/2010 at 10:16 (...) The solution is to add the location of the stdafx.h file to the include path list. T…
Earlier quoted context omitted.
Full new version or Service Packs? I agree with you but a Service Pack should suffice esp. right after you've release a full new version/update to a major product/tool like VS.
The full version vs. service pack distinction doesn't really matter to me.
I'm pretty sure I can upgrade to a service pack. Changing versions, OTOH, probably requires approval from management.
Earlier quoted context omitted.
> 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.
Earlier quoted context omitted.
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.
Earlier quoted context omitted.
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 No…
I can std::thread(a,b,c,d,e,f,g) more than 5 arguments?
Earlier 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…
>Basically, the way feedback works in this world is with feet, not bug reports. If you build it they will come. If you don't they will leave.
Is there any quantifiable metric to measure this so called exodus beyond anecdotes and the ".NET is dying" posts on here?
If there was an IDE for .NET on par with VS, it will definitely see uptake regardless of suits.
I 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…
Earlier quoted context omitted.
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"?