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. Using .NET 2.0 with .NET 1.1

Using .NET 2.0 with .NET 1.1

Scheduled Pinned Locked Moved .NET (Core and Framework)
csharpdesigndebugginghelptutorial
2 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.
  • M Offline
    M Offline
    Mohammed Derbashi
    wrote on last edited by
    #1

    I'm trying to using a component developed using .NET 2.0 with a .NET 1.1 Windoes Forms application, I'd installed the .NET 2.0 Framework on the machine but still when to add reference to the new component have the following Error message: "D:\NewComponent\Debug\myComponent.UI.Win.dll' is not a Microsoft .NET module." do anybody have any idea how to solve this? :sigh: Mohammed Derbashi

    S 1 Reply Last reply
    0
    • M Mohammed Derbashi

      I'm trying to using a component developed using .NET 2.0 with a .NET 1.1 Windoes Forms application, I'd installed the .NET 2.0 Framework on the machine but still when to add reference to the new component have the following Error message: "D:\NewComponent\Debug\myComponent.UI.Win.dll' is not a Microsoft .NET module." do anybody have any idea how to solve this? :sigh: Mohammed Derbashi

      S Offline
      S Offline
      Sebastian Schneider
      wrote on last edited by
      #2

      You CANNOT use a .NET2 component in a .NET1 application without severe hacking (e.g. "patching" your own 1.1 CLR). You could, however, try to recompile that component for 1.1 and make the necessary code-changes to make it work. Cheers, Sebastian -- Contra vim mortem non est medicamen in hortem.

      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