.Net Framework patch Q325699

Does anybody know if this patch (Q325699) has been included into .Net Framework 1.1 ?

This patch fixes:

SYMPTOMS
When you call to an earlier COM component from managed code, you may experience an InvalidCastException exception if the activated COM component idles for more than nine minutes. The following is a typical stack for this exception:

Exception: Caught exception:
System.Reflection.TargetInvocationException:
Exception has been thrown by the target of an invocation. --->
System.InvalidCastException:
QueryInterface for interface xxx failed.
at yyy
--- End of inner exception stack trace ---
at System.Reflection.RuntimeMethodInfo.InternalInvoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean isBinderDefault, Assembly caller, Boolean verifyAccess)
at System.Reflection.RuntimeMethodInfo.InternalInvoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean verifyAccess)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.Reflection.MethodBase.Invoke(Object obj, Object[] parameters)
at yyy in zzz.cs:line nn

(Where xxx is the target interface name, yyy is target method name, and then zzz is the source module that implements the interface.)


CAUSE
After several successful calls, the server stub runs down. This occurs after about nine minutes of idle time. The SafeQueryInterfacecall returns with an HRESULT data type of 0x80010114. 0x80010114 means that
The requested object does not exist
. However, interoperability with COM (COM interop) did not correctly handle the HRESULT: 0x80010114.

Check out:

http://msdn.microsoft.com/library/de...l/sdkstart.asp

for information. It might be listed there.