MultiTrigger.ExitActions are not removed from Xaml correctly

MultiTrigger.ExitActions are not removed from Xaml correctly by Dragonranger

Closed

as Won't Fix Help for as Won't Fix

Type:	Bug
ID:	734115
Opened:	3/29/2012 5:51:21 AM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

A bug with storyboards when editing control templates that can cause Xaml code not to be removed automatically //and crash Blend when you click on the Xaml in designer.//

Edit: Actually the crash is likely unrelated as I have reproduced this many times without changing anything (see my second bug submission)

However the way I found this one originally was when I tried to run the program and it crashed. I debugged in VS and found that there was an extra line to stop an old storyboard I had deleted.

I reproduced this several times as well so it still remains a valid bug.

Details (expand)

Blend for Visual Studio 11 Beta

Bug

When editing a control template

- Create a trigger for example mouse over
- Choose to start a storyboard under "actions when activating"
- Choose to end the same storyboard under "actions when deactivating"

Everything works fine.

If you try to delet the storyboard from "actions when activating" it will normally complain about dependencies.

However on occasion if you mess around with the storyboards (adding removing) it will not remove the code from Xaml and if you click on the related pit of Xaml code it crashes Blend.

If you reopen and try to edit the template again it will crash Blend everytime. The code has to be manually removed from the xaml (can be opened and removed when not editing the template).

I have replicated this many times but I am not 100% sure how. Playing with the storyboards a bit nearly always works.

0 attachments

Hi, thanks for the bug report. I understand the frustration with the referential integrity not being cleaned up and the stability issues but this is not something we're going to have opportunity to address.

By the way, as a sanity check, this bug report says it was filed against 'Blend for Visual Studio 11 Beta'. That's incorrect, right? It was found in Blend 4 with a WPF project?

Many thanks,
Steve White (Blend Program Manager)