Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. .NET (Core and Framework)
  4. Do you still need 3.5 if you only install 4.0?

Do you still need 3.5 if you only install 4.0?

Scheduled Pinned Locked Moved .NET (Core and Framework)
questioncsharp
8 Posts 5 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R Offline
    R Offline
    Randar Puust
    wrote on last edited by
    #1

    We have a 3.5 application and are planning on supporting 4.0 in the near future and were wondering if we should just tell our support to only install the 4.0 framework now. The question really is, will a 3.5 application work, with no changes with only the 4.0 framework installed?

    Randar Puust Software Architect, Jonas Software MCSD.Net, MCSE

    L D A 4 Replies Last reply
    0
    • R Randar Puust

      We have a 3.5 application and are planning on supporting 4.0 in the near future and were wondering if we should just tell our support to only install the 4.0 framework now. The question really is, will a 3.5 application work, with no changes with only the 4.0 framework installed?

      Randar Puust Software Architect, Jonas Software MCSD.Net, MCSE

      L Offline
      L Offline
      Lost User
      wrote on last edited by
      #2

      Yes, definitely. Dotnet Framework 4.0 provides backward compatibility. HTH

      Jinal Desai - LIVE Experience is mother of sage....

      L L 2 Replies Last reply
      0
      • L Lost User

        Yes, definitely. Dotnet Framework 4.0 provides backward compatibility. HTH

        Jinal Desai - LIVE Experience is mother of sage....

        L Offline
        L Offline
        Luc Pattyn
        wrote on last edited by
        #3

        really? that is not how I understand it. Unfortunately I can't test it easily right now. :)

        Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]


        I only read formatted code with indentation, so please use PRE tags for code snippets.


        I'm not participating in frackin' Q&A, so if you want my opinion, ask away in a real forum (or on my profile page).


        1 Reply Last reply
        0
        • L Lost User

          Yes, definitely. Dotnet Framework 4.0 provides backward compatibility. HTH

          Jinal Desai - LIVE Experience is mother of sage....

          L Offline
          L Offline
          Lost User
          wrote on last edited by
          #4

          Jinal Desai - LIVE wrote:

          Dotnet Framework 4.0 provides backward compatibility.

          In that case it should include 3.5, either within itself or by auto install.

          It's time for a new signature.

          1 Reply Last reply
          0
          • R Randar Puust

            We have a 3.5 application and are planning on supporting 4.0 in the near future and were wondering if we should just tell our support to only install the 4.0 framework now. The question really is, will a 3.5 application work, with no changes with only the 4.0 framework installed?

            Randar Puust Software Architect, Jonas Software MCSD.Net, MCSE

            D Offline
            D Offline
            dan sh
            wrote on last edited by
            #5

            Just change the target framework in your application (3.5 Framework one) and test it once. If everything goes fine then you can go ahead with only 4.0 on the computer.

            1 Reply Last reply
            0
            • R Randar Puust

              We have a 3.5 application and are planning on supporting 4.0 in the near future and were wondering if we should just tell our support to only install the 4.0 framework now. The question really is, will a 3.5 application work, with no changes with only the 4.0 framework installed?

              Randar Puust Software Architect, Jonas Software MCSD.Net, MCSE

              A Offline
              A Offline
              Anshul R
              wrote on last edited by
              #6

              If you are creating an installer with the .NET Framework specifications/requirements, it will compel the user to install the version you have specified even if the user has a newer version.

              1 Reply Last reply
              0
              • R Randar Puust

                We have a 3.5 application and are planning on supporting 4.0 in the near future and were wondering if we should just tell our support to only install the 4.0 framework now. The question really is, will a 3.5 application work, with no changes with only the 4.0 framework installed?

                Randar Puust Software Architect, Jonas Software MCSD.Net, MCSE

                L Offline
                L Offline
                Lost User
                wrote on last edited by
                #7

                I've tested this and it seems that any solution/project created under 3.5 and opened in 4.0 requires conversion - it automatically brings up a conversion wizard. Creating new projects under 4.0 gives the choice of frameworks 2.0, 3.0, 3.5 or 4.

                L 1 Reply Last reply
                0
                • L Lost User

                  I've tested this and it seems that any solution/project created under 3.5 and opened in 4.0 requires conversion - it automatically brings up a conversion wizard. Creating new projects under 4.0 gives the choice of frameworks 2.0, 3.0, 3.5 or 4.

                  L Offline
                  L Offline
                  Luc Pattyn
                  wrote on last edited by
                  #8

                  yes, the project files for different Studio versions have different content; this is independent of the .NET version that is being targeted by the project. So VS2010 can create a project that targets .NET 2.0, and said project will result in an exe/dll that runs fine on a 2.0-only system, but the project itself won't open in VS2005. :)

                  Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]


                  I only read formatted code with indentation, so please use PRE tags for code snippets.


                  I'm not participating in frackin' Q&A, so if you want my opinion, ask away in a real forum (or on my profile page).


                  1 Reply Last reply
                  0
                  Reply
                  • Reply as topic
                  Log in to reply
                  • Oldest to Newest
                  • Newest to Oldest
                  • Most Votes


                  • Login

                  • Don't have an account? Register

                  • Login or register to search.
                  • First post
                    Last post
                  0
                  • Categories
                  • Recent
                  • Tags
                  • Popular
                  • World
                  • Users
                  • Groups