Hi Rebecca,

Would you mind zipping up your solution so we can take a look at it?
There's a few ways that you can debug assembly load failures, one of them is to 
use the fusglogvw tool, which will show you all of the .NET assemblies being 
loaded by the CLR.  I suggest running that, enabling it, and try produce your 
load failure.  Then take a look in fuslogvw to see if there was an attempt to 
load the type - it may be missing another assembly that you are referencing 
from it (anything else being referenced?).

Also, you can check your eventvwr and STS logs, and see if there's anything 
interesting in there.

I have never written one of these before so I don't know the exact details - 
but perhaps in your manifest you are listing the incorrect type name 
(spelling/case) perhaps you need to make sure the public key token is correct?

M

Matthew Cosier
Readify | Dev Centre Lead
M: +61 401 932 250 | E: [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]> Blog: 
http://cosier.wordpress.com<http://cosier.wordpress.com/>

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rebecca Thornton
Sent: Thursday, 14 August 2008 4:33 AM
To: [email protected]
Subject: [OzMOSS] "Could not load type" error

Hi all.  Thanks for your suggestions re: the dynamic columns.  I still haven't 
managed to get those working yet, although mainly because I've been given 
something else to work on instead.  :)

I'm now trying to create the configuration page for a custom Information 
Management Policy, based on the Watermark policy example in chapter 8 of the 
Inside MOSS 2007 Microsoft Press book.  The policy itself (i.e. without edit 
page) seems to work okay, but whenever I try to access the Policy Edit page 
for, say, a content type, I get an error in SharePoint: "Could not load type 
'PolicyTest.Watermark.WatermarkPolicySettings'".  The namespace and class names 
are correct (the namespace is PolicyTest.Watermark, and the class 
WatermarkPolicySettings).

I have copied the ascx to the \12\TEMPLATE\LAYOUTS directory, and the DLL 
containing the code-behind is in the GAC (and is visible to SharePoint: all of 
the activation / registration code is in the same assembly, and that is working 
fine).  I haven't included any paths to the ascx in the RootFiles or 
TemplateFiles section of the WSP's manifest, mainly because I was getting an 
error there too.

I have tried searching and comparing my code to various online examples, but 
can't find any hints as to why SharePoint can't see the class.  Any help would 
be greatly appreciated: I have been on this same exercise for days and am 
completely at a loss as to what to try next.

By the way, I am using Visual Studio 2005 with VSEWSS 1.1, and MOSS 2007.


--
Rebecca
------------------------------------------------------------------- OzMOSS.com 
- to unsubscribe from this list, send a message back to the list with 
'unsubscribe' as the subject.
Powered by mailenable.com



------------------------------------------------------------------- OzMOSS.com 
- to unsubscribe from this list, send a message back to the list with 
'unsubscribe' as the subject.

Powered by mailenable.com

Reply via email to