Tuesday, March 27, 2007

Assembly Name or Codebase Invalid Errors

So I've finally recovered from a self-inflicted wound that's lost me more time than I'm willing to admit.  I’m working on a custom field type for MOSS and had been running in to issues when trying to create the field.  I kept getting the error:

The given assembly name or codebase was invalid. (Exception from HRESULT: 0x80131047)

What was the cause?  See if you can spot the difference between:

<Field Name="FieldTypeClass">

    NuSoft.LinkedStandardsCFTField,

    LinkedStandardsCFT,

    Version 1.0.0.0,

    Culture=neutral,

    PublickKeyToken=9f4da00116c38ec5

</Field>

and this:

<Field Name="FieldTypeClass">

    NuSoft.LinkedStandardsCFTField,

    LinkedStandardsCFT,

    Version=1.0.0.0,

    Culture=neutral,

    PublickKeyToken=9f4da00116c38ec5

</Field>

Yes, it’s the missing equals sign in the version part.  OK, so I’m the dumbass who mistyped that, but wouldn’t it be great if the tools helped you figure out those sorts of errors before you build and deploy?

Leaving these sorts of important bits and pieces in free-text elements just doesn’t make sense to me.  Why not have them in a schema-defined structure, either as their own elements or attributes?

Bah.

at

8 comments:

  1. Anonymous10/18/2007 12:01 AM

    Funnily enough your post help me track down a similar problem. It created the spark that allowed me find what had cost me a good few hours!

    Cheers

    ReplyDelete
  2. Anonymous12/05/2007 8:08 PM

    Well, today you were someone's hero. Thanks! Thanks!

    ReplyDelete
  3. Anonymous2/22/2008 11:14 PM

    Oh, dude I had done almost exactly the same thing in an ASP.Net web.config file. In my case, I had replaced the "=" sign with a ".". Rather obvious when I saw it, but do you think I could spot it among all that clutter of XHTML? No way, no matter how hard I looked! Your comment is right on the mark. Thanks, you saved me some serious frazzling! D.S. in Halifax, NS

    ReplyDelete
  4. Anonymous3/11/2008 4:58 PM

    Ditto! Same exact problem as you had. So obvious when you see it; so elusive when you don't.

    ReplyDelete
  5. Anonymous1/21/2009 2:05 AM

    Wonderful post!
    In my case it was a space in this

    Version=2.0 .0.0

    should be

    Version=2.0.0.0

    Darn thing Cost me a few hours!

    Hilary

    ReplyDelete
  6. MacroSloth3/26/2010 3:59 PM

    Thanks so much. I did the exact same thing and couldn't see it till I read your post. It cost me an hour but I think you saved me a couple more.

    ReplyDelete
  7. Mr. Putty4/19/2011 7:08 PM

    Add me to the list of appreciative fans. I was missing a comma, but your example gave me an idea what I might be looking for.

    ReplyDelete
  8. Anonymous9/10/2012 1:59 PM

    I have been a dumbass too: Forgot the '=' ,... ;-)

    Thanks for your post.

    Michael B.

    ReplyDelete