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
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
  1. Home
  2. General Programming
  3. .NET (Core and Framework)
  4. Framework version issue

Framework version issue

Scheduled Pinned Locked Moved .NET (Core and Framework)
csharpdotnethelptutorialquestion
6 Posts 2 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.
  • L Offline
    L Offline
    Lisana
    wrote on last edited by
    #1

    I have an app created by VS2003. The launch conditions of .net framework's supportedRuntime is V1.1.4322. It can be installed in those machine had this version. I have another machine that only have the newest version framework V2.0. When I installed it, it asks me to install the .net framework V1.1.4322. I think that should not happen when the computer has the newest version .net framework in it. But my app can't be installed. Is there anybody know how to solve this issue? THANKS!! Lisa

    D 1 Reply Last reply
    0
    • L Lisana

      I have an app created by VS2003. The launch conditions of .net framework's supportedRuntime is V1.1.4322. It can be installed in those machine had this version. I have another machine that only have the newest version framework V2.0. When I installed it, it asks me to install the .net framework V1.1.4322. I think that should not happen when the computer has the newest version .net framework in it. But my app can't be installed. Is there anybody know how to solve this issue? THANKS!! Lisa

      D Offline
      D Offline
      Dave Kreskowiak
      wrote on last edited by
      #2

      You might want to test your application under the 2.0 Framework before you worry about its installation. Breaking Changes in .NET Framework 2.0[^]. You'll just have to change the installer for the app. You could get away with removing the .NET Framework dependancy or possibly just changing the version of the dependancy to 2.0.(something I can't remember offhand). The code itself will launch (by default) under the latest runtime if the specified runtime is not available. That doesn't mean that it'll work 100% the same as it did under 1.1. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

      L 1 Reply Last reply
      0
      • D Dave Kreskowiak

        You might want to test your application under the 2.0 Framework before you worry about its installation. Breaking Changes in .NET Framework 2.0[^]. You'll just have to change the installer for the app. You could get away with removing the .NET Framework dependancy or possibly just changing the version of the dependancy to 2.0.(something I can't remember offhand). The code itself will launch (by default) under the latest runtime if the specified runtime is not available. That doesn't mean that it'll work 100% the same as it did under 1.1. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

        L Offline
        L Offline
        Lisana
        wrote on last edited by
        #3

        I have changed the version of the dependancy to 2.0.50727, and it works fine under the 2.0 framework. But when I test in another workstation only have .net framework 1.1. The installation request it to install the .Net Framework 2.0, but my application should run under .net framework 1.1 without any problem. How can I work around this? When the workstation has .Net framework version 1.1 and up, it doesn't need to install any more .net framework. THanks, Dave! Lisa -- modified at 12:17 Friday 10th February, 2006

        D 1 Reply Last reply
        0
        • L Lisana

          I have changed the version of the dependancy to 2.0.50727, and it works fine under the 2.0 framework. But when I test in another workstation only have .net framework 1.1. The installation request it to install the .Net Framework 2.0, but my application should run under .net framework 1.1 without any problem. How can I work around this? When the workstation has .Net framework version 1.1 and up, it doesn't need to install any more .net framework. THanks, Dave! Lisa -- modified at 12:17 Friday 10th February, 2006

          D Offline
          D Offline
          Dave Kreskowiak
          wrote on last edited by
          #4

          Whoops! My bad! It's a Dependancy, so without that version, the app won't install. You can put the version number back to the original value, then set the AllowLaterVersions property of the .NET Framework dependency to True. By doing this, you're specifying that your app needs at least version 1.1 of the Framework installed. Newer versions are acceptable for installation. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

          L 1 Reply Last reply
          0
          • D Dave Kreskowiak

            Whoops! My bad! It's a Dependancy, so without that version, the app won't install. You can put the version number back to the original value, then set the AllowLaterVersions property of the .NET Framework dependency to True. By doing this, you're specifying that your app needs at least version 1.1 of the Framework installed. Newer versions are acceptable for installation. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

            L Offline
            L Offline
            Lisana
            wrote on last edited by
            #5

            Hello, Dave..That's so funny..I can't find the AllowLaterVersions property in Launch conditions -> .Net Framework ->property. There are only 4 propperties (Name, InstallUrl, Message, SupportedRuntime) and I'm using VS2003 version. Do you have any idea? Lisa

            D 1 Reply Last reply
            0
            • L Lisana

              Hello, Dave..That's so funny..I can't find the AllowLaterVersions property in Launch conditions -> .Net Framework ->property. There are only 4 propperties (Name, InstallUrl, Message, SupportedRuntime) and I'm using VS2003 version. Do you have any idea? Lisa

              D Offline
              D Offline
              Dave Kreskowiak
              wrote on last edited by
              #6

              Yikes! I though you were using 2005. That property doesn't exist in 2003. About the best option you have, using the Setup and Deployment project in 2003, is to remove the dependancy entirely. The MSI will no longer check to see if the .NET Framework is installed. You're better off using one of the other Installer builders or bootstrappers. Google results[^] RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

              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