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

  • SEARCH
  • Home
  • 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 255641
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 11, 20262026-05-11T21:56:52+00:00 2026-05-11T21:56:52+00:00

I have 1 DLL in the .Net 3.5 framework and another in 2.0. The

  • 0

I have 1 DLL in the .Net 3.5 framework and another in 2.0. The ListBoxItem class exists in 2.0 and I have linked the class in the 3.5 DLL in the same namespace.

When I try to compile I get an “exists in both” error. How can I compile this and maintain the same structure.

I don’t want reference the 2.0 DLL to 3.5 to eliminate this problem, I want keep these DLLs separate.

  • 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-11T21:56:52+00:00Added an answer on May 11, 2026 at 9:56 pm

    This doesn’t seem like a good idea no matter what, but change the namespaces and fully qualify your usages.

    Otherwise, why don’t you just reference one dll?

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

Sidebar

Related Questions

I have a project which references another project's dll. They both were in .net
I have a c++ class which needs to interact with a .NET dll using
I have a dll that comes in both 32bit and 64bit version. My .NET
I have an old dll that was compiled against the .NET framework and deployed.
I have created several DLL (.NET) libraries that are used in several projects. In
I have a .Net DLL that I created that implements a WCF client that
I have a .NET DLL containing functions that I can use in PHP. Though
I have a .NET DLL that writes to the Trace. But it seems that
I have some .net dll's and Exe's. I need to pass MSIL files to
I have a .NET 2.0 program that has a reference to Interop.WIA.dll (.NET), which

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.