VS 2008, or VS2010
-
Ger Hayden wrote:
2008 or 2010 to run on Windows 7 and why?
Because you can.
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. nils illegitimus carborundum me, me, me
I am always amused by these types of questions. Why would you invest time and money in the old technology? I'm sure 2005 is a viable option for most projects, or even the orignial Visual Studio.Net. Why are they running Windows 7 instead of XP (or MS-DOS). You should always buy and learn (invest in) the current version, not an old one. In 2010, C# supports optional parameters. That, by itself, is enough justification.
-
I have Visual Studio 2008 on my personal laptop using Vista, but I now have to recommend a version to my employer. 2008 or 2010 to run on Windows 7 and why?
Ger
In my situation VS2008 works best. I have both it and VS2010 on the office machine but when I decided to build up my development machine for my small business I went with 2008. I was able to get VS2008 "Standard" pretty inexpensively (like ... $125 or so) and built up my environment with Visual Source Safe 6 (which I owned a copy of already) and Active Reports 6 (which I got for about $600). I build Windows desktop applications (and occasional ASP.Net 'tinkering') and it all "just works". I'm running all this on Windows7 Ultimate primarily on my Dell Inspiron 1545 notebook. I've also bought a number of professional books (in PDF form) that are all written for VS2008. The company I work for eventually wants to move to VS2010, though in the development mode we're in I can't honestly see why. We were acquired a year and a half ago and our product is strictly in maintenance mode. However ... that's not my call. I did play with VS2010 with my project and, quite frankly, could not see why I should upgrade to it. Besides seeming a bit slower there weren't any features that I need that would justify me coughing up another $500+ for just to say I have the "latest". For my small company and the product I'm building I doubt I'll need to move on from VS2008 for a very long time. I'm not overusing the feature set of VS2008 as it is. To retool just to have the latest without a solid reason to spend the bucks on it is ridiculous. I'd rather invest my dollars in additional equipment (mag stripe scanners, stuff like that) I need for my product development. Besides, unless (as I said above) some feature identifies itself as a "got to have" feature I just can't see retooling. I've made my investment for the time being - this is a real case (to me) of: "If it ain't broke, don't fix it". -Max :D
-
Except for a much improved compiler, closer to standard, including some C++ "0x" features.
My analysis found that the compiler wasn't much improved, only slightly improved, and I've found most of the C++ "0x" features aren't worth the effort on legacy code.
-
Dwayne J. Baldwin wrote:
Serious developers consider ... multiple monitors ... to be even more productive
Grabbing popcorns and waiting for John C to see this...
They say you can't teach an old dog new tricks. I know they were wrong. For more entertainment, press Windows+Left (or Right).
Dwayne J. Baldwin
-
I have Visual Studio 2008 on my personal laptop using Vista, but I now have to recommend a version to my employer. 2008 or 2010 to run on Windows 7 and why?
Ger
As far as the widely used languages (C/C++/C#/VB) are concerned, they're pretty similar. In the short term you'd probably be fine with either. However, in the long term, unless you actually want to get caught in the we-no-longer-support-this-obsolete-product undertow, go with VS2010, and keep your nose above water a bit longer.
-
I have Visual Studio 2008 on my personal laptop using Vista, but I now have to recommend a version to my employer. 2008 or 2010 to run on Windows 7 and why?
Ger
For WPF, VS2010 is clearly better (in my humble opinion), and .Net 4.0 has some really cool features. It does crash quite a lot, but so did vs2008 (ok a bit less). Anyway, as someone else mentioned, there's no point investing backward, for the company (and for you as a matter of fact), it will just mean extra overhead to upgrade in few years. Like it or not, there's no stopping progress I'm afraid...
-
I have Visual Studio 2008 on my personal laptop using Vista, but I now have to recommend a version to my employer. 2008 or 2010 to run on Windows 7 and why?
Ger
VS 10 all the way. Can you say project specific paths? But the Color Theme editor extension is a MUST.
-
I am always amused by these types of questions. Why would you invest time and money in the old technology? I'm sure 2005 is a viable option for most projects, or even the orignial Visual Studio.Net. Why are they running Windows 7 instead of XP (or MS-DOS). You should always buy and learn (invest in) the current version, not an old one. In 2010, C# supports optional parameters. That, by itself, is enough justification.
Dave_6 wrote:
In 2010, C# supports optional parameters. That, by itself, is enough justification.
VB supported optional parameters from... oh, version 4, I think :rolleyes:
-
Wow. I've never heard anyone say VS2010 was faster doing anything.
Best wishes, Hans
-
I have Visual Studio 2008 on my personal laptop using Vista, but I now have to recommend a version to my employer. 2008 or 2010 to run on Windows 7 and why?
Ger
It is my opinion that VS2010 is superior in every way EXCEPT for the "new" help system, which is utterly useless, broken, intercoursed, etc.
-
The best editor for large text files is hands down Notepad++ It has a multitude of options and plugins that ship with it and even more available to download. Most importantly it's freaking fast, and can handle everything I've thrown at it so far. I just opened a 25mb raw (.nef) file in less than half a second
That is a much better choice of using a proper tool for the job. Still not as good as being parsed into a database for searching and reporting. "Give a child a hammer and the world becomes a nail."
Dwayne J. Baldwin
-
I have Visual Studio 2008 on my personal laptop using Vista, but I now have to recommend a version to my employer. 2008 or 2010 to run on Windows 7 and why?
Ger
-
Dave_6 wrote:
In 2010, C# supports optional parameters. That, by itself, is enough justification.
VB supported optional parameters from... oh, version 4, I think :rolleyes:
ChandraRam wrote:
VB supported optional parameters from... oh, version 4, I think
Yes, but VB! Come on.
-
I have Visual Studio 2008 on my personal laptop using Vista, but I now have to recommend a version to my employer. 2008 or 2010 to run on Windows 7 and why?
Ger
If you're using C++, I would stick with VS2008. I have VS2010 installed on several computers, Vista and Win7 - The help system isn't as good as VS2008 (ymmv) The IDE freezes at times. The IDE crashes fairly often. Intellisense is broken most of the time. Source browsing/references (ie jump to declaration or definition) often doesn't work. Some of the C++00x features aren't implemented in VS2010 anyway.
-
ChandraRam wrote:
VB supported optional parameters from... oh, version 4, I think
Yes, but VB! Come on.
Is C# actually better than VB? If you exclude unsafe code, they seem to be about the same.
-
Is C# actually better than VB? If you exclude unsafe code, they seem to be about the same.
Yes. I know they are both part of the .net framework, but who needs all that If then End if rubbish what’s wrong with if(){}, much simpler. Also by learning c#, you would easily be able to understand java and even c++ to a point. Its like chavy English (VB) compared to the Queens English (C#), they both do the same thing, but which one make you sound like you have had an education. :-D Cheers GC
-
I have Visual Studio 2008 on my personal laptop using Vista, but I now have to recommend a version to my employer. 2008 or 2010 to run on Windows 7 and why?
Ger
At this point, I have my own copy of VS2008 since 08 on my own laptop. I have VS2010 Express for VC++ on the laptop supplied by my employer - thats the one that needs the new version. I have seen some of the performance issues discussed here, and Intellisense doenst work on VS2010 Express for me. I want to go VS2010, partly becasue I dont want to get left behind again as I did staying on 6.0 too long. But the end client is rooted in .NET 3.5 and moving it to .NET 4.0 could be a bridge too far...
Ger
-
Yes. I know they are both part of the .net framework, but who needs all that If then End if rubbish what’s wrong with if(){}, much simpler. Also by learning c#, you would easily be able to understand java and even c++ to a point. Its like chavy English (VB) compared to the Queens English (C#), they both do the same thing, but which one make you sound like you have had an education. :-D Cheers GC
I know a few languages (awk, c, perl, ksh, cfm, c++, vb6 and up, c#, a few others that I choose to forget like cobol). I have to take a deep breath before I open a c++ or vb6 project for different reasons, but I can look at C# in one window and re-type vb.net in the other. Syntax difference isn’t that great (a couple characters at best). I have seen very well written vb.net code and very poor c#, but probably more common the other way around (I won’t discuss vb6). Either way, the .NET language you choose shouldn't put you in an elite or poor programmer group. VB has more programmers than C# and is easier for less experienced people to read and understand. That translates to less maintenance work for me and why I prefer vb.net. I have to vent on this issue once in a while.