If publishing reports to DTP is enabled in DTP Engines, copies of the analyzed files are stored in DTP Server. The appropriate version of a file is displayed when you enter the Violations Explorer, Test Explorer or Coverage Explorer. DTP Engines can also send copies of source files to DTP Server without analyzing code. See "Publishing Sources to DTP Server" in the DTP Engines for C/C++, Java, or .NET documentation.

1. Configure DTP Engine to publish source files to DTP Server
2. Run DTP Engine
3. The sources will appear in an explorer view

Benefits of Publishing Source Code from DTP Engines

• Enables fast access to source files without additional configuration in DTP Server
• Supports source files that are not stored under source control (such as auto-generated files during build)
• Allows you to display source files stored under source control systems that are not natively by DTP
• Provides support for source files that are modified, moved, or copied during build (i.e., files that get disconnected from original source control system).

Additional Considerations

• All analyzed versions of source files are stored at DTP Server.

Deleting Previously Published Source Code

Delete previously published source code by removing the content in the [INSTALLATION_DIR]/data/_DEFAULT_/dc/sources directory.

When code analysis from DTP Engines is rerun (with publishing source code enabled), the file versions will be recreated.

Static analysis violations, unit tests or coverage data that were reported for previously sent versions of files that are not re-published will no longer be displayed in an explorer view. If one of the other source code publishing methods is used, though, DTP may fall-back to another version.