0.97/.net 2.0...how's the perfomrance?

[reven]

oh one bad thing, .net 2.0 seems to "crash" more now, before gbpvr would handle the crash internally and report it to the gbpvr.exe.log, now a lot of crashes will cause gbpvr to close and a error message be sent to the event log (but this error isnt as helpful and is harder to debug).

but thats only because of bugs to begin with

[sub]

@Sub: would it be possible to wrap the patches up in a new release?

I going to be doing that very soon.

[sub]

oh one bad thing, .net 2.0 seems to "crash" more now, before gbpvr would handle the crash internally and report it to the gbpvr.exe.log, now a lot of crashes will cause gbpvr to close and a error message be sent to the event log (but this error isnt as helpful and is harder to debug).

but thats only because of bugs to begin with

Yes, thats very correct.

The default behaviour of .NET 1.1 was to continue on if there was an unhandled exception on a background thread (for example, EPG update). .NET 2.0 treats this very differently, and instead terminates the application. This has accounted for nearly every failed recording I've looked into since v0.97 (though there is one other reason I'm aware of).

In the past this would have caused less impact because recordings would continue to happen, but some background logic may have stopped happening (File Conversion, EPG updates, Post Processing, Parallel Processing etc). These unhandled exceptions were never logged in the past, so we never knew they happened. Under the new .NET 2.0 scheme, the whole process will terminate, leading to failed recordings etc.

I wasnt aware of this until after v0.97 went out there. Much of the bug fixing since the release, and resulting patches, has gone into making sure unhandled exceptions were no longer possible on these background threads.

There is a setting that can be added to a .NET XML configuration file to get it to behave the same way as .NET 1.1, but this is just ignoring problems that were always there. I'd rather fix the problems.

[sub]

Another type of problem we've seen happening on .NET 2.0 is that some things are happening much quicker than they were previously, highlighting a problem with the Access database, which causes committed database updates not to be written to disk immediately. This can cause problems for logic that runs immediately after the updates occur, expecting the data to be there, but instead getting exceptions about inconsistant data.

In the old version of .NET, I had encountered this in a few place, and coded around it (with big sleeps in the code), but now I'm seeing these types of errors in a few more places.

...move on v0.98 when MS Access will no longer be an option.

[lingenfr]

...move on v0.98 when MS Access will no longer be an option.

Yeah!

[sub]

...move on v0.98 when MS Access will no longer be an option.

Yeah!

In case you dont already know, the alternative SQLite database option is already available in v0.97.

[dottore]

so overall it was a good idea to switch to .net 2.0. many unknown errors will be fixed then...

will you look into vista-compatibility? it works with vista, no problem, but every time i exit the config app, it crashes. it writes the changes but cannot restart the recording service.

one minor thing, since vista is not yet official...

[sub]

I'm not going to try vista myself yet, but if you post the logs for this error then I'm happy to take a look.

[dottore]

ok, will try it tonight and post the logs. by the way, if you didn't manage to get a vista-key you won't be able to install it. microsoft stopped the vista-download today.

[sub]

Dont worry, I'll definitly give vista a try with GB-PVR before vista is publically release - just not yet.