Note that there are some explanatory texts on larger screens.

plurals
  1. POError 'TF215097:...Cannot create unknown type for...' custom CodeActivity
    text
    copied!<blockquote> <p><strong>Possible Duplicate:</strong><br> <a href="https://stackoverflow.com/questions/2910983/tfs-2010-custom-build-activity-tf215097-error">TFS 2010 Custom Build Activity TF215097 error</a> </p> </blockquote> <p>I'm trying to create a CustomActivity to run after each successful build.</p> <p>I've followed the exact steps of several tutorials</p> <ol> <li><p><a href="http://blogs.blackmarble.co.uk/blogs/rfennell/archive/2010/03/08/lessons-learnt-building-a-custom-activity-to-run-typemock-isolator-in-vs2010-team-build.aspx" rel="nofollow noreferrer">http://blogs.blackmarble.co.uk/blogs/rfennell/archive/2010/03/08/lessons-learnt-building-a-custom-activity-to-run-typemock-isolator-in-vs2010-team-build.aspx</a></p></li> <li><p><a href="http://www.ewaldhofman.nl/post/2010/04/29/Customize-Team-Build-2010-e28093-Part-4-Create-your-own-activity.aspx" rel="nofollow noreferrer">http://www.ewaldhofman.nl/post/2010/04/29/Customize-Team-Build-2010-e28093-Part-4-Create-your-own-activity.aspx</a></p></li> <li><p><a href="http://www.dotnetcurry.com/ShowArticle.aspx?ID=522&amp;AspxAutoDetectCookieSupport=1" rel="nofollow noreferrer">http://www.dotnetcurry.com/ShowArticle.aspx?ID=522&amp;AspxAutoDetectCookieSupport=1</a></p></li> </ol> <p>And all have lead me to the same result - The build fails after several seconds with this error:</p> <pre><code>TF215097: An error occurred while initializing a build for build definition \MyCompany\Dev - Client: Cannot create unknown type '{clr- namespace:BuildTasks.Activities;assembly=BuildTasks}TFSBuildLocalizer'. </code></pre> <p>I came down to a point where I have removed all custom references I had in the CodeActivity project and commented out all of the code.</p> <p>I have added the output dll to the TFS, and I have the following post build script in the project's properties:</p> <pre><code>"$(DevEnvDir)\TF.exe" checkout "$/MyCompany/Development/Djenne/Dev/Tools/BuildProcess/Output/$(TargetFileName)" copy /Y "$(TargetPath)" "C:\tfs2010\MyCompany\Dev\Tools\BuildProcess\Output\$(TargetFileName)" "$(DevEnvDir)\TF.exe" checkin "$/MyCompany/Development/Djenne/Dev/Tools/BuildProcess/Output/$(TargetFileName)" </code></pre> <p>I've made sure that the namespace in the workflow xaml is correct for the custom CodeActivity.</p> <p>I have no idea what else can I try,</p> <p>Please help!</p> <p>Thanks,</p> <p><strong>EDIT: I'm adding more descriptions about what I've already tried:</strong></p> <p>The CodeActivity class already have the attribute:</p> <pre><code>[BuildActivity(HostEnvironmentOption.All)] </code></pre> <p>The CodeActivity class is contained inside an Activity Library project. Here is the ProjectTypeGuids tag inside the csproj file:</p> <pre><code>&lt;ProjectTypeGuids&gt;{32f31d43-81cc-4c15-9de6-3fc5453562b6};{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}&lt;/ProjectTypeGuids&gt; </code></pre> <p>In the custom workflow xaml I've added my CodeActivity right after "Get Impacted Tests, Index Sources and Publish Symbols"</p> <p>I currently don'e have any InArgument nor OutArgument in my CodeActivity.</p> <p>These are the references in my CodeActivity project:</p> <ul> <li>Microsoft.CSharp</li> <li>Microsoft.TeamFoundation.Build.Client</li> <li>System</li> <li>System.Activities</li> <li>System.Core</li> <li>System.Data</li> <li>System.Data.DataSetExtensions</li> <li>System.Xaml</li> <li>System.Xml</li> <li>System.Xml.Linq</li> <li>WindowsBase</li> </ul> <p>In "Build Controller Properties" I have set the "Version control path to custom assemblies" with the same TFS path as my post build script: $/MyCompany/Development/Djenne/DEV/Tools/BuildProcess/Output</p> <p>In my Build Definition I've set "Build process template" with my custom workflow xaml.</p> <p>Thank you guys for the answers, do you have any more thoughts? Thanks</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload