Is anyone else considering skipping the VS2008 generation?
-
David Lockwood wrote:
I love .Net 2.0 and I also feel I haven't explored the entirety of it along with VS2005
FYI, the new VS lets you continue to target .NET 2 and up.
Tech, life, family, faith: Give me a visit. I'm currently blogging about: Halloween and Celebrating Man's Festivals The apostle Paul, modernly speaking: Epistles of Paul Judah Himango
-
Or becoming a late adopter? Although there's a lot of cool stuff in .Net 3.5 I can't help but feel that I haven't done .Net 2.0 to death yet. Also, given the amount of stuff currently coming out of Microsoft, I do wonder whether it's best to wait and see what falls by the wayside, for instance WPF - from what I've seen people on CodeProject do with it it looks very cool... but it wouldn't be the first time I've devoted effort to learning something only to see the marketability of such skills divebomb into obscurity.
Me: Can you see the "up" arrow? User:Errr...ummm....no. Me: Can you see an arrow that points upwards? User: Oh yes, I see it now! -Excerpt from a support call taken by me, 08/31/2007
I am already using VS 2008 for a new development so I guess I am not becoming a late adopter.
Co-Author ASP.NET AJAX in Action CP Quote of the Day: It is the same Friday that blooms as a new enriching day with novelty and innovation for us every week. - Vasudevan Deepak Kumar
-
Get a better job :)
Me: Can you see the "up" arrow? User:Errr...ummm....no. Me: Can you see an arrow that points upwards? User: Oh yes, I see it now! -Excerpt from a support call taken by me, 08/31/2007
-
Or becoming a late adopter? Although there's a lot of cool stuff in .Net 3.5 I can't help but feel that I haven't done .Net 2.0 to death yet. Also, given the amount of stuff currently coming out of Microsoft, I do wonder whether it's best to wait and see what falls by the wayside, for instance WPF - from what I've seen people on CodeProject do with it it looks very cool... but it wouldn't be the first time I've devoted effort to learning something only to see the marketability of such skills divebomb into obscurity.
Me: Can you see the "up" arrow? User:Errr...ummm....no. Me: Can you see an arrow that points upwards? User: Oh yes, I see it now! -Excerpt from a support call taken by me, 08/31/2007
Anyone who plans to do .NET development will probably want VS 2008. If they do not, then they probably clueless and have their head buried in their work. VS 2008 is a fairly major upgrade and if you are doing web work, it is hard to imagine using prior versions once you have used 2008. Stability will be an issue for a while I would imagine. I have used it for some time now and still have it crash on me at times or functionality will disappear until I reboot. Not that big of thing though and is not worth thinking about compared the new additions. As for technologies such as WPF and LINQ falling by the wayside, anyone that has used these technologies to any extent will confirm, they are only moving ahead. Microsoft has invest billions in these technologies along with the fact, there are very useful! No need to worry, the future is here if people want it. If not, they will be forced to pick it up down the road just a little bit because clients and the job market will demand it just like it has with .NET! I think the smart developer will already have got VS 2008 and at least played with it by now. I know there are number of people that cannot devote the time as they are busy with work, but often that forces them to play catch up later own, I use to be in that camp :)
Rocky <>< Blog Post: LINQ - Disconnected-Attach, no change tracking fix.. Tech Blog Post: Cheap Biofuels and Synthetics coming soon?
-
Or becoming a late adopter? Although there's a lot of cool stuff in .Net 3.5 I can't help but feel that I haven't done .Net 2.0 to death yet. Also, given the amount of stuff currently coming out of Microsoft, I do wonder whether it's best to wait and see what falls by the wayside, for instance WPF - from what I've seen people on CodeProject do with it it looks very cool... but it wouldn't be the first time I've devoted effort to learning something only to see the marketability of such skills divebomb into obscurity.
Me: Can you see the "up" arrow? User:Errr...ummm....no. Me: Can you see an arrow that points upwards? User: Oh yes, I see it now! -Excerpt from a support call taken by me, 08/31/2007
I (and my company) will most likely completely skip it. I don't do business/enterprise applications these days so I just don't see the need.
My Blog A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. - -Lazarus Long
-
Son, I give you that promotion :) (and if any asks tell them that Martin Hughes, yes MARTIN HUGHES, gave you that authorisation. They may say to you "who", you just repeat my name. And with volume. You'll be a shoe in! :) )
Me: Can you see the "up" arrow? User:Errr...ummm....no. Me: Can you see an arrow that points upwards? User: Oh yes, I see it now! -Excerpt from a support call taken by me, 08/31/2007
-
Or becoming a late adopter? Although there's a lot of cool stuff in .Net 3.5 I can't help but feel that I haven't done .Net 2.0 to death yet. Also, given the amount of stuff currently coming out of Microsoft, I do wonder whether it's best to wait and see what falls by the wayside, for instance WPF - from what I've seen people on CodeProject do with it it looks very cool... but it wouldn't be the first time I've devoted effort to learning something only to see the marketability of such skills divebomb into obscurity.
Me: Can you see the "up" arrow? User:Errr...ummm....no. Me: Can you see an arrow that points upwards? User: Oh yes, I see it now! -Excerpt from a support call taken by me, 08/31/2007
I haven't even looked the hype yet. I'll stick with 2005 unless I change to a job where I'm required to use something else.
-
Or becoming a late adopter? Although there's a lot of cool stuff in .Net 3.5 I can't help but feel that I haven't done .Net 2.0 to death yet. Also, given the amount of stuff currently coming out of Microsoft, I do wonder whether it's best to wait and see what falls by the wayside, for instance WPF - from what I've seen people on CodeProject do with it it looks very cool... but it wouldn't be the first time I've devoted effort to learning something only to see the marketability of such skills divebomb into obscurity.
Me: Can you see the "up" arrow? User:Errr...ummm....no. Me: Can you see an arrow that points upwards? User: Oh yes, I see it now! -Excerpt from a support call taken by me, 08/31/2007
This is one of the reasons I've given in my petition against renaming WinFX to .NET 3.0.[^].
2. Rename to .NET 2.5: It may be better than “.NET 2.1” in that it indicates a large advancement, while still building upon the success of the .NET framework and maturity of .NET 2.0 – maturity being very crucial for adoption, particularly in the enterprise market. **The name .NET 3.0 casts doubt on the maturity of the .NET framework as a whole.**.NET 3.5 is .NET 2.0 with a few new features to C# and VB. WPF is part of ".NET 3.0", which isn't even a version of .NET, it's just a toolkit. So there is no question here about whether you should use .NET 3.5 or .NET 2.0: either way, you're still using .NET 2.0; .NET 3.0 and .NET 3.5 features are purely optional. Your question is simply whether or not WPF/WCF/WF are beneficial to your projects. As for VS2008, I won't buy it, because I'm content with VC# 2008 Express. -
Late adopter definitely.
Deja View - the feeling that you've seen this post before.
yeah, and we are very happy with .net 1.1 webpages. :):cool:
Jwalant Natvarlal Soneji
BE IT, India -
Or becoming a late adopter? Although there's a lot of cool stuff in .Net 3.5 I can't help but feel that I haven't done .Net 2.0 to death yet. Also, given the amount of stuff currently coming out of Microsoft, I do wonder whether it's best to wait and see what falls by the wayside, for instance WPF - from what I've seen people on CodeProject do with it it looks very cool... but it wouldn't be the first time I've devoted effort to learning something only to see the marketability of such skills divebomb into obscurity.
Me: Can you see the "up" arrow? User:Errr...ummm....no. Me: Can you see an arrow that points upwards? User: Oh yes, I see it now! -Excerpt from a support call taken by me, 08/31/2007
martin_hughes wrote:
Although there's a lot of cool stuff in .Net 3.5 I can't help but feel that I haven't done .Net 2.0 to death yet.
I feel that way as well, but I'm slowly convincing myself that I can still do most of the 2.0 stuff I'm interested in, but with the all the cool 3.5 stuff. Hell, I haven't even written a single LINQ query yet, and that has to be the coolest! How many times do I curse when writing an iterator only to select certain items?
MY BLOG
-
yeah, and we are very happy with .net 1.1 webpages. :):cool:
Jwalant Natvarlal Soneji
BE IT, IndiaMy team leader has a VM for our last remaining vestiges of 1.1, so he doesn't have to tarnish his machine. We do however use Web Applications, and not the new 2.0 Web Site architecture.
MY BLOG
-
You shouldn't have to be a manager to play a role in determining your development tools.
MY BLOG
-
I already dived right in. I'm using VS 2008 100%, although I'm still targeting the .NET 2.0 framework. Mark
Mark Salsbery Microsoft MVP - Visual C++ :java:
Do you have any blogs or anything on your experiences with it? I'm guessing I'll be diving right in with the promised November release.
MY BLOG
-
Or becoming a late adopter? Although there's a lot of cool stuff in .Net 3.5 I can't help but feel that I haven't done .Net 2.0 to death yet. Also, given the amount of stuff currently coming out of Microsoft, I do wonder whether it's best to wait and see what falls by the wayside, for instance WPF - from what I've seen people on CodeProject do with it it looks very cool... but it wouldn't be the first time I've devoted effort to learning something only to see the marketability of such skills divebomb into obscurity.
Me: Can you see the "up" arrow? User:Errr...ummm....no. Me: Can you see an arrow that points upwards? User: Oh yes, I see it now! -Excerpt from a support call taken by me, 08/31/2007
-
Or becoming a late adopter? Although there's a lot of cool stuff in .Net 3.5 I can't help but feel that I haven't done .Net 2.0 to death yet. Also, given the amount of stuff currently coming out of Microsoft, I do wonder whether it's best to wait and see what falls by the wayside, for instance WPF - from what I've seen people on CodeProject do with it it looks very cool... but it wouldn't be the first time I've devoted effort to learning something only to see the marketability of such skills divebomb into obscurity.
Me: Can you see the "up" arrow? User:Errr...ummm....no. Me: Can you see an arrow that points upwards? User: Oh yes, I see it now! -Excerpt from a support call taken by me, 08/31/2007
I am still converting from 2003 to 2005. As 2005 is the rock which 2008 is based on I will continue with that. Is is my imagination or is .NET doubling in size with each new release? Are we now going to have to start specialising and miss out on parts? Brian Squibb - still remembering how simple VB1 was
-
Some years ago Visual Studio was the best in class tool. Nowadays I love using Eclipse for Java or SharpDevelop for .NET development because VS2005 never ran smoothly. Every part of it is slow compared to Eclipse.
Buy a faster workstation? :-D
-
martin_hughes wrote:
Is anyone else considering skipping the VS2008 generation? Or becoming a late adopter?
I'm jumping in. The CLR is still at Version 2.0, it is just the C# compiler (3.0) and .NET Framework (3.5) that are the big changes. VS2008 also has support for multiple versions of the framework, so I can ditch VS2005 yet still work on .NET 2.0 applications.
martin_hughes wrote:
Although there's a lot of cool stuff in .Net 3.5 I can't help but feel that I haven't done .Net 2.0 to death yet.
.NET 3.0 and 3.5 are both additive. They do not change what exists in .NET 2.0. So you still have a chance to do .NET 2.0 to death, although I personally wouldn't restrict myself. The LINQ stuff alone is enough for me to want to upgrade. LINQ is just a few extra classes and some compiler trickery.
martin_hughes wrote:
Also, given the amount of stuff currently coming out of Microsoft, I do wonder whether it's best to wait and see what falls by the wayside
There is a lot I'm waiting to see where it is going first. But for things like WCF I can see immediate advantages. WPF and Silverlight I think will make it, but I'm waiting a bit before I completely jump in on those. WF (Workflow Foundation) is the thing that no one really seems to talk about but is actually quite powerful - Things like the Web Client Software Factory use it.
martin_hughes wrote:
it wouldn't be the first time I've devoted effort to learning something only to see the marketability of such skills divebomb into obscurity.
Been there, done that, then I re-entered the MS world and I've been fairly safe ever since.
Upcoming FREE developer events: * Glasgow: SQL Server Managed Objects AND Reporting Services ... My website
Colin Angus Mackay wrote:
I'm jumping in. The CLR is still at Version 2.0, it is just the C# compiler (3.0) and .NET Framework (3.5) that are the big changes. VS2008 also has support for multiple versions of the framework, so I can ditch VS2005 yet still work on .NET 2.0 applications.
That's the main reason I plan to upgrade to VS2008 as soon as possible. Multi-targeting should have been included in VS2005 in my opinion...
If you truly believe you need to pick a mobile phone that "says something" about your personality, don't bother. You don't have a personality. A mental illness, maybe - but not a personality. - Charlie Brooker My Blog - My Photos - ScrewTurn Wiki
-
Buy a faster workstation? :-D
In previous versions Eclipse was slow and VS was fast. Now it is vice versa, which is another hint, that the Java IDEs made a great leap forward while MS did not do their job well. It is the same with SQL Server Management Studio: While having some nice new functions it is so bloated that it annoys me whenever I use it. And my machine is not too bad (Pentium D 2,8GHz with 2GB RAM) Both .NET and Java have its Pros and Cons but today it makes more fun to code with Eclipse and Java then with VS2005 and .NET. Therefore I will skip VS2008 and concentrate on OpenSource J2EE. But as soon as .NET will again be more fun to use I may be changing sides again ;)
-
Or becoming a late adopter? Although there's a lot of cool stuff in .Net 3.5 I can't help but feel that I haven't done .Net 2.0 to death yet. Also, given the amount of stuff currently coming out of Microsoft, I do wonder whether it's best to wait and see what falls by the wayside, for instance WPF - from what I've seen people on CodeProject do with it it looks very cool... but it wouldn't be the first time I've devoted effort to learning something only to see the marketability of such skills divebomb into obscurity.
Me: Can you see the "up" arrow? User:Errr...ummm....no. Me: Can you see an arrow that points upwards? User: Oh yes, I see it now! -Excerpt from a support call taken by me, 08/31/2007
My main development is in unmanaged C++ (not using MFC) - I'm still pretty happy with VS2003 - there's not much to attract a C++ developer to later versions - more features in the debugger, checked iterators in STL. In addition, my main development machine runs Windows 2000, so can't actually run VS2008 - there's another good reason :-O.