Share via


An assembly must have a 'dll' extension in order to be referenced???

And how did I get such a useful error you might ask?  By trying to add a reference to a project that is in the same solution in VS.Net 2003.  The project I'm trying to reference is a class library and when I open the project by itself, it builds perfectly fine.

I've got 3 different class library projects added to this solution of mine and 2 of them added as references just fine, it's this 3rd one that's giving me trouble.  Can anyone offer a suggestion as to what to check for this?

I can workaround it for now by just adding the .dll itself, but I'd rather have the project in the same solution for ease of debugging...

Comments

  • Anonymous
    February 25, 2005
    You've built it as a "exe" assembly, not a "library" assembly. Change the project properties. Stupid VS.NET bug (IMO).

  • Anonymous
    February 25, 2005
    The project properties are set to build it as a .dllI had checked that already. :) Thanks for the suggestion however.

  • Anonymous
    June 15, 2005
    The comment has been removed

  • Anonymous
    July 10, 2006
    Thanks Dane!

    BTW, you can delete the guid in the csproj file and VS with generate a new one for you.

  • Anonymous
    January 22, 2007
    Thanks Dane - your fix has just sorted as well!

  • Anonymous
    June 19, 2007
    > two projects with the same guid thx Dane!

  • Anonymous
    August 23, 2007
    You've built it as a "exe" assembly, not a "library" assembly. Change the project properties. Stupid VS.NET bug (IMO). February 25, 2005 4:30 PM THANKS