An error occurred when trying to run.... 2.0.5.6

[Tromador]

Standard error box on run, follow by dump to desktop.

Error log:

2018//08/20 08:11:52 : Unable to access the python interpreter, this is fatal

2018//08/22 02:40:35 : Value cannot be null.
Parameter name: path

Not being funny and I know it's a beta and all, but any chance of a version which actually starts without an error? Hard to test when I can't even run/operate it.

[Tromador]

As far as I can see the right paths are correct in tdh.ini

If I try and run it again

2018//08/22 02:43:01 : Path cannot be the empty string or all whitespace.
Parameter name: path

2018//08/22 02:43:35 : Path cannot be the empty string or all whitespace.
Parameter name: path

[Tromador]

On reflection, having just rerun 2.0.42 and gone through the startup, I realise that 2.0.5.6 never asked me for a path to appconfig.xml - that is likely the problem.

[MarkAusten]

Not being funny but it starts every time for me and I do not publish something that doesn't work on my system. But that's what testing is all about and also something that I'm not good at. Like eyeonus I'm trying to get this done in my copious free time (ha!) and obviously things get missed.

That said, your deduction was right on the money and it is now fixed.

[Tromador]

Are you starting from clean every time?

Given that the app wasn't requesting all the required info, I struggle to see how it could have started correctly without a previously populated tdh.ini - I mean how can 2.0.5.6 have run for you, never having asked for appconfig?

If you aren't testing from clean each time, then this is the flaw in your QA. I always test from a clean installation, on the grounds that a new user would be doing exactly that without expectation of any previous installation info or files.

If it won't start from clean, it's broken :)

[Tromador]

And we all put in our time, be that coding, writing up the documentation, testing, or running a server. I thought that was taken as read. It's still frustrating to download a succession of releases that don't work.

Given your signature says that you find tact and diplomacy to be interesting theoretical concepts, I didn't think I needed to use them. ;)

[MarkAusten]

You are correct, you don't need to use them. Tact and diplomacy are theoretical concepts :) My reply was just a note that time pressures don't often make for good testing. Not in may case anyway.

I was fairly sure that I had started from scratch each time, although I have to say that I do this by getting Visual Studio to rebuild the project which deletes all the files in the output folder, including the ini and db files. Perhaps in my haste I only selected build project. Who knows?

It's even more frustrating to find that no matter what I do one issue keeps on re-occuring yet I've tested the heck out of it and it works every time. New build or update, no issue.