I'm writing a C# application using NeroCOM (v1.3, installed with Nero 6.3).
The problem is that the OnDoneBurn event is not called everytime!
It seems that something goes wrong and Nero doesn't call the OnDoneBurn event, but it happens randomly!!! I tried many times... but the event is not always called!!! However the CD or DVD burned is ok, but the application doesn't know when Nero finish the burning process...

Here's the main procedure of the program (in C# with VS.NET 2003).
Any suggestions? Thanx a lot.

private void btnBurn_Click(object sender, System.EventArgs e)
{
try
{
EnableControls(false);
Log("Burning...");

NEROLib.NeroDrives drives = nero.GetDrives(GetSelectedNeroMediaType());

NEROLib.NeroDrive drive = (NEROLib.NeroDrive)drives.Item(comboDrives.SelectedIndex);

NEROLib.NeroFileSystemDescContainer fs = new NEROLib.NeroFileSystemDescContainerClass();
fs.BurnOptions = NEROLib.NERO_BURN_OPTIONS.NERO_BURN_OPTION_CREATE_ISO_FS
| NEROLib.NERO_BURN_OPTIONS.NERO_BURN_OPTION_USE_JOLIET;
NEROLib.NeroDirectoryContainer dir = fs.RootDirectoryContainer;

for(int i = 0; i < listBoxFiles.Items.Count; i++)
{
dir.AddFile2(
Path.GetFileName(listBoxFiles.Items[i].ToString()),
listBoxFiles.Items[i].ToString(),
-1,
-1
);
}

drive.OnProgress += new NEROLib._INeroDriveEvents_OnProgressEventHandler(OnProgress);
drive.OnSetPhase += new NEROLib._INeroDriveEvents_OnSetPhaseEventHandler(drive_OnSetPhase);
drive.OnDoneBurn += new NEROLib._INeroDriveEvents_OnDoneBurnEventHandler(OnDoneBurn);

int speed = drive.WriteSpeeds.Item(drive.WriteSpeeds.Count-1);
Log("Speed: " + speed.ToString() + "x");

drive.BurnFileSystemContent(
fs,
NEROLib.NERO_BURN_FLAGS.NERO_BURN_FLAG_WRITE
| NEROLib.NERO_BURN_FLAGS.NERO_BURN_FLAG_DAO
| NEROLib.NERO_BURN_FLAGS.NERO_BURN_FLAG_DISABLE_EJECT,
speed,
GetSelectedNeroMediaType()
);
}
catch(Exception ex)
{
Log(ex.Message + nero.LastError);
EnableControls(true);
}
}

Some problems have been identified in the COM - .NET interaction which prevent NeroCOM from working properly in the .NET environment.

The next release will fix these issues.