Difference between revisions of "0.9"

From CDOT Wiki
Jump to: navigation, search
 
Line 7: Line 7:
 
1) Firefox must be installed
 
1) Firefox must be installed
  
2) Wix must be installed
+
2) Wix must be installed (and added to the system path variable)
  
 
Note that this build has been tested but its also likely that there are still tons of bugs. For my 1.0 build I will have these sorted out.  
 
Note that this build has been tested but its also likely that there are still tons of bugs. For my 1.0 build I will have these sorted out.  
Line 17: Line 17:
 
As of April 10th 08 I have uploaded a newer vesion of my software. It looks like for whatever reason the script isn't being generated and at this time this build is NOT working. Fix is coming April 11th...</strike>
 
As of April 10th 08 I have uploaded a newer vesion of my software. It looks like for whatever reason the script isn't being generated and at this time this build is NOT working. Fix is coming April 11th...</strike>
  
Build Fixed and working properly.
+
Build Fixed and working properly.
 +
 
 +
*Update
 +
 
 +
I have noticed on some computers a .autoreg file in the Firefox install directory. If this file exists it will cause the packager to not work because the '.' messes up the wix script. If you simply delete or remove this file while building this issue can be avoided. Build 1.0 will fix this bug.
  
 
http://daven.ca/build9/FirefoxPackager.zip
 
http://daven.ca/build9/FirefoxPackager.zip

Latest revision as of 11:06, 14 April 2008

Since my last build much as changed for my project. I started by creating a function that would count files and record them along with directories and build a small Wix script based on them. I tried to create a dynamic script that would package an extension and add it to an existing script. Unfortunately I learned that its almost impossible to combine two Wix scripts so I was somewhat at a dead-end. That is until I realized that I could use my new function on the Firefox directory as a whole. I tried it and with some bug fixing (by some I mean hours) I was able to re-invent my project but far more powerful.

Now all you need to do is point the program at your Firefox install directory and it makes an .msi file based on your Firefox. This means that all you have to do is install extensions,configurations or add-ons and as long as they are in your Firefox directory my program will package them all together and create an .msi file.

Pre-reqs

1) Firefox must be installed

2) Wix must be installed (and added to the system path variable)

Note that this build has been tested but its also likely that there are still tons of bugs. For my 1.0 build I will have these sorted out.


  • UPDATE

As of April 10th 08 I have uploaded a newer vesion of my software. It looks like for whatever reason the script isn't being generated and at this time this build is NOT working. Fix is coming April 11th...

Build Fixed and working properly.

  • Update

I have noticed on some computers a .autoreg file in the Firefox install directory. If this file exists it will cause the packager to not work because the '.' messes up the wix script. If you simply delete or remove this file while building this issue can be avoided. Build 1.0 will fix this bug.

http://daven.ca/build9/FirefoxPackager.zip



Source files

http://daven.ca/build9/WindowsApplication1.zip