Tuesday, June 05, 2007
What does .NET 3.0 mean for me?
Well if you want to code out a bunch of your own stuff it means you can begin to adopt it now. Maybe we can wait until Visual Studio 2008 for .NET 3.5 to really take advantage of .NET 3.0. As I begin to think about this it really makes sense. When a technology has a the word Framework in it it means to me that the technology is available for production use, but might not be ready for me. I’m a lazy developer and have this idea that the tools should leverage the framework. I’m thinking that maybe we can really start to adopt the newer framework technologies once we have tool support. Now I know a few people where I work embrace the opportunity to jump into the pre-tool support arena. But when you look at how you really roll out a technology for your entire group, I think you really need to take a look at tool support. Maybe next year I can go the “How to leverage development tools to do more with the Framework” presentation. Now that would be awesome.
Subscribe to:
Post Comments (Atom)
1 comment:
Yeah, trying to do something simple with WCF that was outside of the standard Hello World app was excruciating without the right tools and no critical mass of info and articles on the web. Some tool and help file support would go a long way. In fact it turns out that VS addin I was looking for is still CTP even after the framework release. It feels like working with a beta product.
Post a Comment