I'll have to defer to others for those types of questions. There are some legal implications for making contributions (a special form needs to be snail mailed in).
Derek -----Original Message----- From: John Calcote [mailto:[EMAIL PROTECTED] Sent: Saturday, July 22, 2006 6:20 PM To: [email protected]; [EMAIL PROTECTED] Subject: RE: [WiX-users] Issue with 3.0 development release-missing libraries Derek, I'd love to help with the doc if you want. I'd probably need to ask a lot of questions along the way. How do I get started - I mean where do I look for doc sources, and such. Thanks, John >>> "Derek Cicerone" <[EMAIL PROTECTED]> 7/22/2006 5:34 PM >>> WiX 3.0 does not ship wixlib files because the WiX extensions are now completely self-contained in each extension dll. You should see a WixUIExtension.dll in the 3.0 releases. To use it, just specify "-ext WixUIExtension -cultures:en-us" in light and you're done. This will pull in the WiX UI libraries, all the binaries, and the English localized string resources for the UI. I'm not sure what other localizations are offered, but I know en-us is in there. In terms of upgrading from WiX 2.0 to 3.0, it sounds like you did it manually since you commented on some of the major schema changes. It's much, much easier to just run WixCop on all your sources. It will automatically update your source files to the latest schema. This tool is useful even after you convert to WiX 3.0 since it will continue to be updated to allow you to keep your source files using the latest schema. Here's the suggested way to run wixcop: 1. Backup all your source files, or just check them out if you use source management. 2. Run "wixcop -f -s *.wx*" to update all .wxs and .wxi files found in the current directory and all sub-directories. WiX is currently using .net 1.1 for maximum compatibility. The plan is to move to .net 2.0 sometime later this year just for WiX 3.0 (2.0 will stay on .net 1.1). We just want to hold off on that a bit longer because when that happens WiX 2.0 is really going to stop getting updates. We really need someone to volunteer to start updating the docs for 3.0 now that things are beginning to settle down a bit there. Hopefully someone can help out there soon. Please let us know if you have any other questions or feedback. Thanks, Derek -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Calcote Sent: Saturday, July 22, 2006 4:18 PM To: [email protected] Subject: Re: [WiX-users] Issue with 3.0 development release -missing libraries Sorry - I never finished my sentence in the first paragraph below. What I was trying to say, was that after working through the issues of the upgrade, I found it wouldn't link because the wixui library was not in root of the package directory, as it had been with the 2.0 package (odd that you folks don't have an MSI installer for WiX, don't you think? :) I tried moving the 2.x libraries into the 3.x packages, but these didn't link properly - they hadn't properly been upgraded. I also tried searching in your releases directory for other releases, but none of them had the wixlibs in the root directory of the packages. Finally, I tried building from source (after downloading and installing nant) - WiX apparently relies on VS.NET 2003 and the .NET SDK 1.1 - I've already moved on to VS 2005 and .NET SDK 2.0... what a pain! BTW, I LOVE this stuff. I've just barely begun with it, and I already feel comfortable with it and have recommended it to several others. John >>> "John Calcote" <[EMAIL PROTECTED]> 7/22/2006 5:10 PM >>> Hey, I was wondering why don't the wixlib libraries (wixui, etc) ship installed with the developer release? I have an installer with a GUI interface - I take advantage of the WIX UI (Mondo) interface. I tried upgrading my source to the 3.0 developer release. After working through the issues (one source file was generated by tallow - it used the src attribute on the file element - had to be changed to the newer Source attribute. Also had to change LongName to Name and remove the old short Name attributes on the File elements.) Incidentally, the reason for attempting to use 3.0 (unstable) rather than the 2.0 (stable) version was that I was having some verification issues with my installer under the 2.x release, and thought I'd try the new stuff before mentioning it to you. John ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ WiX-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ WiX-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ WiX-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-users
