Home Dashboard Directory Help
Search

TFS 2010 Power Tools Process Editor changes WIT xml without notification by Jesper Fernström


Status: 

Closed
 as Fixed Help for as Fixed


2
0
Sign in
to vote
Type: Bug
ID: 614880
Opened: 10/19/2010 2:40:25 AM
Access Restriction: Public
0
Workaround(s)
view
1
User(s) can reproduce this bug

Description

When using the new layout controls for work items introduced with TFS 2010 the Process Editor will remove or change xml elements and attributes it does not like.

Editing a WIT xml-file with a xml editor adding a LabelControl or WebPageControl and importing it to TFS will work fine. When you open the file with Process Editor it will make "in memory changes" to the xml. There is nothing to notify the user that this happens. It appears as if everything works fine. If the file is closed without any changes by the user these "in memory changes" are not saved. If the user makes any changes the file is marked with a star in VS to notify that it has been changed. When the user saves his/her changes the "in memory changes" that Process Editor made are saved as well.

Basically this means that once you have done anything "advanced" with your WIT the process editor MUST NOT BE USED EVER AGAIN for risk of losing your changes!
Details
Sign in to post a comment.
Posted by Microsoft on 2/15/2011 at 9:49 AM
Thank you. This will be fixed in the next release of the TFS power tools.
Posted by EricStob on 10/27/2010 at 10:43 AM
Oops I see you already did, my bad :)
Posted by EricStob on 10/27/2010 at 10:41 AM
Can you please provide precise example of what was in your xml, and what the editor changed it to?
Posted by Microsoft on 10/19/2010 at 10:13 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Posted by Microsoft on 10/19/2010 at 3:21 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.