Using TFS Build Extensions 2010 Azure in TFS Build Process Templates

I'm trying to use the TFS Build Extensions Azure Actions to deploy to Azure as part of a TFS build.

I added actions from TfsBuildExtensions.Activities.dll and TfsBuildExtensions.Activities.Azure.dll and I can do any actions from TfsBuildExtensions to my build process and they work fine

The problems start when I drag and drop the activity from TfsBuildExtensions-Azure. The action title on the Gui display remains blank except for the general activity icon. The properties panel shows that the properties for this activity cannot be edited. Finally, when saving the build process template, it fails with the following error:

System.IO.FileNotFoundException: Could not load file or assembly 'ServiceManagement, Version=, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
File name: 'ServiceManagement, Version=, Culture=neutral, PublicKeyToken=null'
   at System.Signature.GetSignature(SignatureStruct& signature, Void* pCorSig, Int32 cCorSig, RuntimeFieldHandleInternal fieldHandle, IRuntimeMethodInfo methodHandle, RuntimeType declaringType)
   at System.Signature..ctor(IRuntimeMethodInfo methodHandle, RuntimeType declaringType)


What am I doing wrong or what link am I missing?


source to share

2 answers

I downloaded the project source code and found that the project file has a link to the ServiceManagement.dll file and the dll can be found in the original control.

Loading the DLL from their source and adding it to the project references resolved the issue.

I found a link on MSDN Blogs on ServiceManagement.dll that revolves around deploying to azure, but the original sources for the dll seem to be gone.



It is ideal to confirm that you are targeting the .NET 4.0 Framework and not the .NET 4.0 Client Profile. Sometimes the latter causes seemingly "obvious" assemblies to not load because they have dependencies that are not part of the client profile.

Not a solution per se, but for another way of debugging, you can enable fusion logging and use the Fusion Log Viewer to view assembly binding errors. At the very least, it will tell you where the runtime is looking for those assemblies it does not find.

Here are some clear instructions from Scott Hanselman on how to do this:



All Articles