Visual Studio 2015 Update 1 and XAML build templates -

so going ask original question, answer because found solution.

since upgraded dev box vs 2015 vs 2015 update 1, custom xaml template encountered error didn't seem cause. wondering why?

the build exception may seeing , saw: cannot set unknown member 'microsoft.teamfoundation.build.activities.runscript.failonnonzeroexitcode'(type xamlobjectwriterexception)

turns out microsoft made sort of schema change in vs 2015 update 1 adds property experienced 4 lines in xaml break automatic build templates if running vs 2015 build controller , agent(s). not sure if build controller can updated yet match, here found in 2 xamls:

good no property:

<mtba:runscript arguments="[advancedbuildsettings.getvalue(of string)(&quot;preactionscriptarguments&quot;, string.empty)]" displayname="run optional script before msbuild" enabled="true" filepath="[advancedbuildsettings.getvalue(of string)(&quot;preactionscriptpath&quot;, string.empty)]" sap2010:workflowviewstate.idref="runscript_1" /> <mtba:runscript arguments="[advancedbuildsettings.getvalue(of string)(&quot;postactionscriptarguments&quot;, string.empty)]" displayname="run optional script after msbuild" enabled="true" filepath="[advancedbuildsettings.getvalue(of string)(&quot;postactionscriptpath&quot;, string.empty)]" sap2010:workflowviewstate.idref="runscript_2" /> <mtba:runscript arguments="[advancedtestsettings.getvalue(of string)(&quot;preactionscriptarguments&quot;, string.empty)]" displayname="run optional script before test runner" enabled="true" filepath="[advancedtestsettings.getvalue(of string)(&quot;preactionscriptpath&quot;, string.empty)]" sap2010:workflowviewstate.idref="runscript_3" /> <mtba:runscript arguments="[advancedtestsettings.getvalue(of string)(&quot;postactionscriptarguments&quot;, string.empty)]" displayname="run optional script after test runner" enabled="true" filepath="[advancedtestsettings.getvalue(of string)(&quot;postactionscriptpath&quot;, string.empty)]" sap2010:workflowviewstate.idref="runscript_4" /> 

changed schema using update 1 (same 4 lines of code):

<mtba:runscript arguments="[advancedbuildsettings.getvalue(of string)(&quot;preactionscriptarguments&quot;, string.empty)]" displayname="run optional script before msbuild" enabled="true" failonnonzeroexitcode="true" filepath="[advancedbuildsettings.getvalue(of string)(&quot;preactionscriptpath&quot;, string.empty)]" sap2010:workflowviewstate.idref="runscript_1" /> <mtba:runscript arguments="[advancedbuildsettings.getvalue(of string)(&quot;postactionscriptarguments&quot;, string.empty)]" displayname="run optional script after msbuild" enabled="true" failonnonzeroexitcode="true" filepath="[advancedbuildsettings.getvalue(of string)(&quot;postactionscriptpath&quot;, string.empty)]" sap2010:workflowviewstate.idref="runscript_2" /> <mtba:runscript arguments="[advancedtestsettings.getvalue(of string)(&quot;preactionscriptarguments&quot;, string.empty)]" displayname="run optional script before test runner" enabled="true" failonnonzeroexitcode="true" filepath="[advancedtestsettings.getvalue(of string)(&quot;preactionscriptpath&quot;, string.empty)]" sap2010:workflowviewstate.idref="runscript_3" /> <mtba:runscript arguments="[advancedtestsettings.getvalue(of string)(&quot;postactionscriptarguments&quot;, string.empty)]" displayname="run optional script after test runner" enabled="true" failonnonzeroexitcode="true" filepath="[advancedtestsettings.getvalue(of string)(&quot;postactionscriptpath&quot;, string.empty)]" sap2010:workflowviewstate.idref="runscript_4" /> 

workaround/hack if don't/can't update build controller:

1. make changes templates , save them.
2. remove 4 properties in above lines: failonnonzeroexitcode="true"
3. save without making further changes xaml.
4. repeat process if change needed.

i testing see if can update our build controller update 1 see if permanently fixes issue , post back.