Good day,
Excuse my beginner's english, please
So, my problem:
Our applications are developed in Visual Studio 2003 to use framework version 1.1. We use our own authentication/authorizacion system shared
between ASP ( called through COM interop ) and ASP.NET ( directly called assembly class from GAC ). The way the applications share
authentication information is a string-formatted ticket, made from a class serialized to a string form by BinaryFormatter, then Base64...
All has been working fine until framework 2.0 is installed on the computer. Since that time the system doesn't work because of serialization
differences between the two versions of framework. I've found that COM interop uses the highest framewrok verison installed, but the others
(ASPX GAS assemlby calls) still framework 1.1 (the runtime it was designe in and for). Now - when tehere is a serialized ticket created
through COM interop call given to ASPX to recognize logged user, it throws exception: System.ArgumentOutOfRangeException: "Ticks must be
between DateTime.MinValue.Ticks and DateTime.MaxValue.Ticks. Parameter name: ticks" ( throwed inside BinaryFormatter.Deserialize() ).
I was searching google and found there are two choices to solve:
1. get a repair package from Microsoft, called "Version Tolerant Serialization patch", from Microsoft Product Support Services. It is not a
public patch and it's needed to ask for help with donation ??? ( more here: )
2. Make the framework - by some way - to use framework runtime version 1.1 for COM interop calls, or better : for one concrete assembly in
GAC. I've tried publisher policy, Framework Wizards, Assembly Configuration Tool, but with no success.
3. Uninstall the 2.0 version of framework. It would solve our problems, but we need it to be installed for another applications.
4. Make other appliactions using Authentication component to use framework 2.0. - it isn't soulution for we haven't developer tools for this
runtime and maybe some old applications should have been upgraded. But it would be the only soulution for us if we don't find a better one.
I'm trying it here to ask for solution, for it has been answered nowhere i have posled my problem description.
Have a nice day, dear reader(s)...
Ondrej Kalab, Czech Republic.
Excuse my beginner's english, please
So, my problem:
Our applications are developed in Visual Studio 2003 to use framework version 1.1. We use our own authentication/authorizacion system shared
between ASP ( called through COM interop ) and ASP.NET ( directly called assembly class from GAC ). The way the applications share
authentication information is a string-formatted ticket, made from a class serialized to a string form by BinaryFormatter, then Base64...
All has been working fine until framework 2.0 is installed on the computer. Since that time the system doesn't work because of serialization
differences between the two versions of framework. I've found that COM interop uses the highest framewrok verison installed, but the others
(ASPX GAS assemlby calls) still framework 1.1 (the runtime it was designe in and for). Now - when tehere is a serialized ticket created
through COM interop call given to ASPX to recognize logged user, it throws exception: System.ArgumentOutOfRangeException: "Ticks must be
between DateTime.MinValue.Ticks and DateTime.MaxValue.Ticks. Parameter name: ticks" ( throwed inside BinaryFormatter.Deserialize() ).
I was searching google and found there are two choices to solve:
1. get a repair package from Microsoft, called "Version Tolerant Serialization patch", from Microsoft Product Support Services. It is not a
public patch and it's needed to ask for help with donation ??? ( more here: )
2. Make the framework - by some way - to use framework runtime version 1.1 for COM interop calls, or better : for one concrete assembly in
GAC. I've tried publisher policy, Framework Wizards, Assembly Configuration Tool, but with no success.
3. Uninstall the 2.0 version of framework. It would solve our problems, but we need it to be installed for another applications.
4. Make other appliactions using Authentication component to use framework 2.0. - it isn't soulution for we haven't developer tools for this
runtime and maybe some old applications should have been upgraded. But it would be the only soulution for us if we don't find a better one.
I'm trying it here to ask for solution, for it has been answered nowhere i have posled my problem description.
Have a nice day, dear reader(s)...
Ondrej Kalab, Czech Republic.