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. ILMerge Problems

ILMerge Problems

Scheduled Pinned Locked Moved Visual Basic
comgraphicsgame-devhelpquestion
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.
  • D Offline
    D Offline
    Dr_Lomax
    wrote on last edited by
    #1

    I am using ILMerge to merge my DLLs and it works great. I have run into my first problem unfortunately. I am creating A/V apps using DirectX 9.0c SDK for XP. This is the only SDK whose DLLs I cannot merge with my other DLLs to create a combined assembly. If I exclude the DX DLLs, ILMerge works fine. Here is the syntax I use. c:\> ilmerge /target:library /out:test.dll Interop.Scripting.dll Microsoft.DirectX.AudioVideoPlayback.dll If I include anyother dll besides the DirectX dll, I will get the merged DLL. If I use the DX dll, ILMerge will start and return to the prompt without creating the merged assembly. Has anyone run into a similar problem or does any one have a possible solution to this problem? Thanks.

    D 1 Reply Last reply
    0
    • D Dr_Lomax

      I am using ILMerge to merge my DLLs and it works great. I have run into my first problem unfortunately. I am creating A/V apps using DirectX 9.0c SDK for XP. This is the only SDK whose DLLs I cannot merge with my other DLLs to create a combined assembly. If I exclude the DX DLLs, ILMerge works fine. Here is the syntax I use. c:\> ilmerge /target:library /out:test.dll Interop.Scripting.dll Microsoft.DirectX.AudioVideoPlayback.dll If I include anyother dll besides the DirectX dll, I will get the merged DLL. If I use the DX dll, ILMerge will start and return to the prompt without creating the merged assembly. Has anyone run into a similar problem or does any one have a possible solution to this problem? Thanks.

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

      I have never used it and don't think I ever will. But, since the AudioVideoPlayback more than likely has dependancies on other .DLL's that your not including. You'll probably also have to include the DirectX base .DLL's the managed version wrap. I think your looking at including another 6-10 .DLL's in your merge. IMHO, I don't think it's a good idea to do this with the DirectX .DLL's. I think you'll be much better off just making a prerequisite of your application DirectX 9. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

      D 1 Reply Last reply
      0
      • D Dave Kreskowiak

        I have never used it and don't think I ever will. But, since the AudioVideoPlayback more than likely has dependancies on other .DLL's that your not including. You'll probably also have to include the DirectX base .DLL's the managed version wrap. I think your looking at including another 6-10 .DLL's in your merge. IMHO, I don't think it's a good idea to do this with the DirectX .DLL's. I think you'll be much better off just making a prerequisite of your application DirectX 9. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

        D Offline
        D Offline
        Dr_Lomax
        wrote on last edited by
        #3

        I think I might have included the DirectX base DLL but dont think that made a difference. ILMerge will just merge the DLLs, whether it fucntions or not is secondary, at the moment my concern is just the merge. I have merged all sorts of DLLs without a problem, WMP10, Scripting, Runtime, Enviroment etc. The reason I need to merge this is because I am saving my usercontrol on my flash drive and acessing my PC or laptop to futher build my user control from the flash drive. As a result, I get some dependency issues when I try to use my user control on different system besides the one it was created on.

        D 1 Reply Last reply
        0
        • D Dr_Lomax

          I think I might have included the DirectX base DLL but dont think that made a difference. ILMerge will just merge the DLLs, whether it fucntions or not is secondary, at the moment my concern is just the merge. I have merged all sorts of DLLs without a problem, WMP10, Scripting, Runtime, Enviroment etc. The reason I need to merge this is because I am saving my usercontrol on my flash drive and acessing my PC or laptop to futher build my user control from the flash drive. As a result, I get some dependency issues when I try to use my user control on different system besides the one it was created on.

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

          Dr_Lomax wrote: I think I might have included the DirectX base DLL "DLL", as in singular? How about trying to include ALL the drawing .DLL's. Well, not the 3D ones anyway. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

          D 1 Reply Last reply
          0
          • D Dave Kreskowiak

            Dr_Lomax wrote: I think I might have included the DirectX base DLL "DLL", as in singular? How about trying to include ALL the drawing .DLL's. Well, not the 3D ones anyway. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome

            D Offline
            D Offline
            Dr_Lomax
            wrote on last edited by
            #5

            There is a base DirectX dll and there all all the different interfaces i.e. 3D, Sound, Input etc. Eitherway adding all these additional dependency should affect the functionality of the merged DLL, not the merging process itself. I am concerned about the merging. I will add the additional assemblies when required.

            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