ilmerge

I have a control library in my application that's a bit big for the type of application I'm developing. The library is more than 2Mb and I barely use it's functionality, I would say I use like 5% to 10% of all it's functionality. Is there anyway to remove code that my application never uses from the library? P.S: The library is not developed by me and it's not open-source (you can buy the code though). EDIT: I posted this because I though this could be achieved using ILMerge, that's what someone said to me in the past... I tried to use ILMerge but didn't work and I'm not sure I'm using it

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? I've since found this blog post from Jeffrey Richter and I think it answers adequately my question. 来源： https:/

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 want to include CommonUtilities in. MyProject also depends on Oracle.DataAccess. If I use ILMerge and

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 7 years ago . Please how can I combine multiple dlls into one using ILMerge. You run it, from a command line, like so: ilmerge /out:Merged.dll Lib1.dll Lib2.dll 来源： https://stackoverflow.com/questions/12516866/using-ilmerge-to-combine-multiple-dlls-in

I tried: C:\Windows\System32>ilmerge /target:winexe /out:c:\output.exe c:\MyProgram.exe c:\Microsoft.WindowsAPICodePack.dll But got: 'ilmerge' is not recognized as an internal or external command, operable program or batch file. What am I doing wrong? (And by the way, is there a better way to merge dll’s into an exe file?) Thanks This is not a programming question... but you need to install ILMERGE and make sure that it is either in the path or that you fully reference the path. ILMERGE is not a built-in command that you can just use... As for alternatives, you could embed them as embedded

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? How would i go about integrating this into my build process? Cheeso The question ILMerge Best Practices

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 experience? Looks like just writing out the question helped. Turns out I needed to add /targetplatform