Is anyone else considering skipping the VS2008 generation?
-
I'd love to dive right in but the company I work for is almost completely web service based & hence I never get to work with WPF, Silverlight, LINQ or any other of the new features during my normal day to day routine. That said, however, I do plan to do a few projects for myself (even if they never see the light of day) just to stay current. That I'm mad about technology is a bonus :D
But fortunately we have the nanny-state politicians who can step in to protect us poor stupid consumers, most of whom would not know a JVM from a frozen chicken. Bruce Pierson
Because programming is an art, not a science. Marc CliftonDave Sexton wrote:
I'd love to dive right in but the company I work for is almost completely web service based
What about WCF? My company have its first WCF project entering its final phases just now and so far it looks like it was the right choice.
Upcoming FREE developer events: * Glasgow: SQL Server Managed Objects AND Reporting Services ... My website
-
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
The C++ standard will come until mid-to-late 2009. No more improvements for native C++, so there's no need for me to get VC9. Besides, I already spent many many many bucks with VC8 and frankly I'm not willing to spend more if I don't need to.
Hope is the negation of reality - Raistlin Majere
-
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 used to be a total early adopter and I always promoted the new stuff to others when it came out, now I'm a totally late adopter/attempted skipper. I tried to skip Windows XP but they conspired against me. I love .Net 2.0 and I also feel I haven't explored the entirety of it along with VS2005 (which I adopted late). I managed to mostly skip VS2003, but I found I was behind and needed to do a lot of catchup to be fluent with .Net 2.0 and VS2005 They'll probably conspire against my late adoption of Vista/VS2008 but I'm going to make them work hard for it :) WPF, what little I know of it, still looks like a work in progress to me. I mostly want to stay in the region of the majority of the installed base...when they can honestly say that it's Vista/VS2008, then I'll take the plunge.
-
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 don't even use VS for my personal needs, and at work the decision won't be mine anyway :)
-
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 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:
-
I don't even use VS for my personal needs, and at work the decision won't be mine anyway :)
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
-
Dave Sexton wrote:
I'd love to dive right in but the company I work for is almost completely web service based
What about WCF? My company have its first WCF project entering its final phases just now and so far it looks like it was the right choice.
Upcoming FREE developer events: * Glasgow: SQL Server Managed Objects AND Reporting Services ... My website
I've been thinking of doing up a demo over December (if I'm not working) to use in a proposal in the new year. We've been really busy over the past few months, made a bit of a name for ourselves & were also recently bought (yay!) by a much bigger company so it's been a little crazy lately. Since we work with online payment processing we don't use any technology that's still in beta in our production environment. Best case scenario for WCF (that I can currently predict without any real metrics) is probably early to mid 2009 if we continue as we are currently. Quite possibly sooner but I prefer to under promise & over deliver.
But fortunately we have the nanny-state politicians who can step in to protect us poor stupid consumers, most of whom would not know a JVM from a frozen chicken. Bruce Pierson
Because programming is an art, not a science. Marc Clifton -
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
Too much of what I see is half-baked, unecessary syntactical sugar, and unecessary for my work paradigm. I don't see anything that actually improves my current (what I consider high level of) productivity in terms of architecture or implementation. Until I do, I'll look on as to what others are doing with great curiosity and I'll certainly test my existing code base with VS2008 and .NET 3.5, but I'll probably live in VS2005 land unless there's a marked improvement to the IDE/debugger experience. Marc
-
I used to be a total early adopter and I always promoted the new stuff to others when it came out, now I'm a totally late adopter/attempted skipper. I tried to skip Windows XP but they conspired against me. I love .Net 2.0 and I also feel I haven't explored the entirety of it along with VS2005 (which I adopted late). I managed to mostly skip VS2003, but I found I was behind and needed to do a lot of catchup to be fluent with .Net 2.0 and VS2005 They'll probably conspire against my late adoption of Vista/VS2008 but I'm going to make them work hard for it :) WPF, what little I know of it, still looks like a work in progress to me. I mostly want to stay in the region of the majority of the installed base...when they can honestly say that it's Vista/VS2008, then I'll take the plunge.
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
-
Too much of what I see is half-baked, unecessary syntactical sugar, and unecessary for my work paradigm. I don't see anything that actually improves my current (what I consider high level of) productivity in terms of architecture or implementation. Until I do, I'll look on as to what others are doing with great curiosity and I'll certainly test my existing code base with VS2008 and .NET 3.5, but I'll probably live in VS2005 land unless there's a marked improvement to the IDE/debugger experience. Marc
Marc Clifton wrote:
unless there's a marked improvement to the IDE/debugger experience.
One thing that looks promising is the improved debugging experience for multithreaded apps[^]. The "step into .NET framework source" may prove useful as well.
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'm wanting LINQ. It will really help simplify much of our code where we manipulate lists, collections, arrays, etc. Rather than custom loops all over the place, a simple LINQ query will do the trick. Nice and concise. We use a lot of anonymous methods too...the more terse lambda will improve readability. The built-in extension methods on IEnumerable<T> are really nice and will help improve code readability. So I'm an early adopter this time.
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
-
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.