"Custom" export processing.

In the system I am converting to COT there are several "CSV Exports" that really are creating configurations or scripts. These are free format text files that open in Notepad when the user hits a button.

An example would be a database view may contain a list of IIS web site names, site ids, directory paths, etc, and the user would press a button and get a text file that contains all the command line commands to create those directories and configure IIS.

This was done using the CSV export option in ISD because that already had 90% of the code. What would be the best way to do this in the COT framework?
1 person has
this question
+1
Reply