I was the one who reported that the RadCompression module in build 1314 did not work with Medium Trust last week.
And so you released a new build 1316, and then yesterday 1319.
However, I found that both new builds (1316 and 1319) do not work at all with ASP.NET 3.5, but work fine with ASP.NET 3.5 SP1.
Then I submit another support ticket reporting this issue, and got this kind of response:
====
in order to use our RadScriptManager in .Net 3.5 environment you should use latest framework's service pack.
Please excuse us for the inconvenience.
====
This is not just an inconvenience!
I am building an application on top of ASP.NET 3.5 for clients, and it is not possible to ask all our clients to suddenly upgrade to SP1!!
Build 1314 works fine with 3.5, but not 1319?
I was just asking you guys to support RadCompression in medium trust, and all of a sudden you changed the system requirements to 3.5 SP1 only??
The new builds simply do not work, whether or not I choose to enable RadCompression.
This is just plain ridiculous.
And so you released a new build 1316, and then yesterday 1319.
However, I found that both new builds (1316 and 1319) do not work at all with ASP.NET 3.5, but work fine with ASP.NET 3.5 SP1.
Then I submit another support ticket reporting this issue, and got this kind of response:
====
in order to use our RadScriptManager in .Net 3.5 environment you should use latest framework's service pack.
Please excuse us for the inconvenience.
====
This is not just an inconvenience!
I am building an application on top of ASP.NET 3.5 for clients, and it is not possible to ask all our clients to suddenly upgrade to SP1!!
Build 1314 works fine with 3.5, but not 1319?
I was just asking you guys to support RadCompression in medium trust, and all of a sudden you changed the system requirements to 3.5 SP1 only??
The new builds simply do not work, whether or not I choose to enable RadCompression.
This is just plain ridiculous.