|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
.NET Adoption StatisticsDoes anyone know where I can find statistical info regarding market share of
..NET? More specifically, current usage of various versions of .NET and how long companies wait before upgrading and migrating. I'm trying to begin an effort to start migrating to .NET 3.0. One argument I've heard against is that most people are still on 1.1 so we're not behind the curve yet. Judging from the people in my circle, I can't believe that. But I can't find any facts to refute it. Thanks for any relevant and verifiable info and ammunition you can provide. :) John 3.0?
I think a lot of people are still on 1.1. Companies are just now starting to move to 2.0, but have not necessarily released products on 2.0 yet It also depends on if it's just a web app that the company hosts - in which case it's much easier to upgrade. If you are talking about a product that is deployed by customers, then it all takes a lot longer. The IT at the customer sites is not as quick to upgrade, and so on. It all takes time. Also, I think some people start the migration process later to give 2.0 some time out there before they feel confident enough to start using it. This is more of a feeling and a sense, I don't have any evidence for it. Show quote "John" <revelation@nospam.nospam> wrote in message news:e9t2nbp1GHA.2176@TK2MSFTNGP04.phx.gbl... > Does anyone know where I can find statistical info regarding market share > of .NET? More specifically, current usage of various versions of .NET and > how long companies wait before upgrading and migrating. I'm trying to > begin an effort to start migrating to .NET 3.0. One argument I've heard > against is that most people are still on 1.1 so we're not behind the curve > yet. Judging from the people in my circle, I can't believe that. But I > can't find any facts to refute it. Thanks for any relevant and verifiable > info and ammunition you can provide. :) > John > Hello John,
Are your applications currently built upon .net framework 2.0? As for .net framework 3.0(originally codename winfx), I did have got that some partners and companeis have begun investigating on them. However, based on my understanding, the .net framework 3.0 is mostly built for leverage of the new features introducted in Vista/LongHorn server. for you application, if it is still targeting the current operating system, I don't think you should be eager to migrate them to .net framework 3.0. I haven't any definite statistical info regarding market share of different version of .net. However, I'm sure only a few Microsoft solution parnters have begun researching on them, and most of them are still working with some prototypes. You can get most latest information about .net framework 3.0 in the MSDN development center: http://msdn.microsoft.com/winfx/ http://msdn.microsoft.com/windowsvista/ Hope this helps some. Sincerely, Steven Cheng Microsoft MSDN Online Support Lead ================================================== Get notification to my posts through email? Please refer to http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif ications. Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/subscriptions/support/default.aspx. ================================================== This posting is provided "AS IS" with no warranties, and confers no rights. Thank you both for your responses. We're using 1.1 for most of our internal
web services, migrating to 2.0 as time permits. All our development is for our own internal use. The WCF is where we could get the most benefit from 3.0, which is why I'd like to start us moving in that direction. But it sounds like we should stay on 1.1. I'm a little confused about that. Why is Microsoft marketing 3.0 so hard, yet recommending we stick with older technologies? John Show quote "Steven Cheng[MSFT]" <stch***@online.microsoft.com> wrote in message news:ZXiRACw1GHA.4916@TK2MSFTNGXA01.phx.gbl... > Hello John, > > Are your applications currently built upon .net framework 2.0? As for > .net > framework 3.0(originally codename winfx), I did have got that some > partners > and companeis have begun investigating on them. However, based on my > understanding, the .net framework 3.0 is mostly built for leverage of the > new features introducted in Vista/LongHorn server. for you application, > if > it is still targeting the current operating system, I don't think you > should be eager to migrate them to .net framework 3.0. > > I haven't any definite statistical info regarding market share of > different > version of .net. However, I'm sure only a few Microsoft solution parnters > have begun researching on them, and most of them are still working with > some prototypes. You can get most latest information about .net framework > 3.0 in the MSDN development center: > > http://msdn.microsoft.com/winfx/ > > http://msdn.microsoft.com/windowsvista/ > > Hope this helps some. > > Sincerely, > > Steven Cheng > > Microsoft MSDN Online Support Lead > > > > ================================================== > > Get notification to my posts through email? Please refer to > http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif > ications. > > > > Note: The MSDN Managed Newsgroup support offering is for non-urgent issues > where an initial response from the community or a Microsoft Support > Engineer within 1 business day is acceptable. Please note that each follow > up response may take approximately 2 business days as the support > professional working with you may need further investigation to reach the > most efficient resolution. The offering is not appropriate for situations > that require urgent, real-time or phone-based interactions or complex > project analysis and dump analysis issues. Issues of this nature are best > handled working with a dedicated Microsoft Support Engineer by contacting > Microsoft Customer Support Services (CSS) at > http://msdn.microsoft.com/subscriptions/support/default.aspx. > > ================================================== > > > > This posting is provided "AS IS" with no warranties, and confers no > rights. > > > > > Hi John,
Thanks for the reply. Of course, we're not recommending you stick with older technologies, just means it is not necessary to migrate code immediately since the WINFX/VISTA is still under preview before release. Of course, WCF is a powerful distributed technology introducted in the .net framework 3.0, you're welcome to adopt it into your system. However, as I mentioned earlier, it is recommended that you have some investigation and get an overview on it since it has included not only webservice but also othe powerful featuers(WCF is not designed as new version of webservice , but a new communication framework on VISTA/longhorn though also provide support on XP/2003). If you've ever using WSE 3.0 for your .net 2.0 webservice, you'll found WSE 3.0 code modl is completely compatible with WCF. Anyway, if you have interests on WCF or any othe WINFX features, please feel free to let me know. Welcome anytime:) Sincerely, Steven Cheng Microsoft MSDN Online Support Lead This posting is provided "AS IS" with no warranties, and confers no rights.  |
|||||||||||||||||||||||
Other interesting topics