Commented Unassigned: Separate out scheduler UI into user control [12115]

June 3, 2015, 2:06 am

≫ Next: Commented Unassigned: Separate out scheduler UI into user control [12115]

≪ Previous: Source code checked in, #96191

$

0

0

The UI for configuring the schedule of a task (once/daily/weekly/monthly) is very nice. I'd like it to be a user control, please. That way I could use it in a simpler interface, that is without the advanced settings.


Proposed patch follows.
Comments: ** Comment from web user: iainiainiain **

Thanks, that's fixed.

I found another issue when the trigger edit dialog is open:
1. Change to "At log on"
2. Click the drop down on the Activate calendar. Then cancel the popup by losing focus by e.g. clicking on the Activate checkbox.
3. Uncheck the Activate checkbox
4. Change to "On a schedule"
5. It might immediately throw an exception:
Value of '0001-01-01 00:00:00' is not valid for 'Value'. 'Value' should be between 'MinDate' and 'MaxDate'

Weirdly, this is only reproducible some of the time, maybe 1 in 5 times. And I don't even know if step 2 is necessary. I'll try to have a further look at reproducing this if you can't easily, but I might have to leave it until next week.

---

Commented Unassigned: Separate out scheduler UI into user control [12115]

June 3, 2015, 8:56 am

≫ Next: Created Unassigned: TriggerEditDialog: DateTime out of range [12117]

≪ Previous: Commented Unassigned: Separate out scheduler UI into user control [12115]

$

0

0

The UI for configuring the schedule of a task (once/daily/weekly/monthly) is very nice. I'd like it to be a user control, please. That way I could use it in a simpler interface, that is without the advanced settings.


Proposed patch follows.
Comments: ** Comment from web user: iainiainiain **

On further investigation, the bug I was talking about above is preexisting. I'll open a separate issue for it.

This particular feature request---creating the user control---is now Guaranteed Bug Free. Well, AFAICT.

Created Unassigned: TriggerEditDialog: DateTime out of range [12117]

June 3, 2015, 8:57 am

≫ Next: Commented Unassigned: TriggerEditDialog: DateTime out of range [12117]

≪ Previous: Commented Unassigned: Separate out scheduler UI into user control [12115]

$

0

0

Run this code:
var trigger = new TimeTrigger();
trigger.EndBoundary = new DateTime(2016, 1, 1);
var dialog = new TriggerEditDialog(trigger, supportV1Only: false);
dialog.ShowDialog();

Then interactive with the dialog:
1. Uncheck Expire
2. Change to "At log on"
3. Uncheck Activate
4. Change to "On a schedule".

The following exception is thrown:

An unhandled exception of type 'System.ArgumentOutOfRangeException' occurred in System.Windows.Forms.dll
Additional information: Value of '0001-01-01 00:00:00' is not valid for 'Value'. 'Value' should be between 'MinDate' and 'MaxDate'.

Commented Unassigned: TriggerEditDialog: DateTime out of range [12117]

June 4, 2015, 1:52 am

≫ Next: New Post: COMException Issue

≪ Previous: Created Unassigned: TriggerEditDialog: DateTime out of range [12117]

$

0

0

Run this code:
var trigger = new TimeTrigger();
trigger.EndBoundary = new DateTime(2016, 1, 1);
var dialog = new TriggerEditDialog(trigger, supportV1Only: false);
dialog.ShowDialog();

Then interactive with the dialog:
1. Uncheck Expire
2. Change to "At log on"
3. Uncheck Activate
4. Change to "On a schedule".

The following exception is thrown:

An unhandled exception of type 'System.ArgumentOutOfRangeException' occurred in System.Windows.Forms.dll
Additional information: Value of '0001-01-01 00:00:00' is not valid for 'Value'. 'Value' should be between 'MinDate' and 'MaxDate'.
Comments: ** Comment from web user: iainiainiain **

It looks like valid DateTimes, in particular DateTime.MinValue, are not supported by WinForm's DateTimePicker. The latter has its own DateTimePicker.MinimumDateTime.

New Post: COMException Issue

June 15, 2015, 10:41 am

≫ Next: New Post: COMException Issue

≪ Previous: Commented Unassigned: TriggerEditDialog: DateTime out of range [12117]

$

0

0

I have a user of my program that contains this library and he's getting COMException exceptions along with the error message "The task image is damaged or tampered with". Has anyone else been seeing a lot of these lately?

New Post: COMException Issue

June 17, 2015, 9:48 am

≫ Next: New Post: COMException Issue

≪ Previous: New Post: COMException Issue

$

0

0

This is the first I have heard of this, but a quick internet search turned up these suggestions:

• http://answers.microsoft.com/en-us/windows/forum/windows_vista-performance/task-image-is-corrupt-or-has-been-tampered-with/91c0aef2-fa32-4795-8eb2-5c109cabe550
• http://www.ghacks.net/2011/07/28/fix-the-task-image-is-corrupt-or-has-been-tampered-with-errors/

New Post: COMException Issue

June 17, 2015, 10:15 am

≫ Next: Closed Unassigned: Separate out scheduler UI into user control [12115]

≪ Previous: New Post: COMException Issue

$

0

0

That's the funny thing, I rolled back to version 2.0 of the DLL and it instantly fixed it for the people who were having issues. I was using version 2.32 and that was causing issues for some people. Something changed between version 2.0 and version 2.32 that broke something but I have no idea what.

Closed Unassigned: Separate out scheduler UI into user control [12115]

June 22, 2015, 1:45 pm

≫ Next: New Post: COMException Issue

≪ Previous: New Post: COMException Issue

$

0

0

The UI for configuring the schedule of a task (once/daily/weekly/monthly) is very nice. I'd like it to be a user control, please. That way I could use it in a simpler interface, that is without the advanced settings.


Proposed patch follows.

---

New Post: COMException Issue

June 22, 2015, 7:42 pm

≫ Next: New Post: WeeklyTrigger starting at the wrong time

≪ Previous: Closed Unassigned: Separate out scheduler UI into user control [12115]

$

0

0

Between those versions, I added support for the new interfaces introduced in Windows 8. Other than bug fixes and task validation, only minor edits have been made since. In which version(s) of Windows are you seeing the error?

New Post: WeeklyTrigger starting at the wrong time

June 23, 2015, 4:30 am

≫ Next: New Post: WeeklyTrigger starting at the wrong time

≪ Previous: New Post: COMException Issue

$

0

0

Hi I have a problem with the WeeklyTrigger.
Today we have monday 23 of June.
I want to create a Task, which is called every tuesday. At the time where the code is executed + one minute.
The beginning should be 24. of June.
Now i have tried two solutions.

wt.StartBoundary = DateTime.Now.AddMinutes(1);

The first run of the task is on monday. The next run is on tuesday the next day. So like ist should, except the first execution.

So my other try was do add another day, so it will start on the next day, same time + one minute.

wt.StartBoundary = DateTime.Now.AddDays(1).AddMinutes(1);

The first execution on monday has now diassapeard. BUT the first call of the task is not tomorrow the 24 of June. Instead it is the 30 og June. So one week to late.

Hope you all understood what my problem is.
What am I doing wrong?

Thanks for your help.
Nice regards.

New Post: WeeklyTrigger starting at the wrong time

June 23, 2015, 5:53 am

≫ Next: New Post: COMException Issue

≪ Previous: New Post: WeeklyTrigger starting at the wrong time

$

0

0

Oh no.
I thought wie have Monday bu it's tuesday. So please igmore this thread -.-
I am sorry

New Post: COMException Issue

June 23, 2015, 6:34 am

≫ Next: New Post: COMException Issue

≪ Previous: New Post: WeeklyTrigger starting at the wrong time

$

0

0

Some users reported the issue on Windows 7 and Windows 8.x.

New Post: COMException Issue

June 23, 2015, 6:56 am

≫ Next: Source code checked in, #96679

≪ Previous: New Post: COMException Issue

$

0

0

Can you tell me which line of code causes the exception? If not, can you tell me what activities the users are performing relating to tasks when the exception occurs?

Source code checked in, #96679

June 23, 2015, 9:11 am

≫ Next: Source code checked in, #96680

≪ Previous: New Post: COMException Issue

$

0

0

* Added Spanish translations (not complete) * Fixed bug with Trigger.StartBoundary in UI

Source code checked in, #96680

June 23, 2015, 9:44 am

≫ Next: Source code checked in, #96681

≪ Previous: Source code checked in, #96679

$

0

0

* Changed "German - Germany" resources to generic "German"

---

Source code checked in, #96681

June 23, 2015, 10:16 am

≫ Next: Commented Unassigned: TriggerEditDialog: DateTime out of range [12117]

≪ Previous: Source code checked in, #96680

$

0

0

* Fixed bug related to changing trigger in UI from non-time trigger to time trigger losing StartBoundary

Commented Unassigned: TriggerEditDialog: DateTime out of range [12117]

June 23, 2015, 10:19 am

≫ Next: Source code checked in, #96684

≪ Previous: Source code checked in, #96681

$

0

0

Run this code:
var trigger = new TimeTrigger();
trigger.EndBoundary = new DateTime(2016, 1, 1);
var dialog = new TriggerEditDialog(trigger, supportV1Only: false);
dialog.ShowDialog();

Then interactive with the dialog:
1. Uncheck Expire
2. Change to "At log on"
3. Uncheck Activate
4. Change to "On a schedule".

The following exception is thrown:

An unhandled exception of type 'System.ArgumentOutOfRangeException' occurred in System.Windows.Forms.dll
Additional information: Value of '0001-01-01 00:00:00' is not valid for 'Value'. 'Value' should be between 'MinDate' and 'MaxDate'.
Comments: ** Comment from web user: dahall **

I believe this problem is corrected in the latest source code drop. It will be fixed in release 2.3.3.

Source code checked in, #96684

June 24, 2015, 8:43 am

≫ Next: Source code checked in, #96685

≪ Previous: Commented Unassigned: TriggerEditDialog: DateTime out of range [12117]

$

0

0

* Updated language resources (final)

Source code checked in, #96685

June 24, 2015, 9:30 am

≫ Next: Released: Release 2.3.3 (Jun 24, 2015)

≪ Previous: Source code checked in, #96684

$

0

0

* Tweaked UIs for spacing under Spanish * Fixed bug with event sources enumerating in UI

Released: Release 2.3.3 (Jun 24, 2015)

June 24, 2015, 10:04 am

≫ Next: Updated Release: Release 2.3.3 (Jun 24, 2015)

≪ Previous: Source code checked in, #96685

$

0

0

Some bug fixes, better support for Windows 8 additions to core library, addition of Fluent syntax, and crontab syntax, since the 1.9.4 release. Since 2.0.3 release, added support for .NET 2.0, 3.5 and 4.0, security handling, version compatibility handling (for connecting to up or down-stream versions), bug fixes, enhancements to history control and event trigger editor, compensation for deprecated email and message actions on Win8, and improved performance and marshalling. SeeSource Code for full details of changes. In 2.3.0, a more modern editor has been added as TaskOptionsEditor.

Download Descriptions

• TaskScheduler.zip - Includes the base library (Microsoft.Win32.TaskScheduler.dll) with no UI code. Works with .NET 2.0 and higher. Separate assemblies for .NET 2.0, 3.5 and 4.0. Add this assembly as a reference to interact with Task Scheduler on all systems with IE4 and later. This package is also available via NuGet with package name TaskScheduler.
• TaskSchedulerEditor.zip - Includes the UI library (Microsoft.Win32.TaskSchedulerEditor.dll) with all supporting assemblies. Works with .NET 2.0 and higher. Separate assemblies for .NET 2.0, 3.5 and 4.0. Add this assembly as a reference along with Microsoft.Win32.TaskScheduler.dll to get editor controls and dialogs that allow for viewing and editing tasks, triggers, actions, lists, etc. This package is also available viaNuGet with package nameTaskSchedulerEditor.
• TaskSchedulerHelp.zip - Includes the Microsoft Help compatible help files for both the base and editor libraries. Extract all files and then run Install_TaskScheduler.bat to integrate the help.