Are there any potential compatibility issues - backward or forward - that we should be aware of before upgrading our development machines or recommending the upgrade to our customers?
-
-
Besides the list of bugfixes there seem to be no breaking changes...
(unless you rely on functionality that has been fixed of course
) -
Frandsen wrote:Are there any potential compatibility issues - backward or forward - that we should be aware of before upgrading our development machines or recommending the upgrade to our customers?
I don't know one in particular, but there are bugs in 1.0, so those programs that work around 1.0 bugs might have a problem in 1.1. That's just a speculation in my part, no idea which program does work that way, but I do know that 1.0 had bugs which are fixed in 1.1.
-
From what I understand Service Packs for the framework are bug fixes only. I asked the team working on SP3 for 1.0 why they were writing a SP with 1.1 out and 2.0 on the way. They told me they were committed to supported older versions of the framework and that customer's should'nt have to upgrade to a new framework (with possible breaking changes) because of bugs. So far, I'm really impressed with the continued work on the .NET framework. I figured they'd just throw away old versions and not update them.
-
At our place we installed the thing and tested it with all our inhouse developed apps. Not a single issue was uncovered so we rolled it out to the field.
I would say go for it..
Thread Closed
This thread is kinda stale and has been closed but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.