pouët.net

I really got a lot happier starting with 2012 tbh.

Using VS2013 (Ultimate) for quite a while now - I'm quite happy with it. "Peek Definition" is really a nice convenience feature I've been missing a long time.

All I can say is that VS2010 + VAX is considerably slower than VS2008 + VAX. It became bearable when starting to use an SSD.

As if something would do file access all the time. Like, perhaps.. VAX? :)

@las: what is it?

Yea, I first used 2012 to port my DX11 code to Windows Phone/RT for teh lulz...
So I built it with ARM target instead of x86.
At first I thought "Whoah! Compile time is way shorter! Is that because it has to spend a lot less time optimizing the code than x86 with all its weird idiosyncracies?"
Then I tried building it for x86, and I had about the same nice build times. So apparently there's some fundamental changes in the compiler that make it a lot faster than before.

kb_: Yes, it's a complete mystery, isn't it? :)

For VS2015 they're even announcing C++ refactoring support which is about 15 years overdue. My main hope is they also get around to fixing the ludicrous amount of processing that Intellisense requires. Maybe when they finally give in and just start using clang as the main compiler :)

superplek: http://msdn.microsoft.com/de-de/library/dn160178.aspx
You can also modifiy code in that "subwindow" - I really like that feature.

I wonder if that modern version of VS are working under WINE...

@rez if you can stick with command-line C#, then Xamarin Studio is your bet (Mono IDE)

Whilst there are "cool new features" in the new VS, I'd recommend that anyone already happily using VS2008 create additional project solutions for the new VS and not migrate their existing. This will allow you to switch compilers. I personally prefer using VS2008 day to day as its what I'm most used to, but can't deny the additional value of the tools within the newer versions.

One issue I encountered is that my shared libraries created with VS2008 are forwards compatible to VS2012/2013, but that once created with VS2012/2013 backwards.

So when I migrated a particular solution/project where I'd included a another project for a shared lib all my other older VS20087 projects which also used the shared lib wouldn't then compile.

In the next revision/refactor of my code base I'm designing that kind of project structure out, for that and other reasons.

Also, if anyone has some up to date size coding tips to nobble the default libs and have minimal footprint for VS2013 they'd be useful. If not i'll be investigating myself at some point, but I've got to finish another project before I get back to that..

Yes for some of my libs I would just have multiple versions: NNN_VS2008.lib, NNN_VS2010.lib and such. Same for release and debug build.
But my main codebase is still in VS2010, and not sure when I will be switching over.

(God I wish this forum had an edit option for posts sometimes!)


I guess the rule is don't switch over til ya have to :)

Already been strict about not creating code for the sake of it, as my next project requires a restructure I'm cleaning the slate and only bringing across the essentials. Aiming for One solution&project per compiler vs2008 (maybe vs2013 due code quality checks) and xcode. And as highlighted by Saga Musix above, will be going down the SSD road for swifter compilation too. The goal always always the current project and an experiment or three, not a general library/engine.

You may be surprised, but: I´m not using VAX (or its precedessors) for my intros at all ;D

thats probably why they lack tomatos

I wish VS had the Steam-like notifications from your friends list, like "kb_ just compiled a build!"

XP is still nice for some x86 intros that run too slow on dosbox. It's a pity I don't have it in my box anymore.

Well, at least it has achievements.

Wasn't that just an addon?

Although hm, I guess the whole friendslist stuff could be written in an addon too...

It would be fun to get compile errors from your friends as status updates.

Especially as the party nears? :)

"Preacher just got the error : c:\projects\skene\newdemo\fx\whatever.cpp(816): error C2065: 'wtf_work_already_you_pos_kludge2' : undeclared identifier"

or.. "coder: execution ended unexpectedly"