[wix-users] Separate Component for each SqlScript element?

[Christopher Painter]

Is that really a component rule violation or merely an issue with the component not reinstalling during the patch?   The SqlScript element doesn't have any file elements so I'm not sure the component rules apply here.    I'd wonder what the keypath of the component is.


Then again I'd also consider making this an application problem.  Most data access frameworks have some mechanism for doing code first database migrations at runtime.  It sure would make the installer simpler.


________________________________
From: wix-users <wix-users-bounces at lists.wixtoolset.org> on behalf of Edwin Castro via wix-users <wix-users at lists.wixtoolset.org>
Sent: Monday, May 14, 2018 11:16 AM
To: Ven H
Cc: Edwin Castro; WiX Toolset Users Mailing List
Subject: Re: [wix-users] Separate Component for each SqlScript element?

Every *new* SqlScript element needs to be under it's own *new* component.
The component rules say you cannot add a *new* File element under an
*existing* component. SqlScript is just another resource like File,
RegistryValue, Shortcut, and others.

--
Edwin G. Castro


On Mon, May 14, 2018 at 7:39 AM, Ven H <venh.123 at gmail.com> wrote:

> Thank you very much for the details. So, if I understand correctly, I
> should include every SqlScript element under it's own component as per the
> Component Rules.
>
> Regards,
> Venkatesh
>
> On Mon, May 14, 2018 at 7:43 PM, Edwin Castro <egcastr at gmail.com> wrote:
>
>> You are not allowed to change components. You are breaking the component
>> rules. Rob has a few blog posts on the component rules that you should read
>> and understand. I can't look them up right now, I'm on my phone, but I'll
>> look for them after I get to work.
>>
>> The only time you can change a component is if you are doing a major
>> upgrade *and* RemoveExistingProducts is scheduled early (so that all old
>> components are completely uninstalled before the new, different components
>> can be installed). For all other kinds of upgrades, including major ugrades
>> scheduled late, you cannot change components as the Windows Installer
>> engine requires components to be immutable.
>>
>> --
>> Edwin G. Castro
>>
>>
>>
>> On Mon, May 14, 2018, 04:43 Ven H via wix-users <
>> wix-users at lists.wixtoolset.org> wrote:
>>
>>> Sorry to bring this topic again. But, if we don't allocate individual
>>> component for each SqlScript, then Patch doesn't seem to be working
>>> properly. For example, if I have an SqlScript in first version and I add
>>> another SqlScript element in my Patch, if they are within the same
>>> component, it doesn't seem to be working. But if they are within their
>>> own
>>> components, then it seems to be working. Please advise.
>>>
>>> Regards,
>>> Venkatesh
>>>
>>> On Wed, Feb 28, 2018 at 5:37 PM, Nir Bar via wix-users <
>>> wix-users at lists.wixtoolset.org> wrote:
>>>
>>> > Since SqlComponent are not key paths anyway, you can nest some under a
>>> > single component
>>> >
>>> >
>>> >
>>> > --
>>> > Nir Bar, Independent WiX Expert. Creator of-
>>> > JetBA: WiX WPF Bootstrapper User Interface Framework
>>> >
>>> > JetBA++: WiX Native Bootstrapper User Interface Framework
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > ____________________________________________________________________
>>> > WiX Toolset Users Mailing List provided by FireGiant
>>> > http://www.firegiant.com/
WiX Support | WiX Experts and Resources from FireGiant<http://www.firegiant.com/>
www.firegiant.com
WiX Support | Installation, Development, Deployment | WiX Experts and Resources from FireGiant



>>> >
>>>
>>> ____________________________________________________________________
>>> WiX Toolset Users Mailing List provided by FireGiant
>>> http://www.firegiant.com/
>>>
>>
>

____________________________________________________________________
WiX Toolset Users Mailing List provided by FireGiant http://www.firegiant.com/