For the moment we’re still working with the 2.0 framework and and although 2.0 provides all the necessary we need for the moment, we’ll have to move on to 3.5 sooner or later.
The other day there was an in house discussion going on whether there is any risk involved in this upgrade, and this risk was not to be taken lightly since all our clients are still using the 2.0 framework.
There was a colleague who stated that it would be safer to just recompile all our products against the 3.5 framework en do complete new roll out. This would tackle any compatibility issues.
A lot of work indeed and maybe unnecessary, I believe that wen Microsoft grantees that the framework is backward compatible why should we have any doubts about it?
Am I right about this?
For the moment we’re still working with the 2.0 framework and and although 2.0
Share
It isn’t 100%…. most importantly, 3.5 and 3.5SP1 both include service packs to 2.0 and (later) 3.0; these changes aren’t all trivial.
As a key one; if you start using types in SP1 even in what you think is 2.0, it will fail on a “proper” 2.0 client. There is an FX cop tool to help avoid this, IIRC. Second, there are (in the service pack) changes to things deep in the core – the number of pool threads, for example (or is it the stack size of pool threads… something in that area) that can bite you if you are unlucky.
Also, there are bug-fixes in the 2.0 code; if you happen (by chance) to be relying on a behaviour that changes in the service pack (SP1/SP2)…
But also don’t forget that you have this problem now; if your clients have installed .NET 3.5, then they have taken the 2.0 service pack(s) ;-p
So don’t completely dismiss it – but if you take suitable precautions (with testing) and it should be achievable.