1

Closed

Produce errors when requirements are not met

description

I just realized that I don't have .NET Framework 3.5 which caused toastify to crash but it didn't really say what caused it. It would be easier to check at start which of the requirements are not met. Throw an exception when the framework doesn't match. The same applies to if there are not write privileges at the location where the config file is generated and so on.
Closed Aug 1, 2011 at 11:14 AM by nachmore
As per zowat's comment, this is a No Fix. Feel free to reopen if you feel otherwise!

comments

zowat wrote Mar 15, 2009 at 1:06 PM

I cannot check framework version from this application since it won't start without .NET Framework 3.5(3.0 should also work). It is up to the CLR to display that error.

The write privleges exception is handled in the current version and the uses gets a information message instead of an exception.

pompa wrote Mar 15, 2009 at 1:40 PM

The app. will start even with earlier versions of .NET BUT when it starts running version specific calls, it will crash then. Simply create a class which do all the checks and run that object in the beginning. (beware to use legacy method calls when running those checks).

If you want, I could experiment a bit with the source code and se it if works. In theory it should! ;)

Sign in to add a comment