Nested install

[Nick Duane]

I see that there are many postings regarding nested installs. I read over
these and they've helped. However, I still want to validate my plan and
have an additional question. I've written an MSI for our product. We now
have a .NET version of our product. The installation procedure for our .NET
version is:

1. Install the non .NET version
2. Copy the new .NET files
3. Run some .NET installation routines against these new .NET files (i.e.
gacutil)

I'm thinking that the .NET msi should include the non .NET msi as a nested
install. Does this sound reasonable? Additionally, our non .NET install
has a bunch of options (by defining properties) you can specify on the
command line. How can I best implement this in this new install? My guess
is that I need to support the same list of properties in the .NET install
and pass them along, if they are defined, to the non .NET install. Is this
true?

Thanks,
Nick