- WPF merging now works with resources (e.g., images) in used libraries
- Migrated to Cecil 0.10
- WPF merging handles correctly cases when there in no XAML in the merged project
- Less aggressive attribute cleanup for the main assembly (unchanged for merged ones) (#174)
- Allow proper use of ExcludeFile in Library mode (#185)
- Handle System.Runtime merging (#188)
- PdbStr doesn't work on Unix, skip it on these OS (#176)
- Support /keycontainer flag (#183)
- More verbose output header for debugging (#187)
- Expose an $(ILRepack) property for nuget consumers (#192)
- SRCSRV data from PDBs are merged for sources available with HTTP. Others are not merged and only the one from the primary assembly is kept.
- Signed WPF applications during the repack process now work properly
- Generic-based resource keys can now be used in WPF applications
- UWP applications are now properly merged
- Add set Log level verbose in IlRepack constructor
- Indirect xaml dependency merge now copes with conflicting versions
- Bumped cecil version
- Fixed regression since 2.0.4 that prevented proper merging of resources in dependent assemblies.
- Because of this, no BAML resources were added from dependencies into the merged result.
- Put public the method retrieving repacked assembly names.
- Bcl+BclAsync now repacks correctly
- Due to caching, some TypeRefs where incorrectly flagged class instead of valuetype
- Some original AssemblyReferences were kept in the merged assembly as ExportedType scope or TypeRef scope, this caused issue unless (by luck) the repacked token was the same as original one
- Added ILRepack version in repack log
- When used with copyattrs flag, primary (first) assembly attributes are prefered (when the custom attribute doesn't allow multiple)
- Types fixed during the 'Fixing references' phase are printed in verbose mode.
- InternalsVisibleTo attributes gets cleaned up to allow signed repacked assemblies to be loaded fine.
- WPF Support
- Classes (e.g.: converters) from libraries can now be used inside XAML files.
- User Controls from libraries can now be used inside XAML files.
- XAML Resource paths in
InitializeComponent()
methods are patched to reference the main assembly instead. - Support for styles, theming (
themes/generic.xml
) and inclusion of XAML files (via pack or non-pack URIs).
- API has been cleaned up (with potential breaking changes, depending on the usage).