ilmerge

问题 This question already has an answer here : Closed 6 years ago . Possible Duplicate: Merging .dll with .exe Okay, so... I have all the files of ilmerge, along with the .exe (CabalMain.exe) and the dll (crckd.dll) in one path. C:\Program Files (x86)\Microsoft\ILMerge I shift>rightclick folder and open up command prompt. Since I'd like to merge the two I enter: C:\Program Files (x86)\Microsoft\ILMerge>C:\Program Files (x86)\Microsoft\ILMerg e\ilmerge C:\Program Files (x86)\Microsoft\ILMerge

问题 I am wondering what are the heuristics when creating releases of libraries to be included in other projects in relation to dependencies and if I should include them or not. My problem is the following: I have a CommonUtilities library that provides as the name implies a set of utilities that can be used in more than one place. Dependencies of CommonUtilities include log4net.dll (the logging framework) and Oracle.DataAccess.dll (database driver). I have another project called MyProject that I

问题 I am trying to us ILMerge via nuget to merge two SharePoint assemblies in to my plugin dll. The assemblies are; Microsoft.SharePoint.Client (v16.1) Microsoft.SharePoint.Client.Runtime (v16.1) They seem to successfully merge in to my single plugin dll and i can see the required classes etc if I inspect the dll with JustDecompile. When debugging the plugin, it throws a security exception; Request for the permission of type 'System.Security.Permissions.SecurityPermission, mscorlib, Version=4.0.0

问题 I have an issue using the latest version of ILMerge and I would like if someone can explain me if this is normal. During my search on the web I realized I was not using the latest version of ILMerge so I updated my projects and this is where everything got wrong… First let me explain quickly my project dependencies: The dll project A references and uses ILMerge. The dll project B references and uses the dll A but it do not reference ILMerge. The application project C reference the dll B but

问题 Currently I know of two methods of embedding assemblies into one application file: ILMerge and using the ResolveAssembly event. I would like to know if anyone have had more success with one over the other. Is there any drawbacks from using either one of those (performance, security, ...)? From my point of view, it looks like we should always merge all the "private" assemblies into an application as it is more clean this way when the application is considered as a whole. Any thoughts? 回答1: I

问题 I'm developing a medium sized enterprise application. There are many projects / solutions to this. For example: Company.Data Company.Data.LinqToSql Company.Entities (business objects) Company.BLL I then have some applications - for example a windows service: MyWindowsService. When i deploy this (by creating a setup project) it installs a load of DLL's from the output of the above mentioned projects. Is this where i should be using ILMerge? to create one assembly.... Company.dll for example?

问题 I am using ILMerge to combine 9 .NET DLL's written in C# .NET 4. The problem is ILMerge gets stuck, no error message or anything. The log shows that ILMerge merges all the assemblies correctly, then sets out to write the target assembly. It runs the assembly resolver for a bunch of references and then.. nothing. After successfully resolving System.Configuration the log shows nothing else. The program continues to use the CPU but I don't see if it's doing anything. Any one else had a similar

问题 I'm testing out ILMerge for a new project, and although the .exe file seems to be created correctly, it won't run. I have installed ILMerge via the .msi installer (found here http://www.microsoft.com/download/en/confirmation.aspx?id=17630) and am running on a test project using a batch file. Below is the batch file, and the subsequent output log after running. All appears ok in the logs, no errors reported. I am running .NET framework 4.0 for this test project. When I try to run the .exe, it

问题 I'm trying to merge multiple assemblies into one as my 'Proxy' assembly for a WCF service. Currently, users of the Proxy need to reference the assembly containing the data contracts, and also my domain assembly because of my inheritance schemes. I'd like to use ILMerge for this. In particular, the ILMerge-Tasks project looks promising, especially this line from their project home: ILMerge-Tasks Project Home: ...It even includes a post-build event that merges ILMerge and the task dll so that

问题 So, as the title reads, I have a VS2010 solution with ~50 projects in it right now. If I make a change to a "top level" project that nothing references then VS still rebuilds all 50 projects. I'm running Visual Studio 2010 Ultimate without any add-ons. I am using ILMerge to consolidate all of the projects into a single file. I have verified this by checking the time stamps of the lower level dlls and see that they are indeed rebuilt even though their code wasn't touched. I've read all