Adding wix-users back to the thread.
To answer your last question first, I know of no real way of telling what
tool created the .MSI, except perhaps if Installshield has placed references
in the Registry table of the .MSI. You might see things like
"Installshield_InstallDriver)
If all you have is the .MSI to work from, you're in for a bit of work. Get
the platform SDK, install Orca, open up the .MSI and inspect it. This should
give you an idea of what to work towards, and a reference point to examine
the output from dark. You can actually edit the .MSI within Orca, but you
might want to do some reading first.
You might end up having to recreate some of the work. If the .MSI contains
custom actions, those can be extracted and re-incorporated into your
project, and if there are a lot of files, well, I'd just install it, copy
the files to a different place, and point my .wxs at them.
Personally, I've made the switch to WiX v3, as none of the open bugs affect
any of my projects. If this is your first time with Wix, I'd suggest v2,
there are excellent tutorials and plenty answered questions in the mailing
lists' archive. As Bob said in another email, Wix v2 is a low risk option,
Wix v3 is medium risk.
K
On 8/24/07, V K Gangwar <[EMAIL PROTECTED]> wrote:
>
>
> Thanks Karthik,
>
> I have few more doubts.
>
> I have .msi package with all .dll and .exe files.
> I have to add some more features in existing .msi package.
> What approach I should follow and what version of WiX tool I should use?
>
> What I did -
> I downloaded WiX 3.0 binaries nad votive3.0. Using dark I got my .wxs file
> (with few warnings, as I already mentioned), Now I am going throw the .wxs
> file and trying to understand this.
>
> Is my approach is right? Otherwise there is a better way to comeout from
> my problems.
>
> One more thing that how one will know that particular .msi is build from
> WiX tool only. As I know that there are so many tools to create a .msi file.
>
> Thanks!!
> Veerendra
>
>
>
> *Karthik Krishnan <[EMAIL PROTECTED]>* wrote:
>
> I don't think Dark has been completely updated for use with WiX v3 yet.
> You might have better luck with v2.
>
> That being said, I've never trusted the output from Dark for anything
> other than a reference point to begin work from.
>
>
> On 8/22/07, V K Gangwar <[EMAIL PROTECTED]> wrote:
> >
> > Dear All,
> >
> > First time I am using WiX. I am working on wix-3.0.2925.0-binaries. I am
> > using WiX with MS Visual Studio 2005.
> >
> > I have a .msi file which I have decompiled using dark.exe decompiler and
> > got a .wxs file. Again I tried to build this .wxs file with my application
> > code. Now I am getting errors.
> > What should I do? Is there any version mismatch problem. I have to add
> > some patch with my wix binaries because I read that wix3.0 is not
> > stable.
> > I also got few warnings while decompile the .msi file. Following are the
> > warnings.
> > Please help me.
> >
>
>
> ------------------------------
> Looking for a deal? Find great prices on flights and
> hotels<http://us.rd.yahoo.com/evt=47094/*http://farechase.yahoo.com/;_ylc=X3oDMTFicDJoNDllBF9TAzk3NDA3NTg5BHBvcwMxMwRzZWMDZ3JvdXBzBHNsawNlbWFpbC1uY20->with
> Yahoo! FareChase.
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
