Cisharp

HowTo create a visual studio 2013 multi-project solution and add it to team foundation server express 2013 => create an empty solution in visual studio => add the folder structure and the sub projects as desired => delete the solution file => create the solution file again; this time check the checkbox "add to source control"; choose GIT as the desired version control system => connect to the team foundation server in the team explorer of VS2013 => connect to the desired Team Project Collection (if none existent, then you have to create that one first on the TFS Administration Console => say under "Team Explorer - Connect " -> Create Team Project... and create it => now, clone the repository into an empty folder => close VS, copy the solution and the structure you just created into that newly created empty folder => now make a git commit and then push to origin for the branch master (i use GitExtensions for that)

i recently came across a "new" IDE for C/C++ development. well, is "Qt Creator" really new? not exaclty, so lets call it the underdog of IDEs then. but because of my dissatisfaction with everything apart from visual studio i've so far used, i immediatly tried out the new 1.2.1 version of Qt Creator. and boy, i am amazed! this is really a great IDE for developing C++ applications. The name is a bit irritating because it implies its purpose is to create QT apps. well, maybe it is, but its also very good for "normal" apps. till now i have used eclipse. i hate it but i sticked to it because of its good parser and syntax highlighting. plus the debugger is capable of showing you the base classes members of your instances and resolves the type. this made it the best IDE i knew so far. but now i am more and more working with qt creator. so here a small comparison between qt creator and eclipse of the cons for me of both IDEs Qt Creator vs Eclipse CDT Qt Creat...

I have just finished the new and shiny extensions to socketCC. socketCC, the nice class based Socket library.... so now even more shiny!  :) the original socketCC library was mainly designed for linux. Mac OS support was added to it too, but you could not use it under windows.... awkward choice isnt it?  i therefore made it compiling and working with windows like i already said here . but now all bugs should be out and it works like charm!  the cool thing for all pure-windows VC coders out there is: there is a workable VS2008 solution, that can be compiled just like that, without the need for setting anything else up or understanding makefiles.  AFAIK there is no other nice free open library for windows that does this.  so heres a rough list of what has changed from the features of the original socketCC, (description for a deeper understanding of the original socketCC lib can be found in this Dr. Dobbs socketCC article): • support for windows , tested on VS2005 and VS2008 visual studi...

This blog entry might get you up and running with Eclipse if you come from Visual Studio without you having the need to immediately look at how to create makefiles or how the eclipse workspace philosophy works. I expect that you are somewhat familiar with Visual C++ though. I like Eclipse. Well.... no, i don't. I like Visual Studio especially for C#, but Visual C++ has some drawbacks, especially when used to code cross platform non-.NET and without precompiled headers. Still I don't know why so many people find Eclipse so great, but granted, it has a very decent code completion, nice automake and a very good syntax highlighting. I use it too. Its the next best thing ive tried so far to VS. What I hate about it are the project- and workspace philosophies of Eclipse and that the program is somewhat slow. Visual Studio projects/solutions are much easier to use and you grasp its concepts quicker and, most importantly, you are free to include any file you want into your project ind...