VS2005: Assembly '<assembly>' is incorrectly specified as a file.

visual-studio visual-studio-2005 build assemblies log4net
Ian Boyd picture Ian Boyd · Jan 12, 2009 · Viewed 25.7k times · Source

I've added a reference to the log4net assembly dll to my project.

When I build I get a warning saying:

Warning Assembly 'Lib\log4net.dll' is incorrectly specified as a file.

I look up the help for this error on MSDN, and it says:

This warning is generated during application manifest generation when the build process detects that a file reference is actually a (managed or native) assembly.

This is exactly what I'm doing; the file reference is an assembly. What am I being told here?

How do I add a reference to an assembly dll, while not adding a reference to an assembly dll?

Answer

Muhammad Ousama Ghazali picture Muhammad Ousama Ghazali · May 28, 2009

Try setting the Build Action property of the source DLLs to None. It solved the issue for us.

Related questions

How to fix "Referenced assembly does not have a strong name" error?

I've added a weakly named assembly to my Visual Studio 2005 project (which is strongly named). I'm now getting the error: "Referenced assembly 'xxxxxxxx' does not have a strong name" Do I need to sign this third-party assembly?

Read More
What is the difference between Release and Debug modes in Visual Studio?

Possible Duplicate: Debug vs. release in .NET Debug/Release difference What is the difference between Release and Debug modes in Visual Studio while building a project?

Read More
How do I print to the debug output window in a Win32 app?

I've got a win32 project that I've loaded into Visual Studio 2005. I'd like to be able to print things to the Visual Studio output window, but I can't for the life of me work out how. I've tried 'printf' and …

Read More