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

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 12, 20262026-05-12T08:44:20+00:00 2026-05-12T08:44:20+00:00

I am upgrading project from 1.1 to 3.5. There are some references left to

  • 0

I am upgrading project from 1.1 to 3.5.
There are some references left to .NET 1.1 assemblies.

The question is:
Do I have the requirement now to have both .NET 1.1 and 2.0 (3.5) on the deployed machine or it can be run without 1.1?

Cheers,
Dmitriy.

  • 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-12T08:44:20+00:00Added an answer on May 12, 2026 at 8:44 am

    If you are referencing a specific version of the assembly (i.e. Specific Version is set to true in the properties of the references) then yes, you will need both.

    If you are not referencing specific versions, then no, you will not need both, and your application should be able to use the 3.0 assemblies (although you take your chances by not testing it specifically with 3.0!)

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

Sidebar

Related Questions

I am upgrading current project from Roo 1.1.5 to 1.2.1. I have noticed there
We're upgrading a project from Sitefinity 3.7 to 4.4 and some of our controls
Consider the scenario of upgrading an ASP.NET MVC project. This question is around up-converting
Upgrading from ASP.NET WebAPI Beta to RC has provided some amount of excitement and
I'm upgrading a project from NServiceBus 2.6 to 3.0. We have code similar to
After upgrading a working project from EF 4.0 to 4.1, I am now receiving
I have a project that I'm upgrading from 2008 to 2010. My problem is
I'm running into an issue upgrading a project to .Net 4.0...and having trouble finding
I have an InstallScript project written from scratch in InstallShield 2010. It contains, amongst
I have been using massive Massive Lib (github) for asp.net 4 project. I have

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.