With the way that the TaskScheduler library handles paths, I would need to implement that code hack whenever my program goes to verify if the task action paths are valid.
My code path works like this...
Check if the task exists which uses a call to the doesTaskExist() function. That function first checks to see if the actual task exists. It then checks the ExecAction path and makes sure that the associated ExecAction path exists or not. This is where things can break down. If the library returns a path with quotes in it and I just feed it to a call of IO.File.Exists() then the program will think that the executable doesn't exist thus making the task invalid.
My code path works like this...
Check if the task exists which uses a call to the doesTaskExist() function. That function first checks to see if the actual task exists. It then checks the ExecAction path and makes sure that the associated ExecAction path exists or not. This is where things can break down. If the library returns a path with quotes in it and I just feed it to a call of IO.File.Exists() then the program will think that the executable doesn't exist thus making the task invalid.