You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+21-10Lines changed: 21 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,8 +51,12 @@ WiX supports a number of interfaces including CLI - we decided to go with the Vi
51
51
52
52
## How To Use SunnyFORM
53
53
54
-
1. Clone the repository, and open in Visual Studio. Set the build configuration to x64 (required for Flutter).
55
-
2. Navigate to `Package.wxs`, and under the `Package`tag, update the version number attribute
54
+
1. Run `flutter build windows`, and note CastFORM version
55
+
2. Clone the repository, and open in Visual Studio. Set the build configuration to x64 (required for Flutter).
56
+
3. In the top toolbar go to `Project > Properties > Build`, and modify the absolute paths for Fluttter build output and Visual C++ Redistributable libraries directories
57
+
3. Navigate to `Package.wxs`, and under the `Package`tag, update the version number attribute
58
+
4. Check if the the folder structure in `CastFORM/build/windows/runner/Release` has changed, and update `Folders.wxs` accordingly
59
+
5. Check if the file structure has changed, and update `AppComponents.wxs` accordingly
56
60
57
61
## How To Use HeatWave for Flutter Projects
58
62
@@ -65,24 +69,31 @@ Note2: These instructions assume system-wide installation, rather than user-only
65
69
- If you don't check that last option, you'll end up with a folder structure like so: `.../solution/project/`,
66
70
which may be suitable for large projects but unlikely to be necessary for our intents and purposes
67
71
- After this you can hit `Create`
68
-
2.`Package.wxs` should already be open for you. Modify the `Package` tag with the attributes you'd like to see in the installed app
72
+
2. In the top toolbar go to `Project > Properties > Build`, and under `Preprocessor variables` set any user-defined variables you'd like to use
73
+
- Refer to our `Installer.wixproj` file for an example
74
+
- We use it to house the absolute paths for Fluttter build output and Visual C++ Redistributable libraries directories
75
+
3.`Package.wxs` should already be open for you. Modify the `Package` tag with the attributes you'd like to see in the installed app
69
76
- E.g. `Name` is how it should be displayed in the Start Menu after installation
70
77
- Version should be in the format `major.minor.build`, with the first 2 numbers being 0-255, and the build number being 0-65535
71
78
- Upgrade code is a GUID that lets Windows Installer identify different version of the same software
72
-
3. Nest the following line within the `Package` tags (see ours for reference): `<MediaTemplate EmbedCab="yes"/>`
79
+
4. Nest the following line within the `Package` tags (see ours for reference): `<MediaTemplate EmbedCab="yes"/>`
73
80
- This tells WiX to bundle the cabinet files inside of the `.msi` so that you only distribute one file as the installer
74
-
4. Create a new `Feature` tag to enclose the existing template feature; create another one in the same level as the along side `Main`. Feel free to name the IDs as you see fit (see ours for reference).
81
+
5. Create a new `Feature` tag to enclose the existing template feature; create another one in the same level as the along side `Main`. Feel free to name the IDs as you see fit (see ours for reference).
75
82
- The feature tag should now be a tree with one parent and two children
76
83
- We are repurposing the feature tag provided for the main application, and creating one in the same level for Visual C++ redistributables
77
-
5. Rename all instances of `ExampleComponents` to `AppComponents` in the project
78
-
- See `Package.wxs` and `AppComponents.wxs` in ours for reference
79
-
6. Duplicate `ComponentGroupRef` tag for the other feature with a suitable ID for Visual C++ Redustributable libraries; similarly duplicate `AppComponents.wxs` and rename IDs to waht you used in the corresponding `ComponentGroupRef` ID
84
+
6. Duplicate `ComponentGroupRef` tag for the other feature with a suitable ID for Visual C++ Redustributable libraries; similarly duplicate `ExampleComponents.wxs` and rename IDs to waht you used in the corresponding `ComponentGroupRef` ID
80
85
- See `Package.wxs` and `VRredist.wxs` in ours for reference
81
-
7. Modify `INSTALLFOLDER` in `Folders.wxs` to suit your preferred install location
86
+
7. Use the `ComponentGroupRef` tag to create one component group reference for each folder you'd like to write files to (non-recursive)
87
+
- See `Package.wxs` and `AppComponents.wxs` in ours for reference
88
+
8. Modify `INSTALLFOLDER` in `Folders.wxs` to suit your preferred install location
82
89
- Supplying `ProgramFiles6432Folder` for `StandardDirectory` simply means to use either `C:\Program Files (x86)` or `C:\Program Files` as appropriate depending on build target
83
90
- The template created by HeatWave concatenates company name and product name to make one folder; we split this up into a nested folder structure for our use case
84
-
8. Specify additional folders nested under `INSTALLFOLDER` according to your Flutter build
91
+
9. Specify additional folders nested under `INSTALLFOLDER` according to your Flutter build
85
92
- Refer to `build/windows/runner/Release` after running `flutter build windows` in your Flutter project
93
+
10. Flesh out application component groups - see our `AppComponents.wxs` for reference
94
+
- To use preprocessor variables, see step 2
95
+
11. Repeat for Visual C++ Redustributable libraries
0 commit comments