.NET Zone is brought to you in partnership with:

Martin has worked with many customers in government, finance, manufacturing, health and technology to help them improve their processes and deliver more. He provides management and technical consulting that intends to expose processes and practices to gain transparency, uncover impediments to value delivery and reduce cycle-time as part of an organisations path to agility. Martin is a Professional Scrum Trainer as well as a Visual Studio ALM MVP and Visual Studio ALM Ranger. He writes regularly on http://nakedalm.com/blog, and speaks often on Scrum, good practices and Visual Studio ALM. You can get in touch with Martin through naked ALM. Martin is a DZone MVB and is not an employee of DZone and has posted 64 posts at DZone. You can read more from them at their website. View Full User Profile

TFS Integration Tools – Issue: AnalysisProvider Not Found

07.16.2012
| 2431 views |
  • submit to reddit

Issue

When you are trying to load your custom Adapter you receive a message stating that it does not exist.

image
Figure: AnalysisProvider 06a2457f-ebba-4979-bc5f-0f5006b8b4e6 not found

Applies To

  • TFS Integration Tools 2.2, March 2012

Finding

If you check the logs you will see the same message as the popup:

Application Error: 0 : [7/12/2012 2:41:32 PM] Microsoft.TeamFoundation.Migration.Toolkit.InitializationException: AnalysisProvider 06a2457f-ebba-4979-bc5f-0f5006b8b4e6 not found
   at Microsoft.TeamFoundation.Migration.Toolkit.SyncOrchestrator.CreateAnalysisEngine(Session sessionConfig, ProviderHandler leftProviderHandler, ProviderHandler rightProviderHandler, ITranslationService translationService, IConflictAnalysisService conflictAnalysisService)
   at Microsoft.TeamFoundation.Migration.Toolkit.SyncOrchestrator.ConstructSessionPipeline(Session config, Int32 sessionIndex, LinkEngine linkEngine)
   at Microsoft.TeamFoundation.Migration.Toolkit.SyncOrchestrator.ConstructPipelines()
   at Microsoft.TeamFoundation.Migration.Shell.ConflictManagement.ApplicationViewModel.m_constructPipelinesBW_DoWork(Object sender, DoWorkEventArgs e) 

Figure: Exception in Log

No new information there, but it does imply that there is a problem with the DLL, or that it is not there. I confirmed that it existed in the /Plugins/ folder but on starting a Debug session we see that the problem lies in the complication for .NET 3.5. .NET 3.5 relies on the .NET Framework 2.0 and the new TFS DLL’s all rely on .NET Framework 4.0.

Workaround

This problem is easily solved by changing the application settings from .NET Framework .NET 3.5 to .NET Framework 4.0 and recompiling.

image
Figure: Using an older version of the framework 

Now we are cooking.

Did this solve your problem?

Related Posts:

-Do you want to move to Visual Studio 11 Team Foundation Service NOW? Microsoft is providing a Go-Live licence (that means that it is supported in production) and you can use it today! For help moving forward contact info@nwcadence.com

Published at DZone with permission of Martin Hinshelwood, author and DZone MVB.

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)