![wix formatted file identifier wix formatted file identifier](https://i1.wp.com/www.dunebook.com/wp-content/uploads/2018/01/Screen-Shot-2018-01-30-at-1.20.10-PM.png)
The code comments should provide plenty info about what each part does in general. The main WXS file: SuperForm.wxs We’ll only take a look at the general structure of the main SuperForm.wxs and not its the details. Only variables set in “Define preprocessor variables” or System Environment variables are accessible to the whole project for now. For now there’s no way to tell WiX in Visual Studio to have a wxi include file available to the whole project, so you have to include it in each file separately. This way we couldn’t recreate it in each pre-build event. Because the FilesFragment.wxs is autogenerated on every project build we don’t want to change it manually each time by adding the include wxi at the beginning of the file.
![wix formatted file identifier wix formatted file identifier](https://d2x3xhvgiqkx42.cloudfront.net/12345678-1234-1234-1234-1234567890ab/0ca9e8ba-16ed-4cd8-a1e1-58d01c4420f7/2018/10/02/288a6751-a709-4af5-8b23-38479a226200.png)
This is why we’ve added a System Environment variable named SuperFormFilesDir as is shown in the previous. This is pretty much unacceptable by my standards. This is why I’ve chosen not to go this route because in multi developer teams not everyone has the same directory structure and having a single variable would mean each developer would have to checkout the wixproj file to edit the variable. For preprocessor variable $(var.VariableName) to be seen by every file in the project you have to include them in the WiX project properties->Build->“Define preprocessor variables” textbox.
![wix formatted file identifier wix formatted file identifier](https://d2x3xhvgiqkx42.cloudfront.net/12345678-1234-1234-1234-1234567890ab/7f40210b-c6c2-4c15-bbcf-5bb78a69d10e/2020/09/08/3e8df797-e2a8-42f5-a121-edf1f87a9d40/2780f1e5-81f7-476e-90b8-3a267d91e8d2.png)
You’d have to include it manually into those two wxs files too. If you’ve ever worked with C++ you can think of the include files as.h files.įor example if you include SuperFormVariables.wxi into the SuperForm.wxs, the variables in the wxi won’t be seen in FilesFragment.wxs or RegistryFragment.wxs. To include a wxi file into the wxs file you have to put the wxi at the beginning of each.wxs file you wish to include it in. WXI include file Include files are exactly what their name implies. The more detailed descriptions will be in future posts about features themselves. For wxs file we’ll just go over the general description of what each part does in the code comments. We’re still playing with our super SuperForm application and today we’ll take a look at the general parts of the main wxs file, SuperForm.wxs, and the wxi include file. In we’ve taken a look at the WiX solution/project structure and project properties. Wix-devs wix-users Re: Shortcut Creation Re: Shortcut Creation. WiX toolset Mailing Lists Brought to you by: barnson, robmen.