First, the issue with linking code that uses STL/CLR should be fix and we sould not have LNK2022 when a template is not "instanciated" from the header (and we should neither have LNK 2020 error fro Clone method).

The following thread explain the problem and some workarounds: http://social.msdn.microsoft.com/Forums/is/vclanguage/thread/4f289f9f-6dfd-45d9-869e-4c3a1d7cd5d4

By the way, STL/CLR should be improved to make it easier to use and to switch between /clr options for differents scenario (built-in type, value struct, handle or instance to managed objects...)

By the way, it is very hard to make code that would compile both without /clr option and with the most restrictive /clr option which is /clr:safe because of a bad decision of using ^ and % instead of * and &. The net effect is that when we want to write code that could be used in both cases, we have a lot of artificial differences which make it a pain.

A simple example is why reference are not working when compiling with /clr:safe option and we have to use % instead in that case.

I hope to "partial property" likes "partial method".

// this is partial property declation
partial class SomeClass
{
public partial string PartialProperty { get; set; }
}

// and implemet it
partial class SomeClass
{
public partial string PartialProperty
{
get
{
return _partialPropertyValue;
}
set
{
if( value!=null ) throw new ArgumentNullException("value");
_partialPropertyValue = value;
}
}
}

if partial property not have implementation , thats compiled as auto property.
if partial property have 2 or more implementation , thats as error.

Senario: partial property + Roslyn & code generation.
programers descrive partial property declation , that was parsed with Roslyn, we can generate property implementation on another partial part.(example: setter validation, ConfigProperty , DependencyProperty and more patternd property implements)

Rather than showing the entire path of each file, the resultset can be displayed as a tree view. Considering the following results:


Find all "view", Match case, Subfolders, Find Results 1, Current Project: CBES - Crowd Monitor\CBES - Crowd Monitor.csproj, ""

C:\Users\ABM-7\Documents\Visual Studio 2010\Projects\CBES - Crowd Monitor\CBES - Crowd Monitor\Content\themes\base\jquery.ui.theme.css(15): * To view and modify this theme, visit http://jqueryui.com/themeroller/

C:\Users\ABM-7\Documents\Visual Studio 2010\Projects\CBES - Crowd Monitor\CBES - Crowd Monitor\Scripts\jquery-1.5.1-vsdoc.js(2732): props: "altKey attrChange attrName bubbles button cancelable charCode clientX clientY ctrlKey currentTarget data detail eventPhase fromElement handler keyCode layerX layerY metaKey newValue offsetX offsetY pageX pageY prevValue relatedNode relatedTarget screenX screenY shiftKey srcElement target toElement view wheelDelta which".split(" "),

C:\Users\ABM-7\Documents\Visual Studio 2010\Projects\CBES - Crowd Monitor\CBES - Crowd Monitor\Scripts\jquery-1.5.1.js(2585): props: "altKey attrChange attrName bubbles button cancelable charCode clientX clientY ctrlKey currentTarget data detail eventPhase fromElement handler keyCode layerX layerY metaKey newValue offsetX offsetY pageX pageY prevValue relatedNode relatedTarget screenX screenY shiftKey srcElement target toElement view wheelDelta which".split(" "),

... it can be displayed in a tree-view like:

Find all "view", Match case, Subfolders, Find Results 1, Current Project: CBES - Crowd Monitor\CBES - Crowd Monitor.csproj, ""

▼ C:\Users\ABM-7\Documents\Visual Studio 2010\Projects\CBES - Crowd Monitor\CBES - Crowd Monitor\
|
| ▼ Content\themes\base\jquery.ui.theme.css
| 15: * To view and modify this theme, visit http://jqueryui.com/themeroller/
|
| ▼ Scripts\

| ▼ jquery-1.5.1-vsdoc.js
| 2732: props: "altKey attrChange attrName bubbles button cancelable charCode clientX clientY ctrlKey currentTarget data detail eventPhase fromElement handler keyCode layerX layerY metaKey newValue offsetX offsetY pageX pageY prevValue relatedNode relatedTarget screenX screenY shiftKey srcElement target toElement view wheelDelta which".split(" "),
|
| ▼ jquery-1.5.1.js
| 2585: props: "altKey attrChange attrName bubbles button cancelable charCode clientX clientY ctrlKey currentTarget data detail eventPhase fromElement handler keyCode layerX layerY metaKey newValue offsetX offsetY pageX pageY prevValue relatedNode relatedTarget screenX screenY shiftKey srcElement target toElement view wheelDelta which".split(" "),

IMO, this way it would look more elegant!

As VS has file comparison built in, this should be easy. The most annoying part of all the autorecovery systems throughout Microsoft products is that the user is asked if they want to recover a file but not provided with enough information to make such a decision. Is the recovered file older or newer? Smaller or larger? Most directly, what are the exact differences, line by line? I always have to track down the backup copy and use an external comparer...

But in VS, it should be dead simple to offer users the option of first looking at a side-by-side comparison of the current file and autorecovered file.

I think the task board is a great step forward in lowering the developers effort to update their progress by making it easy for them to change their remaining work. This works great when working with the SCRUM 2.0 template. However, when you use the Agile template, I came across an interesting problem:

The problem is that from a managers perspective, progress tracking is done by comparing the completed and remaining work with the estimated work. A developer can easily change the remaining work, but why not add an additional dropdown so he/she can easily update the completed work? Now they have manually open the Task to update the "completed work" field.

Allow creating TFS projects without having to set permissions in 3 different areas. When we create a TFS project we need to set permissions in TFS, SQL Server, and Report Server.
We then add Windows groups to the appropriate groups in TFS, Sql Server, and Report Server.

Tried to automated this several times with no real luck. Googled everywhere for something to steal.

Lots of people have tried to use the TFSAdminstrationTool Proxy, however, it doesn’t work that well. Especially after they changed the authentication method to use: iTFSProxy.Connect(new Uri(collectionUrl), System.Net.CredentialCache.DefaultNetworkCredentials); That killed the silverlight project.

TfsPowerTools got scaled back so you can’t use it any more.

You can’t and shouldn’t set permissions with the TFS Admin Tool. It has a bad bug where permissions are not shown unless TFS permissions are set. So if you set sharepoint read only it won’t show up in the admin tool.

If you utilize work items appropriately, you'll end up with work items linked more than one level deep, i.e. Change Request - Requirement - Test Case - Test Task - Bug, etc.

The current query environment, would not allow you to find out all of the Requirements that are affected by a given Bug because the Bug would have to be a direct child of the Requirement and not the Test Task where it belongs. And while, you can take an existing work item and add links, this is a very convoluted way of achieving the objective with the contraints of the provided tools.

The query tool needs to be able to crawl through all links of the work items to achieve the reporting objectives.