CS 16.0.3 CSIDE and DumpModuleConfigToFile / module INI files & properties files?

Gurus.

I'm sure this question has been asked - though I cannot find a definitive and current answer.

How does one go about regenerating a module's INI file using CSIDE - the equivalent of the old DumpModuleConfigToFile script?

I can successfully create a new module and generate the initial INI correctly, but can't see a ready process for updating if I up the module revision.

In same thread - what is considered the best practice for updating existing XLATES using CSIDE -- the only method I can see is to amend the .properties file directly, but when I build the module the change doesn't propogate to the installed module. Rather, I can only get these changes out to disk by exporting the module from CSIDE, which sometimes also generates 0kb files!!

Regards,

David Henshaw

Find more posts tagged with

Comments

Stephan_Baumann

The old DumpModuleConfigToFile is still available, but somewhat tedious to use and it has similar issues as the .properties file. There two ways to update the .ini file:

1. OScript Explorer and Outline View

From OScript Explorer locate your module's WebModule.os file and open it. Make sure you have also opened the Eclipse Outline View (Menu: Window->Show View -> Other -> General -> Outline). In the .os file edit the fVersion property for example, save the file and wait for the build to finish. Make sure the Outline View shows inherited features, this is controlled by the grey 'i' button on top of the view. You should see the '0 DumpModuleConfigToFile' in the Outline View; right click on it and select 'Run Script'.

Now the drawback: the module file is updated in the module folder of Content Server but the .ini file in your OScript Project is not (the same as with .properties files...), so you need to update the .ini in the OScript Project manually.

2. With Module Explorer

The script '0 DumpModuleConfigToFile' can also be started via Module Explorer. Navigate to the WebModule object of your module and display inherited features by enabling the grey 'i' button on top of Module Explorer. You should then see the '0 DumpModuleConfigToFile' script under the WebModule object. Right click on it and select 'Run Script'. This also updates the .ini file in Content Server's module folder so you need to update the .ini file in your OScript Project manually.

HFCDev

I can confirm that approach #1 works for me. I was looking for the same information after having just created a brand new module and wanting to add a dependency. At one point, editing the INI file in the src directory would cause a sync issue in Eclipse that would render your whole module foobar, but that seems to have been fixed a few release ago.

-Hugh