Custom Diagnostic Files
In some VTScada applications, you may decided that there is a requirement for diagnostic files (as an example, an SQL data logger diagnostic file in which all queries to the SQL server are written for later analysis).
The following list contains guidelines and tips on diagnostic files and their storage.
- Do not add diagnostic files to your application's file manifest. There is seldom, if ever, a good reason to put the diagnostic file under the application's version control system. Further, diagnostic files can become large, making ChangeSets unwieldy.
- Consider creating a diagnostics folder somewhere outside the application.
- Create the diagnostics file with a .LOG or .DAT extension as VTScada will not automatically add these files to the application during synchronization.
