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

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 18, 20262026-05-18T00:12:23+00:00 2026-05-18T00:12:23+00:00

I have an old project that was build on VS 2008 .NET 2.0. The

  • 0

I have an old project that was build on VS 2008 .NET 2.0. The project is running fine. We upgraded the project on dev side to VS 2010 .NET 3.0. Now, my question is that if I upload the new 3.0 assemblies on the production will it work. Will some .NET 2.0 assemblies be able to communicate with the .NET 3.0 assembly? Our push to production is a simply DLL (3.0) push and on production most of the assemblies are .NET 2.0.

I think it should work since .NEt 2.0 and .NEt 3.0 share the same codebase. If it was .NET 4.0 then it would be totally different.

  • 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-18T00:12:24+00:00Added an answer on May 18, 2026 at 12:12 am

    Yes. They will work together: .net 3.0 = .net 2.0 + WCF+WPF+WF

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

Sidebar

Related Questions

I have a very large project that uses Oracle ODP.NET. Right now it is
I have an old C project that compiles just fine in Unix. I want
I have an old project that is mixed C and C++. It makes extensive
I have a very old project that includes the source from another project directly,
I have an old project at our company that uses shell scripting a lot.
I have an old EJB (2.1) project that uses xdoclet (1.2.3) to generate the
I have a project that takes about 15 minutes to run its build in
We're running Visual SourceSafe 6.0 (build 8163). In one project, there's an old label
We have an old project that is set up like this: . ├── customizationProject
I have an old C++ project and I'm having problem building it. For a

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.