WIX MSBuild automation help - solution best practices -
I know that there are so many questions about this one information I have read them all, but my mind is all Has changed around and I do not know how to go, besides the lack of documentation actually hurts.
This is my scenerio We are trying to use WIX to create an installer for our application to our dealers for our product information. App contains approximately 2,000 images and documents of our products and a SQL CE database that are updated through the Microsoft Sync Framework. The data changes so often that it is very undesirable to keep these 2000s as content files in the app's project, depending on the app, NAT Framework 3.5 SP1, SQL Server CE 3.5, Microsoft Sync Framework 1.0 and ADOnet Sync Service 2.0.
The app has these requirements:
- Dealers will be given an app on a CD every year for any updates (app or data updates).
- The app needs to update itself from the Internet to get any new pictures, documents or data. / Li>
- If they are not present on the client machine, then they must be installed.
- The full installer should be generated from an MSBuild script as much as possible (we do not want to update the 2000+ file list manually).
What we have accomplished so far is that we have a fascinating project in our solution. We have manually specified binary in a .wxs file. The Web has modified the .xxproj file to collect our data (pictures and documents and databases) from a specified location (it is broken and giving ICE38 error) to use the hit directory function. It's fine, but still a lot of work
I am looking to see what other people have done in this situation.
- How will you arrange your solutions in relation to 2000+ data files? Can you create a custom build script that receives current data from the server or do you include them as content files in the main project?
- How do you get WIX to include all project outputs? Referenced assemblies) and all data files? If you have any complete samples, it would be great that I have found that there are small clips here and there and there is no complete example to finish from the beginning.
- How do you handle version numbers? Would you recieve them in a build script and refer them to $ (var.VersionNumberName)? Do you have the automatically automated version number for the project deployment? if so, how?
If there is a better information than what I am getting, please include it. I have read many articles, blogs, Stackworflow questions, teachers, wiki, etc. Everything looks good in bits and pieces, tutorials are good but nothing tells about MSBuild and Votive I would like to see the beginning of ending the tutorial to use MSBuild and Votive and all WIX MSBuild goals. If someone does not know about this tutorial, I can join together. I have already spent the whole week meeting information and reading. I'm also new to MSBuild, so if anyone has a great article on MSBuild, please include them.
Separate different types of complexities in separate merge modules and form part of build They have to completely separate them into an MSI. Things that change in this way can change often without affecting those things that hardly change at all.
1) For data files:
We use Wipe to generate and therefore merge module is a HTML + Flash based help system that receives thousands of files (I CHM can not understand to go).
Compile them into the merge module itself. Assemblies: Assuming that it is a set that at least often creates merge modules with the right files and dependencies or with WixEdit. 3) For the version number there are many ways to manage it based on your build system. Assembly InfoTask is quite easy to ensure that the version of all your assemblies has been appropriately done. If you are using TFS then the MSBuild Extensions Pack has some versatile accessories.
Comments
Post a Comment