First, Thanks for your time in making a nice framework. I was able to successfully implement this framework at my client. Everyone kind of liked it. For that I made few over-riddens to framework's targets (in project file not framework targets file), And
few compromises, particularly in adding custom links in Menu. I couldn't add few extra menu items that my client wanted, so we left that idea for now.
Are you considering to update the framework to provide extensibility to WIX targets? Here are few things I am looking at right now...
- I am against to change the framework files for custom menu items as we have one build server for several applications. Changing framework files screws up other applications. Also, any future updates to framework will loose the customization. If you
can provide more extensibility to WIX ( i know right now this is in .js file) ie, moving wix xml-composition to targets with extensibility, we will have lot of flexibility in customizing the MSI.
- Use of a property (something like InstallerFileName) for MSI name.
- Setting File/Product Versions for assemblies (Alternatively I am changing the each project file before compile the solution)
- Ability to set custom properties (like Version, Source, BuildServer) on MSI file. I don't know if that is possible with WIX. Right now I am using 'PackageComments' with concatenating all properties I need.