All events have changed. It is recommended to reimplement events instead of renaming them. The parameters will all be properly set by your development language. Move your code as described here: 

Old event	Changes to note
Adding	Move the status messages from this event to the FileStatus event. In the FileStatus event, you can consult the CurrentOperation property to customize your message depending on what you're doing. When the lBytesProcessed parameter = 0, the operation on that file is about to begin.
Deleting	Move status messages to the RemovingFile event.
Extracting	Move status messages to the FileStatus event in the same way as for the Adding event changes.
FileComment	Move file comment settings to the ZipPreprocessingFile event.
Fixing	This event no longer exists because the Fix method is no longer necessary.
GlobalStatus	The name and type of functionality has not changed, however you should make sure to reimplement the event, because parameter names and types have changed. See the GlobalStatus topic for details.
Listing	Move status messages to the ListingFile event.
Newdisk	Move the disk prompting dialogs or code to the InsertDisk event. Now you must set the bDiskInserted parameter to True when the user has confirmed inserting a disk, otherwise the process will stop with the xerInsertDiskAbort error.
PwdQuery	Move "file by file" custom password dialog box code to the ZipPreprocessingFile or UnzipPreprocessingFile events. Use the sPassword parameter to achieve the same functionality.
Rename	Move code that renames files to the ZipPreprocessingFile or UnzipPreprocessingFile events.
Replace	Move "replacing file" prompts to the ReplacingFile event. Keep in mind that you now have more information about the source and destination files. Set the bReplace parameter to False if you do not want a file replaced. Move "rename file" prompts to the ZipPreprocessingFile or UnzipPreprocessingFile events, and check the bExisting parameter to determine if a file should be renamed or not.
SkippingFile	The name and type of functionality has not changed, however you should make sure to reimplement the event, because parameter names and types have changed. See the SkippingFile topic for details.
Status	Move file status messages and progress bar updates to the FileStatus event.
Testing	Move status messages to the FileStatus event in the same way as for the Adding event changes.
Updating	Move status messages to the FileStatus event in the same way as for the Adding event changes. Keep in mind that the ZipPreprocessingFile and the UnzipPreprocessingFile events each have a parameter that tells you if the destination file exists or not.