Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8465123
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 10, 20262026-06-10T14:57:08+00:00 2026-06-10T14:57:08+00:00

Visual Studio fails to build the solution S1 with this error message: Error 8:

  • 0

Visual Studio fails to build the solution “S1” with this error message:

Error 8: The referenced assembly “D:\S0\foo\bin\Debug\foo.dll” was not
found. If this assembly is produced by another one of your projects,
please make sure to build that project before building this one.

The referenced foo project is in fact originally part of a different solution (called S0 as seen in the error message) and got included via “Add existing project”.

However, Foo did build fine in S0 and its bin output exists. Since both S0 and S1 exclusively build for x86, the correct path should be “S0\foo\bin\x86\Debug\foo.dll”, so it appears Visual Studio does not look for the binary file in the right place.

Foo does show missing references in S1, likely due to its references to other projects from S0 which are not included in S1. This should not be an issue though, since the required binary files already exist.

I manually copied the files from ‘bin\x86\Debug’ to ‘bin\Debug’ and while not removing the warnings about missing references, this actually made VS build S1 fine, so apparently Visual Studio actually got confused by the “unusual” ‘bin\x86\debug’ path.

How should I solve this issue?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-10T14:57:09+00:00Added an answer on June 10, 2026 at 2:57 pm

    Your build output location is customisable. I believe the standard VS behaviour is to create the x86 folder if other platform configurations exist for the project.

    This isn’t a Visual Studio bug; it sounds like (although the project is in the solution) you have a binary reference that has been created with an incorrect path.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

When a compile fails in VB.NET in Visual Studio 2008, an Error List pops
In Visual Studio, you can unload a project, and when you build the solution
I have a visual studio solution whith (roughly speaking) the following layout: Common.dll Proja
Ok, so, my visual studio is broken. I say this NOT prematurely, as it
I can build locally with Visual Studio 2010, but our automatic builds fail reading
Visual Studio Team system 2008 crashes without any error messages whenever I try to
Visual Studio 2008 insists on indenting HTML like this: <h1> title</h1> <h2> subtitle</h2> where
Visual studio 2005: I am moving from post build event to using the external
Getting following build error: error X2230: the type 'ASA.Log.ServiceLogger.IASALog' is in assembly 'ASA.Log.ServiceLogger' that
I have three Visual Studio solutions. The first is configured to build as Release

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.