Starting today, Microsoft released Visual Studio 2012 product family release candidate. This release also marks the official “2012” naming which replaces what until now was known as “Visual Studio 11” for the beta. MSDN Subscriber Downloads link
When building a mixed solution with C# 4.0 and Silverlight projects, the following error may mislead you to believe something is wrong with the Silverlight project:MSBUILD : error : Copying file C:\Dev\Sources\MyProject\MyProject.Web\debug\bin\MyProject.xap failed. No Silverlight project specified for Silverlight output
In fact, what the error means is that the building of a XAP file cannot be done since there are no assemblies in the given output folder.
The solution, is changing the Output path in the Silverlight project properties under the Build tab to the main web project instead of “\bin\Debug” and \bin\Release”.
Alternatively you can edit the Silverlight’s .csproj file under...
Today I've encountered a strange error when opening the Source Control Explorer:
Team Foundation Error Method not found: 'Boolean Microsoft.TeamFoundation.VersionControl.Client.Workspace.OwnerNameMatches(System.String)'.
That denied any use of the source control.
I’ve tried re-applying Visual Studio 2010 SP1 and TFS 2010 SP1 but to no avail.
Eventually, only after a complete uninstallation and reinstallation of Visual Studio 2010 SP1 the error has gone. Hmmpf.
MSBuild has grown to quite a robust level since its introduction on 2003 and its inclusion in .NET Framework 2.0 in 2005. While its core engine and targets are rock-solid consistent, sometimes there are cases where the later additions introduced in .NET 3.5 and 4.0 just don't keep up with same level of stability. Today I had one of these cases. It came from WPF's Microsoft.WinFX.targets: c:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.WinFX.targets(269,9): error MC1000: Unknown build error, 'Cannot resolve dependency to assembly 'bar, Version=126.96.36.199, Culture=neutral, PublicKeyToken=null' because it has not been preloaded. When using the ReflectionOnly APIs, dependent assemblies must be pre-loaded or loaded...
Apparently there's a bug in the Process Editor when exporting a WIT. It happens when attempting to export a WIT to a file. The export was 'successful' - no error and no indication that something went wrong, and yet the export produced an empty XML. This occurs when the export took place offline, without prompting the user to re-connect to TFS.
The solution is to initiate a connection from the Team Explorer an repeat the export.
By default Microsoft Visual Studio Scrum 1.0 process template does not define the StateChangeDate field like MSF for Agile Software Development v5.0 does. In order to add it you need to modify the Work Item Types as follows:
Export the WIT (Task, Bug or Impediment) using the Process Editor or witadmin to a file.
Add the following block within the <FIELDS> element:<FIELD refname="Microsoft.VSTS.Common.StateChangeDate" name="State Change Date" type="DateTime">
<SERVERDEFAULT from="clock" />
<HELPTEXT>Date and time that the value of the State field changed.</HELPTEXT>
Save the file, and import it back to...
The MSDN article Choose a Process Template, describes the main distinctions between MSF for Agile and MSF for CMMI but doesn’t cover the newer Microsoft Visual Studio Scrum 1.0 process template. So here it is, MSDN’s lost article: “Main Distinctions between MSF for Agile and Scrum”.