Porting applications to the new .NET 2.0
It looks there are issues porting applications from .Net 1.1 to the upcoming 2.0 version. Who did not expect that?
We kind of got used with version differences and things that just stop working after a while. Should I remember CDONTS objects (Windows Email Objects) that are no longer supported and replaced with CDOSYS, or so many other like these ? Some of the changes are justified and constantly pushing for new is understandable, but it looks to me that this "period" since one software version issued until second version shows up and takes over by automatically generating problems for the version one applications, gets shorter and shorter.
They say "portability" is important to Microsoft and they will correct all the issues. Well... this phrase is great but it is based on a wrong supposition: what portability? They call portability when releasing another version of the same software :-)
http://www.eweek.com/article2/0,1759,1820225,00.asp
We kind of got used with version differences and things that just stop working after a while. Should I remember CDONTS objects (Windows Email Objects) that are no longer supported and replaced with CDOSYS, or so many other like these ? Some of the changes are justified and constantly pushing for new is understandable, but it looks to me that this "period" since one software version issued until second version shows up and takes over by automatically generating problems for the version one applications, gets shorter and shorter.
They say "portability" is important to Microsoft and they will correct all the issues. Well... this phrase is great but it is based on a wrong supposition: what portability? They call portability when releasing another version of the same software :-)
http://www.eweek.com/article2/0,1759,1820225,00.asp
posted by Bobby at
12:16 AM
0 Comments:
Post a Comment
<< Home