.net unhandled exception

[sub]

Worked for me
Dave

Great.

[tomper]

Worked fine here too.

Thanks for the quick fix.

[IanSav]

Hi,

The updated installation package now installed for me as well (Windows XP SP3). Only one small anomaly noted, the "install.log" file was left in the root directory (C:\).

Thanks for the quick fix.

Regards,
Ian.

[soccerdad]

You hit it spot on. No problems now.

Thanks sub! It looks great. I am sure there will be some trying times with it, but I for one really appreciate your work and continue to be in awe.

[Ommina]

After a bit of fussing (mostly related to getting the original half-installed version out of the way), the new installation worked on my XP SP3.

Similar to IanSav's report above, I did end up with a number of files in the root of C:

Code:

KeyMappings.xml
empty.db3
npvr.db3
DigitalDevices.xml
AnalogDevices.xml
DeviceRules.xml
config.xml
Config-master-dont-edit.xml
install.log

I didn't check until after reading IanSav's post, so I don't know which of these files were created by the installer, and which by the application itself.

Edit: after deleting the files from the root and re-running the application, the files did not reappear, and settings changes from the previous instance were not lost.

Edit of the edit: For giggles, I did an uninstall and reinstall. The files listed above did not all reappear, although install.log did. (Perhaps the longer list was from the earlier, failed XP install.)

[sub]

After a bit of fussing (mostly related to getting the original half-installed version out of the way), the new installation worked on my XP SP3.

Similar to IanSav's report above, I did end up with a number of files in the root of C:

Code:

KeyMappings.xml
empty.db3
npvr.db3
DigitalDevices.xml
AnalogDevices.xml
DeviceRules.xml
config.xml
Config-master-dont-edit.xml
install.log

These were from the earlier attempted install, when it wasnt able to correctly identify the location for the data directory.

[IanSav]

Hi Ommina,

I had a similarly long list of files after my first install, with the broken installer. I cleaned up before using the fixed installer. The newer installer only left the "install.log" file in the root directory.

Regards,
Ian.

[mvallevand]

I had a check on some of my test boxes, and there was a bogus "Application and Setting" folder in the root to deal with.

It also looks like c:\install.log will get created every time the NRecord service is installed or uninstalled. It is NRecord doing this not the Setup program.

Martin

[imilne]

The vcredist is also leaving a bunch of files at the root of c: - is that to be expected?

Found some more info on this if anyone is interested... http://support.microsoft.com/kb/950683

[JEF]

Thanks Sub -- It worked for me as well