[Mono-aspnet-list] Project References broken in compiled DLLs

Nathan Bridgewater nathan at integratedwebsystems.com
Mon Aug 9 10:52:26 EDT 2010

This is a shot in the dark, but I had some problems like this lastnight when
configuring DbProviders for SQLite on linux/mono.  The problem ended up
being the assembly filename's casing. I know you're not using SQLite, but
this follows the same rules for all types of references.

I had System.Data.SQLite.DLL  and not System.Data.SQLite.dll.    Switching
the filename to use a lowercase extension worked.

I also noticed in your message you entered BLL in an assembly reference. I'm
guessing it's a typo. Assembly references typically use the Assembly Name,
which excludes the extension. Here, for example, is my reference related to
the db providers I mentioned earlier.

<...  type="System.Data.SQLite.SQLiteFactory, System.Data.SQLite"/>

For many situations, you can leave out the version and signature and just
follow the pattern "{fully qualified class name}, {assembly name}" as long
as that assembly is accessible to your executable; (either in the GAC, the
PATH or in the same folder), it should be able to find it.

There may also be odd situations where CPU architecture of the assembly will
cause it not to be found. If a .NET assembly is hard-wired to CPU
architecture, then you need to make sure your executable matches that
architecture.  SQLite again is a good example.  If you're running default
.NET compilation on x64 platform, then it will run with native x64 runtime.
If you reference the 32bit SQLite assembly it will give you an error that it
cannot be found. You have to manually reference the x64 SQLite assembly.
Normally this isn't an issue when .NET assemblies are compiled to use ANY

Good Luck!

On Thu, Aug 5, 2010 at 8:31 PM, LordJMann <lordjmann at gmail.com> wrote:

> I am really puzzled as to why this is happening... I have numerous projects
> in a solution (they all compile and everything) and they have varying
> interconnected dependencies (no cyclic dependencies), and then I have a web
> project that uses these libraries. Everything builds properly with project
> dependencies and such, but when you use the Assembly Browser on any of the
> references all their corresponding references in the DLL are "Can't load:"
> and none of them are actually referencing each other, and I receive this
> error when trying to load up my page on the server:
> Could not load file or assembly 'PlayerAuction.BLL, Version=,
> Culture=neutral, PublicKeyToken=null' or one of its dependencies. The
> module
> was expected to contain an assembly manifest.
> It would seem none of them were given assembly manifests. I'm really
> stumped.
> --
> View this message in context:
> http://mono.1490590.n4.nabble.com/Project-References-broken-in-compiled-DLLs-tp2315824p2315824.html
> Sent from the Mono - ASP.NET mailing list archive at Nabble.com.
> _______________________________________________
> Mono-aspnet-list mailing list
> Mono-aspnet-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-aspnet-list


Nathan Bridgewater
Integrated Web Systems, LLC
nathan at integratedwebsystems.com

Microsoft Certified Professional Developer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-aspnet-list/attachments/20100809/de7b1dd6/attachment.html 

More information about the Mono-aspnet-list mailing list