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. Visual Basic
  4. Registration Free COM with VS 2003

Registration Free COM with VS 2003

Scheduled Pinned Locked Moved Visual Basic
comquestionvisual-studio
5 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.
  • A Offline
    A Offline
    Atara
    wrote on last edited by
    #1

    I recently learned that on XP (and later) OS, you do not need to register activeX, if you use "isolated" option from vs 2005 menu to create a special manifest file. Does anyone know how can I make the required manifest lines if I only have VS 2003 ? Thanks,

    Atara

    C A 2 Replies Last reply
    0
    • A Atara

      I recently learned that on XP (and later) OS, you do not need to register activeX, if you use "isolated" option from vs 2005 menu to create a special manifest file. Does anyone know how can I make the required manifest lines if I only have VS 2003 ? Thanks,

      Atara

      C Offline
      C Offline
      Christian Graus
      wrote on last edited by
      #2

      VS2003 doesn't create manifest files.  I also don't see how a COM dll can work without being registered, unless the manifest contains the GUIDs and so on, and everything has to be in the same directory.

      Christian Graus - C++ MVP 'Why don't we jump on a fad that hasn't already been widely discredited ?' - Dilbert

      A 1 Reply Last reply
      0
      • C Christian Graus

        VS2003 doesn't create manifest files.  I also don't see how a COM dll can work without being registered, unless the manifest contains the GUIDs and so on, and everything has to be in the same directory.

        Christian Graus - C++ MVP 'Why don't we jump on a fad that hasn't already been widely discredited ?' - Dilbert

        A Offline
        A Offline
        Atara
        wrote on last edited by
        #3

        The manifest should contain clsid. This technologie (COM dll can work without being registered) should work on XP sp2, and Vista. according to the documentation it should work on .Net 1.1 but I can not find the exact format of the needed manifest file :( more about this "Reg Free COM" technologie in - http://msdn.microsoft.com/msdnmag/issues/05/04/RegFreeCOM/[^]

        Atara

        1 Reply Last reply
        0
        • A Atara

          I recently learned that on XP (and later) OS, you do not need to register activeX, if you use "isolated" option from vs 2005 menu to create a special manifest file. Does anyone know how can I make the required manifest lines if I only have VS 2003 ? Thanks,

          Atara

          A Offline
          A Offline
          Atara
          wrote on last edited by
          #4

          I solved it with the help of: (1) Escape DLL Hell - Simplify App Deployment with ClickOnce and Registration-Free COM (VS 2005 Article) http://msdn.microsoft.com/msdnmag/issues/05/04/RegFreeCOM/ (2) Registration-Free Activation of COM Components: A Walkthrough (VS 2003 Article) http://msdn2.microsoft.com/en-us/library/ms973913.aspx (3) oleView.exe C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\oleView.exe (or . . . \Tools\Bin) oleView.exe: File->View TypeLib The solution: 1. The main manifest (myProg.exe.manifest): ... more files ... 2. The myAxFileN manifest (myAxFileN.X.manifest): The id are taken from oleView.exe: File->View TypeLib generated file. I hope it will help you to start digging your specific needs. Atara

          A 1 Reply Last reply
          0
          • A Atara

            I solved it with the help of: (1) Escape DLL Hell - Simplify App Deployment with ClickOnce and Registration-Free COM (VS 2005 Article) http://msdn.microsoft.com/msdnmag/issues/05/04/RegFreeCOM/ (2) Registration-Free Activation of COM Components: A Walkthrough (VS 2003 Article) http://msdn2.microsoft.com/en-us/library/ms973913.aspx (3) oleView.exe C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\oleView.exe (or . . . \Tools\Bin) oleView.exe: File->View TypeLib The solution: 1. The main manifest (myProg.exe.manifest): ... more files ... 2. The myAxFileN manifest (myAxFileN.X.manifest): The id are taken from oleView.exe: File->View TypeLib generated file. I hope it will help you to start digging your specific needs. Atara

            A Offline
            A Offline
            Atara
            wrote on last edited by
            #5

            or, you can use only one manifest file, e.g: ... Note: all *.ocx, *.dll files of the activeX should also be in the same folder, with the manifest and the exe files. Atara

            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