|
Yes, it's a horrible little country with high unemployment and crazy inflation and is years behind the times. Plus the grass is always greener... 
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
Those who seek perfection will only find imperfection
nils illegitimus carborundum
me, me, me
me, in pictures
|
|
|
|
|
If you can, I'd upgrade straight to VS2012. There are lots of little improvement in newer versions (parallel stacks etc.) Also the NuGet features of 2012 are awesome. Want NUnit or log4net? Then just add the package and the references are downloaded and added to the solution. That is awesome.
Regards,
Rob Philpott.
|
|
|
|
|
VsVim doesn't work with VS 2008. For me, it would be enough reason to migrate to a newer version.
|
|
|
|
|
Yes.
If your actions inspire others to dream more, learn more, do more and become more, you are a leader.-John Q. Adams
You must accept one of two basic premises: Either we are alone in the universe, or we are not alone in the universe. And either way, the implications are staggering.-Wernher von Braun
Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.-Albert Einstein
|
|
|
|
|
Well for one thing VS2012 has better performance and lower footprint. Even if you stay with .NET2 you'll be happy to use a faster more responsive tool.
Regarding IPC, first there was remoting, then there was WCF dunno if it's any faster/slower but it's more flexible and the preferred serialization to use with it (DataContract) is much more flexible / less constraining than remoting.
Now WCF is quite good I think, but arguably its configuration often quickly become terrible. Some people prefer OSS Servicestack for that reason. Though I think they dismiss WCF a little too quickly IMHO.
Eventually you can progressively give a go to new technology such as LINQ, parallel async library. they do make life easier when you use them!
Also I will encourage you to use WPF and MVVM for new UI. You'll be surprise how much cleaner and easier to maintain things become with it (once you get the hang of it! ^^)
Finally don't rewrite existing things which works for no reason, use new tech for new things! 
|
|
|
|
|
Because of time constraints and lack of developer experience with WPF, we stuck with WinForms, though we may eventually use it in future releases.
Regarding Linq, our application is not such a database-centric one. Usually SCADA/Industrial softwares need to combat large amount of data in realtime so almost, everytime, using RDBMS is useless. At the en we developed an in-house method for storing/retrieving data into/from file.
And for P.A. library, i have no idea. Any guide?
Finally, we are at the stage of improving performance/stability and our application is almost feature-complete, So using any new technology should be with great care 
Behzad
|
|
|
|
|
Behzad Sedighzadeh wrote: Regarding Linq, our application is not such a database-centric one.
Linq does more than just databases, it also works with .NET collections like Lists (really, anything that implements IEnumerable).
|
|
|
|
|
Yeah, I know what the LINQ does, But , for me, some helper methods can do what the LINQ library is doing. You know what i wanna say...
Behzad
|
|
|
|
|
Well that's really all it is, a bunch of helper methods. Why write it from scratch if someone else has already done it and tested it? (Of course, I understand it not being worth upgrading for just that, especially if you aren't manipulating collections much.)
|
|
|
|
|
|
Parallel Async
Behzad
|
|
|
|
|
|
Super Lloyd wrote: such as LINQ, parallel async library. they do make life easier when you use
them!
Really? How much easier specifically? How much more productive are you using measured metrics (rather than just the whimsical - 'of course I am')?
And presumably you are using them correctly as well. Is everyone else working on your product using them correctly as well? How do you ensure that?
Naturally if someone isn't using them correctly and starts trying to use them for absolutely everything they can or even misunderstanding the basics then one might suppose that at some point it isn't going be easier and in fact is going to be much harder.
|
|
|
|
|
Contrary to Super Loyd, I find the performance of VS2012 to be much worse than VS2008. If you don't need F# or the latest WPF stuff (and, I'm not sure if VS2008 supports the latest .NET framework), stick with 2008. And as others have commented, completely skip 2010 - waste of time.
Marc
|
|
|
|
|
I would not bother upgrading to 2012 if all your current code works you will just be buying into a world of hurt.
I upgraded from 2008 to 2010 a while back and didn't regret it at all - although all I really gained were some improvements in plug-in handling and being able to zoom the editor text size up and down. I didn't notice any significant performance differences within the area I working. I did it mostly for the editor improvements.
The change to 2010 should be painless if you want to bother; the change to 2012 will be painful, guaranteed!
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
Forogar wrote: I would not bother upgrading to 2012 if all your current code works you will just be buying into a world of hurt.
Actually, I converted a large client-server application without problems, but then again, there were very few component dependencies (only DevExpress, which gave me no problems.)
Marc
|
|
|
|
|
I found vs2012 starts as fast vc# 2008 express does or even faster;
i am surprised and sad for you, you have a different experience!
have you installed some plugins? I only have the one you can download with the extension manager, NO resharper for example...
|
|
|
|
|
Super Lloyd wrote: have you installed some plugins?
Nope, no plugins. VS2012 locks up for a minute or two quite often on startup with the message "busy performing a background task". Geez, if it's a background task, why does it affect foreground operations? That's probably one of the more stupid messages I've ever seen. 
Marc
|
|
|
|
|
Yeah I had that sometimes with VS2010!
|
|
|
|
|
Of course, sharepoint development, especially web part deployment, is much easier in VS2010/2012. This is the only reason, i have installed VS2012 
Behzad
|
|
|
|
|
Behzad Sedighzadeh wrote: Of course, sharepoint development, especially web part deployment, is much easier in VS2010/2012.
Hmm, good to know.
Marc
|
|
|
|
|
Behzad Sedighzadeh wrote: Besides, i don't see any real reason to migrate to new .Net 4 or 4.5, simply because i have not used any feature of those packages.
Whehe ..and now you want us to tell you why you should upgrade, convincing you? Have you ever tried to convince someone who asked for a valid reason to upgrade from VB6?
You can still target the 2.0 framework and use the 4.0 runtime for it's benefits. Things like improved garbage-management come to mind. Ooh, gone the days that a .NET app froze without any obvious reason 
..and yes, I'm using the 4.0 framework from both OpenSUSE aswell as Debian (a Raspberri Pi).
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
|
I use VS2010 at home (for WinForms development) and love it. I upgraded from VS2005 and VS2008. At work I use both VS2010 and VS2012.
/ravi
|
|
|
|
|
I use 2012 at work (mostly for SSIS), but 2010 at home where I'm more likely to do WinForms.
But mostly I write console apps and libraries and I don't use VS for that.
Behzad Sedighzadeh wrote: the new Help viewer
Yes, the old one was better.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
