I want to exclude JSON.NET from the merged assembly (DLL, .NET 3.5), but nothing I did worked. I changed the ILMergeTransitive setting in the ILMerge.props file to false. I copied the DLLs from the .ilmerge file in the obj folder to the ILMergeOrder.txt file (did not change the ILMergeOrderFile setting in the ILMerge.props file) and left everything except the Newtonsoft.Json.dll. Deleted the obj folder. Still, every time I build, the .ilmerge file gets recreated and it contains Newtonsoft.Json.dll (and the output tells me that it is included in the merge). Is this a bug? Or am I not doing it correctly?
↧
Created Unassigned: Cannot exclude a DLL from merge [18]
↧
New Post: Could not abel to build WPF project
ILMerge doesn't handle WPF well, AFAIK - something goes wrong with the embedded resources.
↧
↧
Commented Unassigned: Cannot exclude a DLL from merge [18]
I want to exclude JSON.NET from the merged assembly (DLL, .NET 3.5), but nothing I did worked. I changed the ILMergeTransitive setting in the ILMerge.props file to false. I copied the DLLs from the .ilmerge file in the obj folder to the ILMergeOrder.txt file (did not change the ILMergeOrderFile setting in the ILMerge.props file) and left everything except the Newtonsoft.Json.dll. Deleted the obj folder. Still, every time I build, the .ilmerge file gets recreated and it contains Newtonsoft.Json.dll (and the output tells me that it is included in the merge). Is this a bug? Or am I not doing it correctly?
Comments: Hi, is reference to JSON.NET dll marked as "Copy Local" in your project? if it is, it will be included, otherwise not. Cheers
Comments: Hi, is reference to JSON.NET dll marked as "Copy Local" in your project? if it is, it will be included, otherwise not. Cheers
↧
Commented Unassigned: Cannot exclude a DLL from merge [18]
I want to exclude JSON.NET from the merged assembly (DLL, .NET 3.5), but nothing I did worked. I changed the ILMergeTransitive setting in the ILMerge.props file to false. I copied the DLLs from the .ilmerge file in the obj folder to the ILMergeOrder.txt file (did not change the ILMergeOrderFile setting in the ILMerge.props file) and left everything except the Newtonsoft.Json.dll. Deleted the obj folder. Still, every time I build, the .ilmerge file gets recreated and it contains Newtonsoft.Json.dll (and the output tells me that it is included in the merge). Is this a bug? Or am I not doing it correctly?
Comments: Yes, I figured out that I need to turn the Copy Local setting off. So I assume there is no other way to specify which modules will be included or excluded, and the only purpose of the ILMegeOrder.txt is simply for the order (so even if a module is excluded, it'll still be merged). AFAIK, ILMerge allows you to specify which modules to include regardless of whether they are copied locally.
Comments: Yes, I figured out that I need to turn the Copy Local setting off. So I assume there is no other way to specify which modules will be included or excluded, and the only purpose of the ILMegeOrder.txt is simply for the order (so even if a module is excluded, it'll still be merged). AFAIK, ILMerge allows you to specify which modules to include regardless of whether they are copied locally.
↧
Commented Unassigned: Cannot exclude a DLL from merge [18]
I want to exclude JSON.NET from the merged assembly (DLL, .NET 3.5), but nothing I did worked. I changed the ILMergeTransitive setting in the ILMerge.props file to false. I copied the DLLs from the .ilmerge file in the obj folder to the ILMergeOrder.txt file (did not change the ILMergeOrderFile setting in the ILMerge.props file) and left everything except the Newtonsoft.Json.dll. Deleted the obj folder. Still, every time I build, the .ilmerge file gets recreated and it contains Newtonsoft.Json.dll (and the output tells me that it is included in the merge). Is this a bug? Or am I not doing it correctly?
Comments: _ILMerge allows you to specify which modules to include_ Naturally, but if you need that fine grained control over the merge you'd be better with installing just the ILMerge package and calling it from the post-build step. The whole point of this little project was the easy of use, not the full coverage...
Comments: _ILMerge allows you to specify which modules to include_ Naturally, but if you need that fine grained control over the merge you'd be better with installing just the ILMerge package and calling it from the post-build step. The whole point of this little project was the easy of use, not the full coverage...
↧
↧
Commented Unassigned: Cannot exclude a DLL from merge [18]
I want to exclude JSON.NET from the merged assembly (DLL, .NET 3.5), but nothing I did worked. I changed the ILMergeTransitive setting in the ILMerge.props file to false. I copied the DLLs from the .ilmerge file in the obj folder to the ILMergeOrder.txt file (did not change the ILMergeOrderFile setting in the ILMerge.props file) and left everything except the Newtonsoft.Json.dll. Deleted the obj folder. Still, every time I build, the .ilmerge file gets recreated and it contains Newtonsoft.Json.dll (and the output tells me that it is included in the merge). Is this a bug? Or am I not doing it correctly?
Comments: That's fair. In fact, not copying modules that should be excluded from ILMerge seems like a reasonable approach (at least, if you do not rely on project output AS IS, e.g. when using project output in an installer, but there are always workarounds). I just wish that there were an explicit warning (maybe in the ILMergeOrder.txt file) to notify people who would make an erroneous assumption that modules could be excluded by not listing them in the merge order file). But great job, nonetheless. really handy package. Thanks.
Comments: That's fair. In fact, not copying modules that should be excluded from ILMerge seems like a reasonable approach (at least, if you do not rely on project output AS IS, e.g. when using project output in an installer, but there are always workarounds). I just wish that there were an explicit warning (maybe in the ILMergeOrder.txt file) to notify people who would make an erroneous assumption that modules could be excluded by not listing them in the merge order file). But great job, nonetheless. really handy package. Thanks.
↧
Commented Unassigned: Configure Output assembly name [17]
Hi.
Is there a way to keep an initial assembly unmerged with its initial name, and the merged one as additional with configured name (using OutputFile property from the original IL Merge)?
Example of output folder is:
assembly1.dll
assembly2.dll
They both will be merged to assembly1.dll automatically.
Now I am having problems in Test projects which references project for assembly1 (but assembly is already merged and contains types from assembly2)
The test project references also assembly2 project which brings confusion for the compiler in the Test solution
It would be great if initial assemblies (the main assembly) could stay as they are, and the final, merged one could be stored under different name (if configured so)
Or maybe there is already such a possibility?
Ps. The project is great and works as a charm, but there is no way to work with Unit Testing after merging
Comments: This would be great.
Is there a way to keep an initial assembly unmerged with its initial name, and the merged one as additional with configured name (using OutputFile property from the original IL Merge)?
Example of output folder is:
assembly1.dll
assembly2.dll
They both will be merged to assembly1.dll automatically.
Now I am having problems in Test projects which references project for assembly1 (but assembly is already merged and contains types from assembly2)
The test project references also assembly2 project which brings confusion for the compiler in the Test solution
It would be great if initial assemblies (the main assembly) could stay as they are, and the final, merged one could be stored under different name (if configured so)
Or maybe there is already such a possibility?
Ps. The project is great and works as a charm, but there is no way to work with Unit Testing after merging
Comments: This would be great.
↧
Created Unassigned: XML documents do not get merged correctly [19]
If I set ILMergeXmlDocumentation to true, in the merged XML, I lose all of the primary assembly XML comments; if I set it to false, then none of the XML comments from the secondary assemblies get merged into the final XML. Either way, I'm missing half of the comments. Not sure if there is a workaround for this.
↧