Commented Issue: Unsetting a trigger's end boundary in UI does not reset the trigger's EndBoundary property [10778]

using Microsoft.Win32.TaskScheduler.dll v1.9.2

Let's assume I configure a scheduled task this way, with an end boundary set on the trigger.
I get the following output :

```
Name : test
Enabled : True
LastRunTime : 01/01/0001 00:00:00
LastTaskResult : 0
State : Unknown
IsActive : False
NextRunTime : 01/01/0001 00:00:00
Should have run : 22/01/2013 09:00:00
Trigger #1:
Start boundary : 15/01/2013 09:00:00
End boundary : 22/01/2013 00:00:00
```

notice that IsActive and NextRunTime are correct as the trigger is deactivated because of the passed end boundary date

now when I unset this end boundary date from Trigger#1 :

```
Name : test
Enabled : True
LastRunTime : 01/01/0001 00:00:00
LastTaskResult : 0
State : Unknown
IsActive : False
NextRunTime : 30/01/2013 09:00:00
Should have run : 22/01/2013 09:00:00
Trigger #1: à 09:00 tous les jours, début : 15/01/2013
Start boundary : 15/01/2013 09:00:00
End boundary : 22/01/2013 00:00:00
```

IsActive still returns False, EndBoundary still returns the same date (and it shouldn't)
but NextRunTime is correct !

Hope this helps
LV
Comments: ** Comment from web user: lvorburger **

Hi, thanks for answering
Indeed when using your task editor API, things work fine.
I am using Windows XP standard scheduled tasks UI.

Check the attached screenshot (sorry, in French) : I unchecked "expires" in the Win XP UI and it's still set in TaskDialog (which is "normal" as the expiration date is still set)

Guess the problem lies in Win (XP at least, I have no other version to test)...