I just upgraded my copy of CodeSite. Now CodeSiteEx does not work. Help!
Chances are you just upgraded from a pre-CodeSite 3 version to version 3 or later. The good news is you did not find a bug; this is a known issue. It is also an issue that is relatively simple to resolve. Between versions 2 and 3 of CodeSite, Raize Software made numerous architectural changes to CodeSite, including renaming object structures and the CodeSite unit itself. For instance, in CodeSite 2 you could add CSIntf to your USES clause and begin using CodeSite calls; as of version 3, you need to add CodeSiteLogging instead.
Perhaps the most significant change (to the CodeSite user) is the format of the new Send method calls. In older versions, CodeSite had distinct methods for sending various data types, such as SendInteger() and SendString(). These have been replaced, where possible, with a single overloaded Send() method.
If CSX does not work after upgrading your copy of CodeSite, simply update the CSX.INC file. You will find a conditional define (for example, {$DEFINE CodeSite3} ) that must be set to enable CodeSiteEx for your particular version of CodeSite. Details on this can be found in the Configuration section of the FAQ. After setting this conditional define, simply recompile your packages and CodeSiteEx should work properly.
If you still receive errors after doing this, chances are your source code has references to "old CodeSite", such as CSIntf in the USES clause or deprecated calls such as SendInteger() in your methods. The only "fix" for this is the manual replacement of the offending lines of code.