>> Why? You'd have to ask the Windows Installer team.
Ah, understand. That was actually what I expected.
Thanks for the explanation, Rob!
-- Yan
On Sat, Feb 19, 2011 at 7:28 PM, Rob Mensching wrote:
> The MSI database is read-only. You can add information to the in memory
> copy but it is, of
The MSI database is read-only. You can add information to the in memory copy
but it is, of course, discarded when the install is complete. IIRC, the
Windows Installer does not let you modify the stuff read-only from the
database. I think that's just a restriction they enforce.
Why? You'd have to a
Yes, that's what I mean...
How is inserting temporary records possible then? I assume it inserts
temporary records to a certain view of the database in memory during install
time, right? Why isn't it possible to modify this view in memory, not only
inserting? Sorry if I'm asking the stupid things,
What do you mean "persistent data"? Are you asking why a CA can't modify an
MSI database? If so, the answer is: The Windows Installer opens the database
for read-only during install.
On Thu, Feb 17, 2011 at 1:55 AM, Yan Sklyarenko wrote:
> Hello WiX Community,
>
> Well, actually the subject tell
Hello WiX Community,
Well, actually the subject tells it all. I'm aware of this limitation, and
I've been successfully using the CA working with temporary data.
Now I'd like to know the reasoning behind this. Is it a technical
limitation? Why we can't "temporary" change the persistent data, just f
5 matches
Mail list logo
