Home » Visual Studio

Could not load file or assembly "Microsoft.TeamFoundation.Build.Tasks.VersionControl.dll"

Hi all

I'm trying to create a custom work item if a build fails, but am getting this strange error message;
(Windows Vista Business, Microsoft Visual Studio 2010 Version 10.0.30319.1 RTMRel, Microsoft .NET Framework Version 4.0.30319 RTMRel)


My xml snippet is;

<UsingTaskTaskName="Microsoft.TeamFoundation.Build.Tasks.CreateNewWorkItem"AssemblyFile="$(TeamBuildRefPath)\Microsoft.TeamFoundation.Build.Tasks.VersionControl.dll"/><TargetName="CreateWorkItem"><CreatePropertyValue="$(WorkItemTitle) overriden by me!!"><OutputTaskParameter="Value"PropertyName="WorkItemTitle"/></CreateProperty><CreatePropertyValue="$(ErrorWarningLogText) &lt;a href='file:///$(DropLocation)\$(BuildNumber)\ErrorsWarningsLog.txt' &gt; $(DropLocation)\$(BuildNumber)\ErrorsWarningsLog.txt &lt;/a &gt;. "><OutputTaskParameter="Value"PropertyName="ErrorWarningLogText"Condition="Exists('$(DropLocation)\$(BuildNumber)\ErrorsWarningsLog.txt')"/></CreateProperty><MessageText="WorkItemTitle = $(WorkItemTitle)"/><MessageText="ErrorWarningLogText = $(ErrorWarningLogText)"/><CreateNewWorkItemBuildId="$(BuildNumber)"Description="$(WorkItemDescription)"TeamProject="$(TeamProject)"TeamFoundationServerUrl="$(TeamFoundationServerUrl)"Title="$(WorkItemTitle)"WorkItemFieldValues="$(WorkItemFieldValues)"WorkItemType="$(WorkItemType)"ContinueOnError="true"/></Target>

What is wrong? why can't it find the dll in question?




15 Answers Found


Answer 1

Hello Kedoo,


Are you using Teambuild 2008 or 2010?


If you are using 2010,  you considerate to create the WI using the workflow instead of msbuild?


Answer 2

Hi Alex,

I am using Teambuild 2010. How do I do this using work flow?

In my xml the custom work item is triggered in an OnError event. I'm not familiar with the solution you suggest. It would be good if you could include some links etc for this.



Answer 3

Hi Kedoo, by default TFS build  will create a work item if the build fails. Check out this post on how to modify the contents of the work item in TFS 2010 here:

Hope that helps


Answer 4

Hi Jakob

The link is great and I had seen it before. You see I'm not using a .proj file, instead I'm using .xml file, the reasion is that I'm executing remote commands on a Linux box and a .proj cannot be used in quite the same way. (I do know about power tools).

The link above is meant for a .proj file.

The problem here is a) DevEnvDir has a blank value, therefore b) TeamBuildRefPath has a blank value and c) Microsoft.TeamFoundation.Build.Tasks.VersionControl.dll does not exist.

I can fix a and b by using something similar to;

    <DevEnvDir Condition="'$(DevEnvDir)'==''">"$(ProgramFiles)\Microsoft Visual Studio 10.0\Common7\IDE"</DevEnvDir>

    <TeamBuildRefPath Condition="'$(TeamBuildRefPath)'==''">"$(DevEnvDir)\PrivateAssemblies"</TeamBuildRefPath>

but that's not desirable and in any case does not fix the problem of missing assembly. I have re-installed on two different machines (both with Vista) and the same problem persists.

The example provided in all MSDN/MS Blogs etc. is the same as what I have used (see original post) and yet this problem is not solved.



Answer 5

Keedo, as I said Team build  2010 uses a workflow to define the operataions in build process, one of those operation is to create a WI in case of failure.


The link Jakob sent show how to customize the workitem creation. You can change the witype, the title, or any other field.


The fact that you are using a linux have no relevance, because the work run in the build agent.


For more information in customizing the build process in tem build 2010 please reffear to this link: http://msdn.microsoft.com/en-us/library/dd647551.aspx


Answer 6

Alex, thanks. I understand all that, this doesn't answer the question of the missing assembly!

This is the top part of my make.xml file;

<?xmlversion="1.0"encoding="utf-8"?><ProjectDefaultTargets="SetEnv"xmlns="http://schemas.microsoft.com/developer/msbuild/2003"ToolsVersion="3.5"><ImportProject="$(MSBuildExtensionsPath)\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets"/><PropertyGroup><CleanCmd>clean:clean</CleanCmd><CompileCmd>compile</CompileCmd><PackageCmd>package</PackageCmd><InstallCmd>install</InstallCmd><ResultDir>C:\Builds</ResultDir></PropertyGroup><PropertyGroup><!--Enclose in "" since $(M2_HOME) path could include spaces--><Maven>"$(M2_HOME)\bin\mvn"</Maven><!--DevEnvDir Condition="'$(DevEnvDir)'==''">$(ProgramFiles)\Microsoft Visual Studio 10.0\Common7</DevEnvDir--><!--TeamBuildRefPath Condition="'$(TeamBuildRefPath)'==''">$(DevEnvDir)\IDE</TeamBuildRefPath--></PropertyGroup><!-- <<< >>> --><PropertyGroup><SkipWorkItemCreation>false</SkipWorkItemCreation><WorkItemType>Bug</WorkItemType><WorkItemFieldValues>System.Reason=Build Failure;System.Description=I did this</WorkItemFieldValues><WorkItemTitle>(I broke it)Build failure in build:</WorkItemTitle><DescriptionText>This work item was created by Team build  on a build failure (when I broke it).</DescriptionText><BuildlogText>The build log file  is at: somewhere</BuildlogText><ErrorWarningLogText>The errors/warnings log file is at: somewhere else</ErrorWarningLogText><UpdateAssociatedWorkItems>true</UpdateAssociatedWorkItems></PropertyGroup><!-- <<< >>> -->

This follows what's been described in the link priovided by Jakob and to which you refer. But it simply doesn't work!!

As for the link you provided, I've gone through this before [http://social.msdn.microsoft.com/Forums/en/tfsbuild/thread/5a52ac23-337b-4c77-913b-5034d202a190]. I'm not sure why the insistence that I should be using an xaml as opposed to xml, but in either case things don't seem to work.

This is a standard installation out of the box on two separate machine that don't work. It is even more frustrating when there are no information available and no-one from microsoft  seems to be available (or able) to answer these questions.



Answer 7



I understand that you are confused. I will try to explain better.


In TFS2008 the only way to perform any task was by using msbuild. Every operations such as Getlatest, label, create WI, copy files, etc....


The xml that you are pasting are msbuild tags.


In Team build  2010, MS changed the way that you define a build. For now on all the operations are defined using a workflow (xaml), only the compilation still using the msbuild (for obvius reasons) 


Using a workflow is much more powerfull, you can define try catch structures, you can use any framework namespace, you can easily understand the structure of the build, you can easily perform loops (anyone who tried do perform a simple loop in msbuild can say that only this would be a good reason to abandon msbuild do control workflow)


Bottom line: Although you still capable to create a workitem using msbuild xml, i strongly recomend that you do this using the xaml workflow. Any other recommendation that you find in the internet might refeear to the tfs2008!  



Hope helps!


Answer 8

Hi Alex

Thanks for taking the time to explain. I have read and researched a lot into xaml, but as a company we have made a decision to go with the xml solution. Without going into too much detail, it is not easy to change once a process has been established and approved.

I wonder, did you get a chance to look at the last link I pasted? (here it is just in case), Cathy Kong's answer (who apparently is a MSFT Moderator) was to reinstall with the invitation to let her know any follow up issues. Well I did that but she didn't even have the courtesy of replying. Looking at a lot of her so-called replies, they all say that the software should be reinstalled and that they should get back to her with any further queries that then she ignores.

Then again this seems to be the general attitude in MSFT, as soon as a question becomes difficult or complicated, it is ignored. A lot of these threads seem to end with someone from MSFT saying re-install and then not providing any real reasons or solutions.

Now there are two very real and separate issues here,

a) The original post: referring to opening a copy of DefaultTemplate.xaml - this was an out-of-the-box installation (on separate machines) and both installations were giving the same error.

b) No one had a reply/reason/solution for this. So fine I tried the xml route, even copy-pasted some source out of MSDN (see here) but the error mentioned here persists.

You see, the issue here isn't how I create a work item, the issue is why am I getting these errors? I don't even get as far as creating a work item, anything I override is ignored (see both of my xml snippets here). Why would a default xaml template supplied with the software not work? Why the system cannot find an assembly  that is so obviously part of tfs? If I need to install additional software, why does no-one seem to know what it is?



Answer 9

Hello Keddo,


I'm sorry, but in my vision, this is a community forum, with a strong presence of MS guys, they help a lot. I learn a lot here, and try to help other users.


If you need a official position from microsoft, i think thatt you should open a process in support.microsoft.com, accord with your support contract.


Answer 10

Hi Alex

Thanks for your reply. I'm really not that bothered about official positions or whatever, I'm just trying to get an issue resolved. That is the reason I've come to this forum and also the reason why I appreciate the time and effort people like you put into resolving them.

All that said and done, it is still not clear to me why the default xaml template comes up with over 50 errors?



Answer 11

Hi kedoo,

I am so sorry I didn't follow up the issue in your original thread.

I understand that your feeling, I am sorry I didn't supply a effective method. I will pay more attention to the threads I replied, continue to strengthen my technology knowledge and hope can help you.

About this issue, I recommend to submit it on http://connect.microsoft.com/visualstudio, and our engineers will take it into consideration and you will receive a quicker response.

Best Regards,

Cathy Kong


Answer 12

Hi Cathy

Thank you for your response.

I have done as you suggested and have submitted this issue on the connect website.

In time when I have a solution, I will update this thread for the benefit of others.



Answer 13

Hi kedoo,

Thank you for your feedback!

I think this will be helpful to improve TFS products.

Best Regards,

Cathy Kong


Answer 14

This issue is now solved.

For those who may be interested;

1) All my xml snippets posted here, I have now found out, refer to VS 2008 only! VS 2010 ignores them, hence the reason why I couldn't override default behaviour. See below for the solution;

2) Also the issue with DefaultTemplate.xaml causing 50 errors (and this is the silliest bit) is because just having Visual Studio 2010 on its own is not enough! You also have to install Visual Studio 2010 Professional (or higher) to get the assemblies that DefaultTemplate.xaml refers too! In other words with TFS you cannot modify a standard build  unless you purchase another license!

Both issues above will be resolved and you will be able to create your custmised work item and/or facny build scripts (llike ours) AFTER installing the Pro or higher version.



Answer 15

Hi kedoo,

I’m glad to hear that you got it working. Thank you for sharing your experience here.

It will be very beneficial for other community members having the similar questions.


Best Regards,

Cathy Kong




Hi, everyone, I met a problem here.

The situation is : I just reinstalled Visual Studio 2008 Team suite, and then rebuilt my projects.

And then I got the following error message:

The "Microsoft.Build.Tasks.Message" task could not be loaded from the assembly Microsoft.Build.Tasks.v3.5,
Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a. Could not load file or assembly 'Microsoft.Build.Tasks.v3.5,
Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies.
The module was expected to contain an assembly manifest. Confirm that the <UsingTask> declaration is correct,
and that the assembly and all its dependencies are available. NI.Framework.DataAccess

Does anybody know what the problem is this and tell me how to fix it?



Hi All,

I'm trying to get our automated build to compile the solution and run unit tests. The solution build fine but the unit tests dont run and the build log shows the error mentioned in this threads Title.

Here is my TFSBuild.proj:


<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="DesktopBuild" xmlns="http://schemas.microsoft.com/developer/msbuild/2003" ToolsVersion="4.0">
  <!-- Do not edit this -->
  <Import Project="$(MSBuildExtensionsPath)\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets" />
    <!-- Team Foundation Build Version - DO NOT CHANGE - Project File Version 2 and 3 produce the saem results-->
    <ProjectFileVersion>2 </ProjectFileVersion>

    <DropLocation>\\xxx\D$\Microsoft Team Foundation Server 2010\Builds\Optimus Build</DropLocation>
    <WorkItemFieldValues>System.Description=Start the build using Team Build</WorkItemFieldValues>
    <WorkItemTitle>Build failure in build:</WorkItemTitle>
    <DescriptionText>This work item was created by Team Build on a build failure.</DescriptionText>
    <BuildlogText>The build log file is at:</BuildlogText>
    <ErrorWarningLogText>The errors/warnings log file is at:</ErrorWarningLogText>

    <!--  SOLUTIONS  -->
    <SolutionToBuild Include="$(BuildProjectFolderPath)/Optimus.sln">

    <!--  CONFIGURATIONS  -->
    <ConfigurationToBuild Include="Debug|x86">

    <!--  TEST ARGUMENTS  -->
    <TestContainer Include="$(OutDir)\vsUnitTests.dll" />

    <!-- TEST ARGUMENTS  -->
    <MSTestRefPath>$(ProgramFiles)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies</MSTestRefPath>
    <DevEnvDir>C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE</DevEnvDir>

    <TestToolsTaskToolPath>C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\MSTest.exe</TestToolsTaskToolPath>


  <Target Name="AfterTest">
    <GetBuildProperties TeamFoundationServerUrl="$(TeamFoundationServerUrl)"
                        Condition=" '$(IsDesktopBuild)' != 'true' ">
      <Output TaskParameter="TestSuccess" PropertyName="TestSuccess"/>
    <SetBuildProperties TeamFoundationServerUrl="$(TeamFoundationServerUrl)"
                        Condition=" '$(IsDesktopBuild)' != 'true' and '$(TestSuccess)' != 'true' ">



How do I map the TestToolsTask to with the full file path to the \PrivateAssemblies\Microsoft.TeamFoundation.Build.ProcessComponents.dll.?


Here is the build log output:



Build started 2/07/2010 2:07:42 PM.
Project "C:\dev\tfs\optimus\Sources\tfsbuild.proj" on node 1 (default targets).
Project "C:\dev\tfs\optimus\Sources\tfsbuild.proj" (1) is building "C:\dev\tfs\optimus\Sources\tfsbuild.proj" (1:2) on node 1 (CoreCompile target(s)).
Project "C:\dev\tfs\optimus\Sources\tfsbuild.proj" (1:2) is building "C:\dev\tfs\optimus\Sources\tfsbuild.proj" (1:3) on node 1 (CompileConfiguration target(s)).
Project "C:\dev\tfs\optimus\Sources\tfsbuild.proj" (1:3) is building "C:\dev\tfs\optimus\Sources\tfsbuild.proj" (1:4) on node 1 (CompileSolution target(s)).
Project "C:\dev\tfs\optimus\Sources\tfsbuild.proj" (1:4) is building "C:\dev\tfs\optimus\Sources\Optimus.sln" (2) on node 1 (default targets).
  Building solution configuration "Debug|x86".
  The project "BusinessObjects" is not selected for building in solution configuration "Debug|x86".
  The project "CustomControls" is not selected for building in solution configuration "Debug|x86".
  The project "UserInterface" is not selected for building in solution configuration "Debug|x86".
  The project "Csla" is not selected for building in solution configuration "Debug|x86".
  The project "CDXfer.Service" is not selected for building in solution configuration "Debug|x86".
  The project "ResourceDependancies" is not selected for building in solution configuration "Debug|x86".
  The project "MimeDetect" is not selected for building in solution configuration "Debug|x86".
  The project "TestHarness" is not selected for building in solution configuration "Debug|x86".
  The project "VsUnitTests" is not selected for building in solution configuration "Debug|x86".
Done Building Project "C:\dev\tfs\optimus\Sources\Optimus.sln" (default targets).
Done Building Project "C:\dev\tfs\optimus\Sources\tfsbuild.proj" (CompileSolution target(s)).
Done Building Project "C:\dev\tfs\optimus\Sources\tfsbuild.proj" (CompileConfiguration target(s)).
Done Building Project "C:\dev\tfs\optimus\Sources\tfsbuild.proj" (CoreCompile target(s)).
Project "C:\dev\tfs\optimus\Sources\tfsbuild.proj" (1) is building "C:\dev\tfs\optimus\Sources\tfsbuild.proj" (1:5) on node 1 (RunTest target(s)).
Project "C:\dev\tfs\optimus\Sources\tfsbuild.proj" (1:5) is building "C:\dev\tfs\optimus\Sources\tfsbuild.proj" (1:6) on node 1 (TestConfiguration target(s)).
C:\Program Files\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets(1440,5): error MSB4062: The "Microsoft.TeamFoundation.Build.Tasks.TestToolsTask" task could not be loaded from the assembly \PrivateAssemblies\Microsoft.TeamFoundation.Build.ProcessComponents.dll. Could not load file or assembly 'file:///C:\PrivateAssemblies\Microsoft.TeamFoundation.Build.ProcessComponents.dll' or one of its dependencies. The system cannot find the file specified. Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask. [C:\dev\tfs\optimus\Sources\tfsbuild.proj]
Done Building Project "C:\dev\tfs\optimus\Sources\tfsbuild.proj" (TestConfiguration target(s)) -- FAILED.
Done Building Project "C:\dev\tfs\optimus\Sources\tfsbuild.proj" (RunTest target(s)) -- FAILED.
Done Building Project "C:\dev\tfs\optimus\Sources\tfsbuild.proj" (default targets) -- FAILED.


"C:\dev\tfs\optimus\Sources\tfsbuild.proj" (default target) (1) ->
"C:\dev\tfs\optimus\Sources\tfsbuild.proj" (RunTest target) (1:5) ->
"C:\dev\tfs\optimus\Sources\tfsbuild.proj" (TestConfiguration target) (1:6) ->
(CoreTestConfiguration target) -> 
  C:\Program Files\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets(1440,5): error MSB4062: The "Microsoft.TeamFoundation.Build.Tasks.TestToolsTask" task could not be loaded from the assembly \PrivateAssemblies\Microsoft.TeamFoundation.Build.ProcessComponents.dll. Could not load file or assembly 'file:///C:\PrivateAssemblies\Microsoft.TeamFoundation.Build.ProcessComponents.dll' or one of its dependencies. The system cannot find the file specified. Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask. [C:\dev\tfs\optimus\Sources\tfsbuild.proj]

    0 Warning(s)
    1 Error(s)

Time Elapsed 00:00:01.28


I have migrated my project to visual studio 2010 beta 2 recently. Still i am targeting 3.5 framework.
When i try to run the build from Visual studio 2010 command prompt i am getting the following error.

error MSB4062: The "Microsoft.TeamFoundation.Build.Tasks
.Label" task could not be loaded from the assembly c:\Program Files\Microsoft V
isual Studio 10.0\Common7\IDE\\PrivateAssemblies\Microsoft.TeamFoundation.Build
.ProcessComponents.dll. Could not load file or assembly 'file:///c:\Program Fil
es\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\Microsoft.TeamFou
ndation.Build.ProcessComponents.dll' or one of its dependencies. This assembly
is built by a runtime newer than the currently loaded runtime and cannot be loa
ded. Confirm that the <UsingTask> declaration is correct, and that the assembly
 and all its dependencies are available.

The machine i am building has only visual studio 2010 installed and doesnot contain any other prior versions.
My build scripts import the new version of Microsoft.TeamFoundation.Build.targets file.
Is there any other setting have to be changed?


TFS 2008 is installed on the same server

TSWA 2008 was install and apparently functioning

TSWA 2008 was removed in order to install TSWA 2008 SP1 (this appeared to work, although didn't test it for long)

I then tried to install TFSTimesheet, I had some problems with this, so decided to uninstall TSWA 2008 SP1, then reinstall

I have since tried to reinstall severaL times, after the last uninstall I removed all the TSWA sites and App pools (as there where now 4 of them)

Any help on this would be most appreciated

The error I'm getting

Could not load file or assembly 'Microsoft.TeamFoundation.Client' or one of its dependencies. Access is denied.Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.IO.FileLoadException: Could not load file or assembly 'Microsoft.TeamFoundation.Client' or one of its dependencies. Access is denied.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Assembly Load Trace: The following information can be helpful to determine why the assembly 'Microsoft.TeamFoundation.Client' could not be loaded.

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

Stack Trace:

[FileLoadException: Could not load file or assembly 'Microsoft.TeamFoundation.Client' or one of its dependencies. Access is denied.]
System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) +0
System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) +43
System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +127
System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +142
System.Reflection.Assembly.Load(String assemblyString) +28
System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +46

[ConfigurationErrorsException: Could not load file or assembly 'Microsoft.TeamFoundation.Client' or one of its dependencies. Access is denied.]
System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +613
System.Web.Configuration.CompilationSection.LoadAllAssembliesFromAppDomainBinDirectory() +203
System.Web.Configuration.CompilationSection.LoadAssembly(AssemblyInfo ai) +105
System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig) +178
System.Web.Compilation.BuildProvidersCompiler..ctor(VirtualPath configPath, Boolean supportLocalization, String outputAssemblyName) +54
System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) +229
System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) +261
System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) +101
System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean noAssert) +126
System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp, Boolean noAssert) +62
System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath) +33
System.Web.UI.PageHandlerFactory.System.Web.IHttpHandlerFactory2.GetHandler(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath) +40
System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig) +160
System.Web.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +93
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +155

Version Information:  Microsoft .NET Framework Version:2.0.50727.3082; ASP.NET Version:2.0.50727.3082


I tried to use the sample code in the SDK (Februrary 2007) WIbrownser (located in directory C:\Program Files\Visual Studio 2005 SDK\2007.02\VisualStudioTeamSystemIntegration\Work Item Tracking\WorkItemInterfaceSample)

When I run the sample I end up with the following error as soon as I try to connect to my server:

WIBrowser.vshost.exe' (Managed): Loaded 'C:\Program Files\Visual Studio 2005 SDK\2007.02\VisualStudioTeamSystemIntegration\Work Item Tracking\WorkItemInterfaceSample\bin\Debug\WIBrowser.exe', Symbols loaded.

A first chance exception of type 'System.IO.FileLoadException' occurred in mscorlib.dll

Additional information: Could not load file or assembly 'Microsoft.TeamFoundation.WorkItemTracking.Controls, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)

The assembly cannot be found in the GAC.  I tried to install it manually with GACUTIL without any success.

I un-install and re-install the SDK without any success. 

What is the problem?

Thanks in advance

Hi there, 

i use vs 2010 wih Msbee project to build target framework 1.1. I got error like below. I just check framework path and there is no assembly called  Microsoft.CompactFramework.Build.Tasks.dll. How could i setup that ? Framework 2.0 is installed and other patchs have been made.

The "CFResGen" task could not be loaded from the assembly C:\Windows\Microsoft.NET\Framework\v2.0.50727\Microsoft.CompactFramework.Build.Tasks.dll. Could not load file or assembly 'file:///C:\Windows\Microsoft.NET\Framework\v2.0.50727\Microsoft.CompactFramework.Build.Tasks.dll' or one of its dependencies. The system cannot find the file specified. Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.

Thanks in advance.

I'm using the Visual Studio 2005 SDK Version 4.0, and get an error when attempting to publish my windows based C# application.  The publish succeeds however when I start the app, and it attempts to update itself, I get the following error:

"Strong name signature not valid for this assembly Microsoft.TeamFoundation.Common.dll"

 Following errors were detected during this operation.
 * [7/18/2007 3:52:04 PM] System.Deployment.Application.InvalidDeploymentException (SignatureValidation)
  - Strong name signature not valid for this assembly Microsoft.TeamFoundation.Common.dll.
  - Source: System.Deployment
  - Stack trace:
   at System.Deployment.Application.ComponentVerifier.VerifyStrongNameAssembly(String filePath, AssemblyManifest assemblyManifest)

Has anyone seen this or know of a work around?


This happens when I use the following

      <TestContainer Include="$(SolutionRoot)\CRCTest\TestAll.orderedtest" />

From previous posts it looks like webtest and loadtest are supported in SP1. But I have Sp1 and Team System development system installed and I get

TeamFoundation.Build.targets : warning MSB4018: System.BadImageFormatException: Could not load file or assembly

I am not sure why this would not work and that it would work directly with MSTest.



I'am making an PowerShell script which run various Tfs related PS script. When a script fail, I want to send an email to all Tfs admin.

So I'am trying to get all e-mail address of all Tfs admin directly from TFS. I don't want to connect to a collection because I don't need it (and I don't want to hardcode a collection name), so I can't relay on the service IGroupSecurityService, instead I use the IIdentityManagementService. Here is the PS code:


$URI = New-Object System.Uri( "UsualURI to server" )
$tfsConfigSrv = [Microsoft.TeamFoundation.Client.TfsConfigurationServerFactory]::GetConfigurationServer( $URI );
$idmgt = $tfsConfigSrv.GetService( [Microsoft.TeamFoundation.Framework.Client.IIdentityManagementService] )
$SIDS = $idmgt.ReadIdentity( [Microsoft.TeamFoundation.Framework.Common.IdentitySearchFactor]::AccountName,
               "Team Foundation Administrators",
               [Microsoft.TeamFoundation.Framework.Common.ReadIdentityOptions]::None )

$UserIDs = $idmgt.ReadIdentities( $SIDS.Members,
                 [Microsoft.TeamFoundation.Framework.Common.ReadIdentityOptions]::None )

It's running fine but I get an array of TeamFoundationIdentity, which do not indicated the e-mail. I must obtain the Identity object instead to have the e-mail. I try to use IdentityHelper.Convert(...) which seem to exactly do that, but unfortunately I did not find how to get and a TeamFoundationRequestContext.

Somebody got an idea ?

Version: TFS 2010.


I cannot load Microsoft.TeamFoundation.WorkItemTracking.Client because a dependency is failing to load

"Microsoft.TeamFoundation.WorkItemTracking.Client.Datastore" version

could someone post a link to download an updated version of Microsoft.TeamFoundation.WorkItemTracking.Client.Datastore.dll

I can only seem to find version


I'm running VS 2010 Team Explorer version 10.0.30319.1 RTMRel on .net 4.0.30329 RTMRel on Vista Business SP2.

Tried to create a new custom build definition - a copy of DefaultTemplate.xaml. When I double click in Source Control, there are 50 errors displayed, mostly in the form of

'Assembly 'Microsoft.TeamFoundation.Common' was not found. Verify that you are not missing an assembly reference. Also, verify that your project and all referenced assemblies have been built.'

I have not changed any of the defaults, what I'm trying to do is to get Delphi 2006 automated-build setup on TFS.

What is causing this error? and how can I resolve it?



Hi , I have been trying to use 'ICommonStructureService '  , 'ReadOnlyCollection<>'  classes but

it needs Microsoft.TeamFoundation.Server.dll .

so I copied this dll from my TFS Webservices\bin\ ... directory , referenced it in my project .

But I am unable to see these classes listed .

Red Gate's .NET Reflector shows the verwsion of my Microsoft.TeamFoundation.Server.dll  as .

Which version do u need to have to use these classes ?

What update should I install ? plz give me link

else It would be also nice if someone upload this .dll for me .

I have been looking 2 days for this

Any help appreciated .Thnx!!



i have VS 2010 and TFS 2010 and all the latest update installed, but i still cannot find the Microsoft.TeamFoundation.Team.WorkFlow.dll file.

what package or SP should i install?



I created a project to customize a XAML Build proces with my own custom activities.

When I reference Microsoft.Teamfoundation.Build.Workflow, a warning appear, I can't build the project:

The referenced assembly "Microsoft.TeamFoundation.Build.Workflow, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL" could not be resolved because it has a dependency on "Microsoft.Build.Engine, Version=, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" which is not in the currently targeted framework ".NETFramework,Version=v4.0,Profile=Client". Please remove references to assemblies not in the targeted framework or consider retargeting your project.

Following errors:

The type or namespace name 'Workflow' does not exist in the namespace 'Microsoft.TeamFoundation.Build' (are you missing an assembly reference?)

I can not resolve this issue for the moment...

When installing the Team Foundation Server Build Extensions Power Tool April 2010, I have noticed that it doesn't register the assembly in the gac, leading to some confusion and aggravation.  Namely, you can't use the Activities until they've been registered by hand into the gac.  Is there a reason this isn't done in the installer?


I am using TFS2005 for version control and VS2008 for development. Recently we migrated our project to VS2010.

We have  a power shell script that we use for updating the build step. When I migrated the build server to VS2010, the below mentioned line throws error.


throws the below error.

 Unable to find type [Microsoft.TeamFoundation.Build.Proxy.BuildStore]: make sure that the assembly containing this type
 is loaded.

Still if I mannually trigger the Power Shell script on those machines where we haven't migrated to VS2010 the script doesn't throw any error. Please let me know how to get this name space installed on my build machine.  The build machine has VS2010 with .net framework 3.5 SP1 and 4.0 installed. I have tried installing Windows SDK, TFS Sidekicks and also have tried installing VS2008 SP1 along with the existing VS2010. But still the PS1 script throws the same error.

I found that this namespace has been deprecated TFS2008 onwards. But i do not know how the script was working on the build machine earlier which had VS2008 SP1.

Please help me in clearing this problem.

Thanks in adv!

Sudharsan Simhan



I am facing an exception in C++/CLI while dynamically loading assembly which itself an EXE created in C++/CLI managed mode using Assembly.Load. It successfully loads a dll assembly, but fails to load EXE assembly and generates following exception:

An unhandled exception of type 'System.IO.FileLoadException' occurred in TestManager.dll

Could not load file or assembly 'testAssembly, Version=1.0.3836.39802, Culture=neutral, PublicKeyToken=null' or one of its dependencies. Attempt to load an unverifiable executable with fixups (IAT with more than 2 sections or a TLS section.) (Exception from HRESULT: 0x80131019)

Note : TestManager.dll itself managed dll and loaded into another CLR process in CLI and trying to load EXE assembly as seperate process but fails and generates about exception.

This could probably be due to playing with mixed mode. I am stuck here and needs kind help.




I've got a solution that involves some custom MSBuild magic, so I've got a couple of class library projects in my assembly that contain the code for the custom MSBuild tasks.

When I try building the project in Visual Studio Professional 2008, I frequently have the problem that it fails to build those assembly projects because it complains that they're in use.

Everything works fine if it's the first build after launching VS, or if I run MSBuild from the command line. But if I start getting that error in VS, I have to completely exit VS and start it again before I can get the custom tasks to build again.

So my guess is that VS has some bugs with regards to not unloading custom task assemblies once it's finished building, or something? Is this known behaviour? Is there a workaround?


After installing Microsoft Security Patches, we're unable to use TFS Web Access due to this error:

Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Could not load type 'Microsoft.TeamFoundation.WebAccess.CompressionModule'. (D:\Program Files\Microsoft Visual Studio 2008 Team System Web Access\Web\web.config line 125)

Source Error:


Line 123:

Line 124:    <httpModules>

Line 125:      <add name="CompressionModule" type="Microsoft.TeamFoundation.WebAccess.CompressionModule"/>

Line 126:      <add name="ReportWrapperModule" type="Microsoft.TeamFoundation.WebAccess.ReportWrapperModule"/>

Line 127:    </httpModules>

Source File: D:\Program Files\Microsoft Visual Studio 2008 Team System Web Access\Web\web.config    Line: 125  

Thanks in advance for you help in resolving this issue.


Could not load file or assembly "System.Data.DLL" or one of its dependencies

<< Previous      Next >>

Microsoft   |   Windows   |   Visual Studio   |   Sharepoint   |   Azure