<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Easily Debugging Custom Work Item Controls</title>
	<atom:link href="http://blogs.teamsystemnotes.com/2009/06/17/easily-debugging-custom-work-item-controls/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.teamsystemnotes.com/2009/06/17/easily-debugging-custom-work-item-controls/</link>
	<description>Just another WordPress.com weblog</description>
	<lastBuildDate>Fri, 05 Mar 2010 23:47:11 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: TFS 2010 Beta 2 – Custom Work Item Controls. Step 2, Work Item Setup &#171; nickhoggard</title>
		<link>http://blogs.teamsystemnotes.com/2009/06/17/easily-debugging-custom-work-item-controls/#comment-200</link>
		<dc:creator>TFS 2010 Beta 2 – Custom Work Item Controls. Step 2, Work Item Setup &#171; nickhoggard</dc:creator>
		<pubDate>Fri, 05 Mar 2010 23:47:11 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.teamsystemnotes.com/2009/06/17/easily-debugging-custom-work-item-controls/#comment-200</guid>
		<description>[...] Debugging Visual Studio instances: http://blogs.teamsystemnotes.com/2009/06/17/easily-debugging-custom-work-item-controls/ [...]</description>
		<content:encoded><![CDATA[<p>[...] Debugging Visual Studio instances: <a href="http://blogs.teamsystemnotes.com/2009/06/17/easily-debugging-custom-work-item-controls/" rel="nofollow">http://blogs.teamsystemnotes.com/2009/06/17/easily-debugging-custom-work-item-controls/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Can’t debug VS2010 from VS008 &#171; nickhoggard</title>
		<link>http://blogs.teamsystemnotes.com/2009/06/17/easily-debugging-custom-work-item-controls/#comment-189</link>
		<dc:creator>Can’t debug VS2010 from VS008 &#171; nickhoggard</dc:creator>
		<pubDate>Sat, 14 Nov 2009 02:46:50 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.teamsystemnotes.com/2009/06/17/easily-debugging-custom-work-item-controls/#comment-189</guid>
		<description>[...] I&#8217;ve done this before for Team Explorer 2008 and wasn&#8217;t anticipating any problems. The basic setup can be obtained using these instructions on the Team System Notes blog. [...]</description>
		<content:encoded><![CDATA[<p>[...] I&#8217;ve done this before for Team Explorer 2008 and wasn&#8217;t anticipating any problems. The basic setup can be obtained using these instructions on the Team System Notes blog. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VSTF Wannabe</title>
		<link>http://blogs.teamsystemnotes.com/2009/06/17/easily-debugging-custom-work-item-controls/#comment-159</link>
		<dc:creator>VSTF Wannabe</dc:creator>
		<pubDate>Fri, 14 Aug 2009 20:54:17 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.teamsystemnotes.com/2009/06/17/easily-debugging-custom-work-item-controls/#comment-159</guid>
		<description>I have figured out how to debug a custom control in TF and I want to post it here to help others who may need to do this for the future:

1.	Open up VS 2008 and load your project.
2.	Delete all breakpoints in your project.
3.	Right click on the project and go to the project properties.
4.	For the configuration, select Active (Debug).
5.	Under the enable debuggers section, check Enable unmanaged code debugging and enable the Visual Studio hosting process.
6.	Save.
7.	Right click on your project and click Clean.
8.	Right click on your project again and click Rebuild.
9.	In Windows Explorer, go to debug folder and copy the output (.dll, .exe., etc.) to the C:\Documents and Settings\All Users\Application Data\Microsoft\Team Foundation\Work Item Tracking\Custom Controls\9.0 (this is where TF 2008 WI looks for the .dll and .wicc files).
10.	On your toolbar with the drop down set to debug, click the arrow.
11.	You will get a mini screen with your control on it.  There should be a load button.  Click on it and make sure you load the .dll/.exe from the path specified in step 9.
12.	Leave it open and don’t close anything. Open up another instance of VS2008.
13.	In Team Explorer, open the Work item type that contains your custom control (Add Work Item-&gt; . . . . . ).
14.	Go back to the instance of VS2008 in step 1 and go to Debug-&gt;Attach to Process.
15.	In the attach to Process Window, leave the Transport as Default and the Attach To field to have checked managed code and native code.
16.	In the Available processes window, you will see the process devenv.exe with an ID and the title of the Work Item you just created.  Select that row and click on Attach.
17.	You will see some processing in the background as it is loading symbols.  Once it is done, set your breakpoints accordingly.
18.	Go back to your 2nd instance of VS2008 (step 12) and perform what you need to perform on the Work item you created in step 13 to make sure the break point gets hit.
19.	Once your feel the breakpoint is hit, go back to the 1st instance of VS2008 (step 1 and step 17) and you will see the breakpoints you set hit.  Now all you have to do is debug (sigh!).</description>
		<content:encoded><![CDATA[<p>I have figured out how to debug a custom control in TF and I want to post it here to help others who may need to do this for the future:</p>
<p>1.	Open up VS 2008 and load your project.<br />
2.	Delete all breakpoints in your project.<br />
3.	Right click on the project and go to the project properties.<br />
4.	For the configuration, select Active (Debug).<br />
5.	Under the enable debuggers section, check Enable unmanaged code debugging and enable the Visual Studio hosting process.<br />
6.	Save.<br />
7.	Right click on your project and click Clean.<br />
8.	Right click on your project again and click Rebuild.<br />
9.	In Windows Explorer, go to debug folder and copy the output (.dll, .exe., etc.) to the C:\Documents and Settings\All Users\Application Data\Microsoft\Team Foundation\Work Item Tracking\Custom Controls\9.0 (this is where TF 2008 WI looks for the .dll and .wicc files).<br />
10.	On your toolbar with the drop down set to debug, click the arrow.<br />
11.	You will get a mini screen with your control on it.  There should be a load button.  Click on it and make sure you load the .dll/.exe from the path specified in step 9.<br />
12.	Leave it open and don’t close anything. Open up another instance of VS2008.<br />
13.	In Team Explorer, open the Work item type that contains your custom control (Add Work Item-&gt; . . . . . ).<br />
14.	Go back to the instance of VS2008 in step 1 and go to Debug-&gt;Attach to Process.<br />
15.	In the attach to Process Window, leave the Transport as Default and the Attach To field to have checked managed code and native code.<br />
16.	In the Available processes window, you will see the process devenv.exe with an ID and the title of the Work Item you just created.  Select that row and click on Attach.<br />
17.	You will see some processing in the background as it is loading symbols.  Once it is done, set your breakpoints accordingly.<br />
18.	Go back to your 2nd instance of VS2008 (step 12) and perform what you need to perform on the Work item you created in step 13 to make sure the break point gets hit.<br />
19.	Once your feel the breakpoint is hit, go back to the 1st instance of VS2008 (step 1 and step 17) and you will see the breakpoints you set hit.  Now all you have to do is debug (sigh!).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VSTF Wannabe</title>
		<link>http://blogs.teamsystemnotes.com/2009/06/17/easily-debugging-custom-work-item-controls/#comment-158</link>
		<dc:creator>VSTF Wannabe</dc:creator>
		<pubDate>Thu, 13 Aug 2009 14:44:34 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.teamsystemnotes.com/2009/06/17/easily-debugging-custom-work-item-controls/#comment-158</guid>
		<description>CORRECTION!!!!

I MADE A MISTAKE ON SECOND.

THIS IS WHAT IT SHOULD BE: copy /Y &quot;$(TargetDir)*.*&quot; &quot;$(UserProfile)\Application Data\Microsoft\Team Foundation\Work Item Tracking\Custom Controls\9.0&quot;

I apologize</description>
		<content:encoded><![CDATA[<p>CORRECTION!!!!</p>
<p>I MADE A MISTAKE ON SECOND.</p>
<p>THIS IS WHAT IT SHOULD BE: copy /Y &#8220;$(TargetDir)*.*&#8221; &#8220;$(UserProfile)\Application Data\Microsoft\Team Foundation\Work Item Tracking\Custom Controls\9.0&#8243;</p>
<p>I apologize</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VSTF Wannabe</title>
		<link>http://blogs.teamsystemnotes.com/2009/06/17/easily-debugging-custom-work-item-controls/#comment-157</link>
		<dc:creator>VSTF Wannabe</dc:creator>
		<pubDate>Thu, 13 Aug 2009 14:30:44 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.teamsystemnotes.com/2009/06/17/easily-debugging-custom-work-item-controls/#comment-157</guid>
		<description>First, thank you for posting this as this helps some of us try to get better with this.

Second, I would suggest changing this line:

copy /Y &quot;$(TargetDir)*.*&quot; &quot;$(UserProfile)\AppData\Local\Microsoft\Team Foundation\Work Item Tracking\Custom Controls\9.0\&quot; 

to 

copy /Y &quot;$(TargetDir)*.*&quot; &quot;C:\Documents and Settings\All Users\Application Data\Microsoft\Team Foundation\Work Item Tracking\Custom Controls\9.0&quot; 

The reason is the path I have stated above is what I have seen others recommend to put the custom controls to.  Your path doesn&#039;t even exist on my machine.  I was getting some weird errors when I put in your path so that&#039;s why I changed it and it worked.  Let me know if you disagree and/or I am missing the point.

Third, I want to debug this when I have brought up a Work Item.  How do I do that? If I follow your steps, I just get the control brought up which is pretty useless; I want to debug the control as if I were debuggin an app.  If the control is clicked on the work Item, I want to debug it.  How would I do this so I can step through the code when it is part of the work item?

Thanks in advance.</description>
		<content:encoded><![CDATA[<p>First, thank you for posting this as this helps some of us try to get better with this.</p>
<p>Second, I would suggest changing this line:</p>
<p>copy /Y &#8220;$(TargetDir)*.*&#8221; &#8220;$(UserProfile)\AppData\Local\Microsoft\Team Foundation\Work Item Tracking\Custom Controls\9.0\&#8221; </p>
<p>to </p>
<p>copy /Y &#8220;$(TargetDir)*.*&#8221; &#8220;C:\Documents and Settings\All Users\Application Data\Microsoft\Team Foundation\Work Item Tracking\Custom Controls\9.0&#8243; </p>
<p>The reason is the path I have stated above is what I have seen others recommend to put the custom controls to.  Your path doesn&#8217;t even exist on my machine.  I was getting some weird errors when I put in your path so that&#8217;s why I changed it and it worked.  Let me know if you disagree and/or I am missing the point.</p>
<p>Third, I want to debug this when I have brought up a Work Item.  How do I do that? If I follow your steps, I just get the control brought up which is pretty useless; I want to debug the control as if I were debuggin an app.  If the control is clicked on the work Item, I want to debug it.  How would I do this so I can step through the code when it is part of the work item?</p>
<p>Thanks in advance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VSTS Links – 06/25/2009 - Team System News - Team System Rocks</title>
		<link>http://blogs.teamsystemnotes.com/2009/06/17/easily-debugging-custom-work-item-controls/#comment-81</link>
		<dc:creator>VSTS Links – 06/25/2009 - Team System News - Team System Rocks</dc:creator>
		<pubDate>Thu, 25 Jun 2009 11:28:37 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.teamsystemnotes.com/2009/06/17/easily-debugging-custom-work-item-controls/#comment-81</guid>
		<description>[...] Team System Notes on Easily Debugging Custom Work Item Controls [...]</description>
		<content:encoded><![CDATA[<p>[...] Team System Notes on Easily Debugging Custom Work Item Controls [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
