Integrate Registry tweaks in current preset

[BadHellie]

I think that it would be very convenient if NTL offered a list of Registry operations to integrate, which will be saved in the current preset. Such list will use the same format of standard .reg files (addition or deletion of keys or values). This way, one can avoid maintaining separate .reg files for a given Preset but can save everything inside a Preset. Thanks

 

[garlin]

I would disagree on including reg file content inside a preset, because it adds a lot of clutter to the preset. When I ask someone to post their preset, I will in fact read every single line to see if there's something wrong. Also makes it a pain to diff compare two presets.

The nearest thing NTLite could do is mimic what it does today with Update subscriptions. You would have a cached folder for reg files, divided up by when the reg file gets processed:

- Registry (offline image)​

- Post-Setup (Before logon)​

- Post-Setup (After logon)​

With a subscription model, then NTLite can auto-process the submitted reg files as needed. But definitely not store them inside a preset. I can imagine someone getting too excited and bloating the XML.

 

[tistou77]

You can put all your settings (registry keys) in a single REG file and your preset "saves" this REG file

    <Registry>
        <File>path of your REG file</File>
    </Registry>

That NTLite will apply during the process

 

[BadHellie]

I got your points. My idea was simply to avoid maintaining too many separate files for a single project. The solution including all Registry tweaks inside an xml Preset would have resulted more "centralized" and compact, closer to how I would have done things.
I understand the need of inspecting and comparing xml files for debug purposes; however all Reg entries could easily be placed at the end, so one who must inspect the xml can simply skip the last part. But it's ok, mine was just an idea ^_^