Databases
StackOverflow2013
Postsdbo
POValidateXAML Failure on a TFS Build with a Silverlight 3 Project
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POValidateXAML Failure on a TFS Build with a Silverlight 3 Project
    primarykey
    data
    text
    <p>I have a Silverlight 3 project which compiles and runs fine when compiled on a development machine. On our TFS environment with Silverlight 3 and the Silverlight 3 SDK installed, I get the following error:</p> <blockquote> <p>C:\Users\tfsservice\AppData\Local\Temp\\Release\Sources\Source\Trunk\Themes\ UserDatesStyles.xaml(63,47,63,47): error : The property 'Command' does not exist on the type 'Button' in the XML namespace 'clr-namespace:Mvvm.Input;assembly=Mvvm'.</p> </blockquote> <p>More information: Command is an attached property on Button that is part of the Mvvm assembly in the Mvvm.Input namespace.</p> <p>Am I missing something on my TFS server? I would have thought that all I would require is the SDK. If I edit this project and change the ValidateXAML element to false, the TFS server does compile properly. However, this is obviously not the ideal situation.</p> <p>Here is the XAML that causes it:</p> <pre><code>&lt;ResourceDictionary xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:commands="clr-namespace:MvvmFramework.Input;assembly=MvvmFramework" xmlns:d="http://schemas.microsoft.com/expression/blend/2008" xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006" mc:Ignorable="d"&gt; &lt;Style x:Key="UserDatesStyle" TargetType="controls:UserDates"&gt; &lt;Setter Property="Template"&gt; &lt;Setter.Value&gt; &lt;ControlTemplate TargetType="controls:UserDates"&gt; &lt;Grid Height="600" Width="800" d:DesignWidth="800" d:DesignHeight="600"&gt; &lt;Button Content="Previous" commands:CommandBinder.Command="{Binding PreviousPageCommand}" Margin="0,0,10,0" Style="{StaticResource PrevBtn}" /&gt; &lt;/Grid&gt; &lt;/ControlTemplate&gt; &lt;/Setter.Value&gt; &lt;/Setter&gt; &lt;/Style&gt; &lt;/ResourceDictionary&gt; </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USRay Booysen
    1. USRay Booysen
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POValidateXAML Failure on a TFS Build with a Silverlight 3 Project
      1. USRay Booysen
      1. VTBountyStart
    2. VO
      singulars
      1. POValidateXAML Failure on a TFS Build with a Silverlight 3 Project
      1. This table or related slice is empty.
      1. VTBountyClose
    1. COI've heard of TFS Build having some issues when building Silverlight projects, although my team uses it all the time for the Silverlight Toolkit... if your development environment uses ValidateXaml, and check-ins are performed from such an environment, could you just make the call like you say to exclude XAML validation during official builds? We've had to do that when delay signing Silverlight apps, for instance, so the build can continue.
      singulars
      1. POValidateXAML Failure on a TFS Build with a Silverlight 3 Project
      1. USJeff Wilcox
    2. COdisabling ValidateXAML is possible but seems pretty hackish. I would prefer it ran and gave the same output as building in Visual Studio. Thank you for the comment.
      singulars
      1. POValidateXAML Failure on a TFS Build with a Silverlight 3 Project
      1. USRay Booysen
    3. COSame error if you login interactively to the build server under the build account, load the solution in Visual Studio, and build?
      singulars
      1. POValidateXAML Failure on a TFS Build with a Silverlight 3 Project
      1. USAidan Ryan
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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