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. C#
  4. Framework 1.0 vs Framework 1.1

Framework 1.0 vs Framework 1.1

Scheduled Pinned Locked Moved C#
questioncsharpvisual-studiocomcollaboration
4 Posts 3 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.
  • A Offline
    A Offline
    Alex Getman
    wrote on last edited by
    #1

    Hi to all, I want to ask: I wrote a Visual C# application using VS.NET 2003, so it was created to run under Framework v 1.1 and when I try to launch my application on the mashine where VS.NET 2002 installed I just can do it and some exception occurs. The question is how can I create an assembly wich able to launch on Framework 1.0 using VS.NET 2003? developers team

    D 1 Reply Last reply
    0
    • A Alex Getman

      Hi to all, I want to ask: I wrote a Visual C# application using VS.NET 2003, so it was created to run under Framework v 1.1 and when I try to launch my application on the mashine where VS.NET 2002 installed I just can do it and some exception occurs. The question is how can I create an assembly wich able to launch on Framework 1.0 using VS.NET 2003? developers team

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

      VS.NET 2K3 will only build for the .NET Framework 1.1. You could install the .NET Framework 1.1 on the target machine and your app will run without problem. Now, you could also go into the project properties of your app, Common Properties, General and click on Supported Runtimes. Here you will be able to select which version of the Framework your app will compile against, v1.0, v1.1, or BOTH. But, there's a catch...since v1.0 of the .NET Framework doesn't support certain features v1.1 does and v1.1 has some implementation changes from v1.0, your app might not compile against v1.0 or it will compile, but run differently depending on which framework it's running on. RageInTheMachine9532

      A 1 Reply Last reply
      0
      • D Dave Kreskowiak

        VS.NET 2K3 will only build for the .NET Framework 1.1. You could install the .NET Framework 1.1 on the target machine and your app will run without problem. Now, you could also go into the project properties of your app, Common Properties, General and click on Supported Runtimes. Here you will be able to select which version of the Framework your app will compile against, v1.0, v1.1, or BOTH. But, there's a catch...since v1.0 of the .NET Framework doesn't support certain features v1.1 does and v1.1 has some implementation changes from v1.0, your app might not compile against v1.0 or it will compile, but run differently depending on which framework it's running on. RageInTheMachine9532

        A Offline
        A Offline
        Alex Getman
        wrote on last edited by
        #3

        Thanx. Tommorow I'll try to intall my homework ;) and I hope you solution will help... www.xedom.com

        H 1 Reply Last reply
        0
        • A Alex Getman

          Thanx. Tommorow I'll try to intall my homework ;) and I hope you solution will help... www.xedom.com

          H Offline
          H Offline
          Heath Stewart
          wrote on last edited by
          #4

          Just wanted to add that if you built for 1.0 and ran against a newer framework, you don't need the .config. The framework used is the same or newer than what's referenced in the assembly. The same "gotcha" that Dave mentioned still applies, though, except that deprecated functionality (stuff that doesn't exist in newer frameworks) will cause exceptions to be thrown if you use them, if your assembly even runs. This is much more uncommon, though, as most functionality is usually left in without being changed (functionality may be added to existing classes, but this still works).

          Microsoft MVP, Visual C# My Articles

          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