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 6533185
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 25, 20262026-05-25T10:05:39+00:00 2026-05-25T10:05:39+00:00

I originally thought that a reference to a dll was just that, a reference.

  • 0

I originally thought that a reference to a dll was just that, a reference. But it appears the referenced dlls are copied to the bin\debug folder.

How do I prevent this?

  • 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-05-25T10:05:40+00:00Added an answer on May 25, 2026 at 10:05 am

    You can right click on the reference in the solution explorer, and choose “Properties”. One of the options is “Copy Local”. Set that to false, and it won’t copy the assembly.

    Just realize that the assembly must still be discoverable at runtime. This is why it copies it locally by default.

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

Sidebar

Related Questions

Originally, I just want to verify that session_start locks on session. So, I create
Originally: I thought this was a circular reference problem........turns out it's not. The problem
I thought a foreign key meant that a single row must reference a single
I originally thought Python was a pure pass-by-reference language. Coming from C/C++ I can't
Originally I thought to ask if there would be an easy way to provide
Originally I though I'll just take a screenshot of my app on the iPhone
I originally asked this question on RefactorMyCode , but got no responses there... Basically
Currently I have a program that takes as input a folder that contains .MPP
I've been finding that a lot of Github projects use Markdown . I originally
We have a prototype application that was originally published to an external server hosted

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.