Yet another change I have encountered while migrating our environment to the
VS.NET 2003 and the 1.1 Framework is the change of the class
BaseCodeGeneratorWithSite from public to internal.
For those of u who did not encounter it I can just say that it is used for
building custom tools, and a sample can be found in the MSDN
magazine.
Those of u who already used it (like me) will have to face the fact that
Microsoft has decided that the class is to be internal in the VS.NET 2003, so u
can’t use it any more that way, but, a small search in got dot net revealed a little magic - The
full source code of the class for the developers who have been using the
class in the previous version.
A week ago while I tried the new 1.1 framework on our web project, I have
encounter a strange unexplainable behavior.
Thou I could not explain it
exactly; it was definitely a change of behavior between the 1.0 and the 1.1
framework.
A few breakpoints and some call stacks after, I discovered that a call to
HttpServerUtility.Transfer(string path) is translated in 1.0 to
HttpServerUtility.Transfer(string path, bool perserveForm = false) and in
1.1 to HttpServerUtility.Transfer(string path, bool perserveForm =
true).
With
a little help of Anakrino(www.saurik.com) u
can see the difference more easily
Framework 1.0
public void Transfer(string
path)
{
bool local0;
Page
local1;
local0 = true;
local1 = this._context.Handler as Page;
if (local1 != null
&& local1.IsPostBack)
local0 = false;
this.Transfer(path, local0);
}
Framework
1.1
public void Transfer(string
path)
{
this.Transfer(path, true);
}