Any valid reason to migrate from VS 2008?
-
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! ;)
My programming get away... The Blog... DirectX for WinRT/C# since 2013! Taking over the world since 1371!
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.
-
What's a "P.A." library?
My programming get away... The Blog... DirectX for WinRT/C# since 2013! Taking over the world since 1371!
Parallel Async ;)
Behzad
-
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
Of course, sharepoint development, especially web part deployment, is much easier in VS2010/2012. This is the only reason, i have installed VS2012 :laugh:
Behzad
-
Of course, sharepoint development, especially web part deployment, is much easier in VS2010/2012. This is the only reason, i have installed VS2012 :laugh:
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 :suss: If you can't read my code, try converting it here[^]
I just binged and found this link : An Overview of Performance Improvements in .NET 4.5[^]. Though it is ver. 4.5 not 4.0, i will read it to find out the differences, but for now, the overall performance of .net 3.5 SP1 is acceptable.
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
-
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
ho? then: http://msdn.microsoft.com/en-us/library/vstudio/hh191443.aspx[^]
My programming get away... The Blog... DirectX for WinRT/C# since 2013! Taking over the world since 1371!
-
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. :laugh: Marc
Yeah I had that sometimes with VS2010!
My programming get away... The Blog... DirectX for WinRT/C# since 2013! Taking over the world since 1371!
-
I still use it for our main application and am happy with it. The only new feature that is missing is word highlighting which, for it, i have installed WordLight. I generally hate the new Help viewer system and stuck with the old one . 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. To be honest, our application ( A Huge SCADA software, more than 200 KLOC ) is written in WinForms not WPF, and for IPC, we use .Net remoting, though it is slow in some scenarios and i am thinking to migrate to some free alternatives. Finally cross platform execution is a must have. Do you have any experience in this root? any thought?
Behzad
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.