Guys,
We have an error thrown below
1) Exception Information
*********************************************
Exception Type: System.TypeLoadException
Message: Method CreateFromTaskID in type
Tranmit.Sprinter.Approval.Interop.ApprovalTaskFactory from assembly
Tranmit.Sprinter.Approval.Interop, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=a7e947bc8958e994 does not have an implementation.
TypeName: Tranmit.Sprinter.Approval.Interop.ApprovalTaskFactory
I've used ildasm and it looks like the assembly does have the correct method
so my next thought was to use fusion binding log viewer to enable ForceLogs
to ensure all assembly binds are reported as I wanted to find out the full
path of the file which was loaded by the CLR.
Unfortunately the fusion binding log viewer doesn't report any assemblies in
the viewer.
Any ideas why?
Cheers
Matt
Matt Adamson - 12 Sep 2006 06:42 GMT
I need some help on this urgently, shall I post to a different newsgroup, if
so which one?
I tried microsoft.public.vsnet.debugging who suggested posting to this one.
> Guys,
>
[quoted text clipped - 25 lines]
>
> Matt
Oleg Starodumov - 12 Sep 2006 07:37 GMT
Try to compare your setup with the information here:
http://www.grimes.demon.co.uk/workshops/fusWSFive.htm#Example_5_1
(the path to the log would be my first suspect)
If it does not help, you can try using FileMon to see where the file
is loaded from.
Oleg
http://www.debuginfo.com/
Matt Adamson - 13 Sep 2006 12:59 GMT
Thanks Oleg,
Yes interestingly if the log path specified in the registry isn't created it
won't be automatically created.
Creating the path has now at least allowed the log files to be produced
although the viewer still doesn't display any results.
> Try to compare your setup with the information here:
> http://www.grimes.demon.co.uk/workshops/fusWSFive.htm#Example_5_1
[quoted text clipped - 5 lines]
> Oleg
> http://www.debuginfo.com/