|
Hi again WaldenThanks for that. I was aware that there were betas, and fully expected that this would be the source of the information. Of course beta is beta and does not set anything in concrete, but I accept that it provides a pretty strong indication of how things will likely be.
Your second comment gets to the heart of what I was getting at. Regards Evan Harris At 09:16 a.m. 22/06/2005, you wrote:
>Another rhetorical question: if the new release of .NET is not out yet, how >do you know now it does not break anything ? Betas, CTPs (Community Technology Previews), and RCs (Release Candidates). Microsoft has always been good at getting code into the developer community's hands LONG before the code goes RTM (Released To Manufacturing). However, I must say that Steve is not correct. 2.0 does break some things from 1.1. However, the list is well documented, and has been available for a while. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetde p/html/listofbreakingchanges.asp -Walden
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
