To merge not all dll's with ILMerge












1














Is it possible to merge not all, but just some of reference dll's with ILMerge? I have two references - Zxsign and DirectShowLib. I did ILMerge just with DirectShowLib:



"C:Program Files (x86)MicrosoftILMergeILMerge.exe" SnapShot.exe DirectShowLib.dll /out:aa.exe


FIles zxing.dll and zxing.presentation.dll was placed near aa.exe. Got exception during call to zxing package:



See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Exception: Timeout waiting to get picture
at SnapShot.Capture.Click()
at SnapShot.Form1.button1_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8936 (WinRelRS4.050727-8900)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
aa
Assembly Version: 1.0.6890.24360
Win32 Version: 1.0.6890.24360
CodeBase: file:///D:/C%23nonsens/DirectShowSamples-2010-February/Samples/Capture/DxSnap/bin/Release/New%20folder/aa.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8922 (WinRelRS4.050727-8900)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8934 (WinRelRS4.050727-8900)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8922 (WinRelRS4.050727-8900)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.


Is it possible somehow manage ILMerge in order not to have such error?










share|improve this question



























    1














    Is it possible to merge not all, but just some of reference dll's with ILMerge? I have two references - Zxsign and DirectShowLib. I did ILMerge just with DirectShowLib:



    "C:Program Files (x86)MicrosoftILMergeILMerge.exe" SnapShot.exe DirectShowLib.dll /out:aa.exe


    FIles zxing.dll and zxing.presentation.dll was placed near aa.exe. Got exception during call to zxing package:



    See the end of this message for details on invoking 
    just-in-time (JIT) debugging instead of this dialog box.

    ************** Exception Text **************
    System.Exception: Timeout waiting to get picture
    at SnapShot.Capture.Click()
    at SnapShot.Form1.button1_Click(Object sender, EventArgs e)
    at System.Windows.Forms.Control.OnClick(EventArgs e)
    at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
    at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
    at System.Windows.Forms.Control.WndProc(Message& m)
    at System.Windows.Forms.ButtonBase.WndProc(Message& m)
    at System.Windows.Forms.Button.WndProc(Message& m)
    at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
    at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


    ************** Loaded Assemblies **************
    mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8936 (WinRelRS4.050727-8900)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
    ----------------------------------------
    aa
    Assembly Version: 1.0.6890.24360
    Win32 Version: 1.0.6890.24360
    CodeBase: file:///D:/C%23nonsens/DirectShowSamples-2010-February/Samples/Capture/DxSnap/bin/Release/New%20folder/aa.exe
    ----------------------------------------
    System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8922 (WinRelRS4.050727-8900)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    ----------------------------------------
    System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8934 (WinRelRS4.050727-8900)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    ----------------------------------------
    System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.8922 (WinRelRS4.050727-8900)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    ----------------------------------------

    ************** JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.

    For example:

    <configuration>
    <system.windows.forms jitDebugging="true" />
    </configuration>

    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.


    Is it possible somehow manage ILMerge in order not to have such error?










    share|improve this question

























      1












      1








      1







      Is it possible to merge not all, but just some of reference dll's with ILMerge? I have two references - Zxsign and DirectShowLib. I did ILMerge just with DirectShowLib:



      "C:Program Files (x86)MicrosoftILMergeILMerge.exe" SnapShot.exe DirectShowLib.dll /out:aa.exe


      FIles zxing.dll and zxing.presentation.dll was placed near aa.exe. Got exception during call to zxing package:



      See the end of this message for details on invoking 
      just-in-time (JIT) debugging instead of this dialog box.

      ************** Exception Text **************
      System.Exception: Timeout waiting to get picture
      at SnapShot.Capture.Click()
      at SnapShot.Form1.button1_Click(Object sender, EventArgs e)
      at System.Windows.Forms.Control.OnClick(EventArgs e)
      at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
      at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
      at System.Windows.Forms.Control.WndProc(Message& m)
      at System.Windows.Forms.ButtonBase.WndProc(Message& m)
      at System.Windows.Forms.Button.WndProc(Message& m)
      at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
      at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


      ************** Loaded Assemblies **************
      mscorlib
      Assembly Version: 2.0.0.0
      Win32 Version: 2.0.50727.8936 (WinRelRS4.050727-8900)
      CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
      ----------------------------------------
      aa
      Assembly Version: 1.0.6890.24360
      Win32 Version: 1.0.6890.24360
      CodeBase: file:///D:/C%23nonsens/DirectShowSamples-2010-February/Samples/Capture/DxSnap/bin/Release/New%20folder/aa.exe
      ----------------------------------------
      System.Windows.Forms
      Assembly Version: 2.0.0.0
      Win32 Version: 2.0.50727.8922 (WinRelRS4.050727-8900)
      CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
      ----------------------------------------
      System
      Assembly Version: 2.0.0.0
      Win32 Version: 2.0.50727.8934 (WinRelRS4.050727-8900)
      CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
      ----------------------------------------
      System.Drawing
      Assembly Version: 2.0.0.0
      Win32 Version: 2.0.50727.8922 (WinRelRS4.050727-8900)
      CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
      ----------------------------------------

      ************** JIT Debugging **************
      To enable just-in-time (JIT) debugging, the .config file for this
      application or computer (machine.config) must have the
      jitDebugging value set in the system.windows.forms section.
      The application must also be compiled with debugging
      enabled.

      For example:

      <configuration>
      <system.windows.forms jitDebugging="true" />
      </configuration>

      When JIT debugging is enabled, any unhandled exception
      will be sent to the JIT debugger registered on the computer
      rather than be handled by this dialog box.


      Is it possible somehow manage ILMerge in order not to have such error?










      share|improve this question













      Is it possible to merge not all, but just some of reference dll's with ILMerge? I have two references - Zxsign and DirectShowLib. I did ILMerge just with DirectShowLib:



      "C:Program Files (x86)MicrosoftILMergeILMerge.exe" SnapShot.exe DirectShowLib.dll /out:aa.exe


      FIles zxing.dll and zxing.presentation.dll was placed near aa.exe. Got exception during call to zxing package:



      See the end of this message for details on invoking 
      just-in-time (JIT) debugging instead of this dialog box.

      ************** Exception Text **************
      System.Exception: Timeout waiting to get picture
      at SnapShot.Capture.Click()
      at SnapShot.Form1.button1_Click(Object sender, EventArgs e)
      at System.Windows.Forms.Control.OnClick(EventArgs e)
      at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
      at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
      at System.Windows.Forms.Control.WndProc(Message& m)
      at System.Windows.Forms.ButtonBase.WndProc(Message& m)
      at System.Windows.Forms.Button.WndProc(Message& m)
      at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
      at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


      ************** Loaded Assemblies **************
      mscorlib
      Assembly Version: 2.0.0.0
      Win32 Version: 2.0.50727.8936 (WinRelRS4.050727-8900)
      CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
      ----------------------------------------
      aa
      Assembly Version: 1.0.6890.24360
      Win32 Version: 1.0.6890.24360
      CodeBase: file:///D:/C%23nonsens/DirectShowSamples-2010-February/Samples/Capture/DxSnap/bin/Release/New%20folder/aa.exe
      ----------------------------------------
      System.Windows.Forms
      Assembly Version: 2.0.0.0
      Win32 Version: 2.0.50727.8922 (WinRelRS4.050727-8900)
      CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
      ----------------------------------------
      System
      Assembly Version: 2.0.0.0
      Win32 Version: 2.0.50727.8934 (WinRelRS4.050727-8900)
      CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
      ----------------------------------------
      System.Drawing
      Assembly Version: 2.0.0.0
      Win32 Version: 2.0.50727.8922 (WinRelRS4.050727-8900)
      CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
      ----------------------------------------

      ************** JIT Debugging **************
      To enable just-in-time (JIT) debugging, the .config file for this
      application or computer (machine.config) must have the
      jitDebugging value set in the system.windows.forms section.
      The application must also be compiled with debugging
      enabled.

      For example:

      <configuration>
      <system.windows.forms jitDebugging="true" />
      </configuration>

      When JIT debugging is enabled, any unhandled exception
      will be sent to the JIT debugger registered on the computer
      rather than be handled by this dialog box.


      Is it possible somehow manage ILMerge in order not to have such error?







      c# ilmerge zxing.net






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 12 at 13:08









      vico

      4,5412166139




      4,5412166139
























          1 Answer
          1






          active

          oldest

          votes


















          0














          This is possible with the following nuget
          Install-package ILMerge.MSBuild.Tasks



          Example of the target in .csproj between <Project> </Project>



          <Target Name="AfterBuild">
          <ItemGroup>
          <MergeAsm Include="$(OutputPath)$(AssemblyName).dll" />
          <MergeAsm Include="$(OutputPath)2nd.dll" />
          <MergeAsm Include="$(OutputPath)3th.dll" />
          </ItemGroup>
          <PropertyGroup>
          <MergedAssembly>$(ProjectDir)$(OutDir)$(AssemblyName).dll</MergedAssembly>
          </PropertyGroup>
          <Message Text="ILMerge @(MergeAsm) -&gt; $(MergedAssembly)" Importance="high" />
          <ILMerge InputAssemblies="@(MergeAsm)" OutputFile="$(MergedAssembly)" TargetKind="SameAsPrimaryAssembly" />
          </Target>


          The MergeAsm you can define every dll you wanna merge to the primary as shown in the example 2nd.dll and 3th.dll






          share|improve this answer





















            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53262864%2fto-merge-not-all-dlls-with-ilmerge%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            This is possible with the following nuget
            Install-package ILMerge.MSBuild.Tasks



            Example of the target in .csproj between <Project> </Project>



            <Target Name="AfterBuild">
            <ItemGroup>
            <MergeAsm Include="$(OutputPath)$(AssemblyName).dll" />
            <MergeAsm Include="$(OutputPath)2nd.dll" />
            <MergeAsm Include="$(OutputPath)3th.dll" />
            </ItemGroup>
            <PropertyGroup>
            <MergedAssembly>$(ProjectDir)$(OutDir)$(AssemblyName).dll</MergedAssembly>
            </PropertyGroup>
            <Message Text="ILMerge @(MergeAsm) -&gt; $(MergedAssembly)" Importance="high" />
            <ILMerge InputAssemblies="@(MergeAsm)" OutputFile="$(MergedAssembly)" TargetKind="SameAsPrimaryAssembly" />
            </Target>


            The MergeAsm you can define every dll you wanna merge to the primary as shown in the example 2nd.dll and 3th.dll






            share|improve this answer


























              0














              This is possible with the following nuget
              Install-package ILMerge.MSBuild.Tasks



              Example of the target in .csproj between <Project> </Project>



              <Target Name="AfterBuild">
              <ItemGroup>
              <MergeAsm Include="$(OutputPath)$(AssemblyName).dll" />
              <MergeAsm Include="$(OutputPath)2nd.dll" />
              <MergeAsm Include="$(OutputPath)3th.dll" />
              </ItemGroup>
              <PropertyGroup>
              <MergedAssembly>$(ProjectDir)$(OutDir)$(AssemblyName).dll</MergedAssembly>
              </PropertyGroup>
              <Message Text="ILMerge @(MergeAsm) -&gt; $(MergedAssembly)" Importance="high" />
              <ILMerge InputAssemblies="@(MergeAsm)" OutputFile="$(MergedAssembly)" TargetKind="SameAsPrimaryAssembly" />
              </Target>


              The MergeAsm you can define every dll you wanna merge to the primary as shown in the example 2nd.dll and 3th.dll






              share|improve this answer
























                0












                0








                0






                This is possible with the following nuget
                Install-package ILMerge.MSBuild.Tasks



                Example of the target in .csproj between <Project> </Project>



                <Target Name="AfterBuild">
                <ItemGroup>
                <MergeAsm Include="$(OutputPath)$(AssemblyName).dll" />
                <MergeAsm Include="$(OutputPath)2nd.dll" />
                <MergeAsm Include="$(OutputPath)3th.dll" />
                </ItemGroup>
                <PropertyGroup>
                <MergedAssembly>$(ProjectDir)$(OutDir)$(AssemblyName).dll</MergedAssembly>
                </PropertyGroup>
                <Message Text="ILMerge @(MergeAsm) -&gt; $(MergedAssembly)" Importance="high" />
                <ILMerge InputAssemblies="@(MergeAsm)" OutputFile="$(MergedAssembly)" TargetKind="SameAsPrimaryAssembly" />
                </Target>


                The MergeAsm you can define every dll you wanna merge to the primary as shown in the example 2nd.dll and 3th.dll






                share|improve this answer












                This is possible with the following nuget
                Install-package ILMerge.MSBuild.Tasks



                Example of the target in .csproj between <Project> </Project>



                <Target Name="AfterBuild">
                <ItemGroup>
                <MergeAsm Include="$(OutputPath)$(AssemblyName).dll" />
                <MergeAsm Include="$(OutputPath)2nd.dll" />
                <MergeAsm Include="$(OutputPath)3th.dll" />
                </ItemGroup>
                <PropertyGroup>
                <MergedAssembly>$(ProjectDir)$(OutDir)$(AssemblyName).dll</MergedAssembly>
                </PropertyGroup>
                <Message Text="ILMerge @(MergeAsm) -&gt; $(MergedAssembly)" Importance="high" />
                <ILMerge InputAssemblies="@(MergeAsm)" OutputFile="$(MergedAssembly)" TargetKind="SameAsPrimaryAssembly" />
                </Target>


                The MergeAsm you can define every dll you wanna merge to the primary as shown in the example 2nd.dll and 3th.dll







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 12 at 13:20









                H.Mikhaeljan

                771514




                771514






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53262864%2fto-merge-not-all-dlls-with-ilmerge%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    List item for chat from Array inside array React Native

                    Thiostrepton

                    Caerphilly