Invalid module qualification: Failed to resolve assembly N2.Edit & N2.Security

Jul 8, 2008 at 10:22 PM
In the web.config I get these error's since 1.4:
Invalid module qualification: Failed to resolve assembly N2.Edit on

        <siteMap defaultProvider="PublicSiteMap">
            <providers>
                <add name="PublicSiteMap" type="N2.Web.PublicSiteMapProvider, N2" startPageIsRoot="true"/>
                <add name="EditSiteMap" type="N2.Edit.Web.EditSiteMapProvider , N2.Edit" startPageIsRoot="false"/>
                <add name="FileSiteMap" type="N2.Edit.Web.FileSiteMapProvider, N2.Edit" startPageIsRoot="false"/>
            </providers>
        </siteMap>
and
Invalid module qualification: Failed to resolve assembly N2.Security on
        <membership defaultProvider="ContentMembershipProvider">
            <providers>
                <clear/>
                <add name="ContentMembershipProvider" type="N2.Security.ContentMembershipProvider, N2.Security"/>
            </providers>
        </membership>
        <roleManager enabled="true" defaultProvider="ContentRoleProvider">
            <providers>
                <clear/>
                <add name="ContentRoleProvider" type="N2.Security.ContentRoleProvider, N2.Security"/>
            </providers>
        </roleManager>

any ideas?
Coordinator
Jul 9, 2008 at 3:53 AM
Are those assemblies in /bin?
Jul 9, 2008 at 8:54 AM
yes, they are (but not referenced)
Coordinator
Jul 10, 2008 at 4:20 AM
Maybe some version mismatch? what are the version numbers of n2, n2.security and n2.edit?

You may also remove EditSiteMap and FileSiteMap they are not needed anymore.
Jul 10, 2008 at 7:51 AM

Maybe some version mismatch? what are the version numbers of n2, n2.security and n2.edit?
all are 1.4.0.0 ...


You may also remove EditSiteMap and FileSiteMap they are not needed anymore.
I figured so, did I miss that somewhere?


Jun 22, 2009 at 6:14 PM

I got exactly the same error message "Invalid module qualification: Failed to resolve assembly …",

My assembly is in the /bin folder and the assembly is not used until run time. I don’t think it is version issue. If I changed the assembly that is referenced during the Asp.net startup, the error message will go away.  

This post has no final solution. It has been a year, did original poster MartijnRasenberg find the solution? Or a work around?

Coordinator
Jun 22, 2009 at 8:03 PM

Out of curiosity. How does this error manifest itself (is it an exception) and how do you change the the assembly? Do you have any old assemblies referencing older versions of N2?

Jun 23, 2009 at 6:20 PM

I add the following XML code into web.config file

 

 

 

 

 

 My situation has nothing to do with N2. but exerctly the same scenario.

I added xml code to the web.config file like this:

   <system.runtime.serialization>
    <dataContractSerializer>
      <declaredTypes>
        <add type="XCoreDataObject, XCore.CommonData">
          <knownType type="ResultObject, XCore.StubLib"/>
        </add>
      </declaredTypes>
    </dataContractSerializer>
  </system.runtime.serialization> 
<font color="#0000ff">

The error message (Invalid module qualification: Failed to resolve assembly XCoreCommonData)  displayed when my mouse is over the XCore.CommonData. No error message displayed over XCore.Stublib as it is a dll that is used during the ASPNET startup. Both dlls are in the /bin folder.

</font>