Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I managed to fix it on our solution... drove me nuts, we could get away with disabling xaml validation on the build server by passing /property:ValidateXaml=false to our build script. However it became a showstopper when we couldn’t build the project in blend. Blend doesn’t follow the same build process as VS, perhaps it just shells out to msbuild.</p> <p>I added this to Microsoft.Silverlight.Common.targets just above the call to ValidateXaml:</p> <pre><code> &lt;Message Text="--------------- Start: Build Hack -------------------------" /&gt; &lt;Message Text="ReferenceAssemblies: @(ReferencePath);@(InferredReference-&gt;'$(TargetFrameworkDirectory)\%(Identity)')" /&gt; &lt;Message Text="ProjectAssemblies: @(BuiltProjectOutputGroupKeyOutput)" /&gt; &lt;Message Text="SilverlightPages: @(Page)" /&gt; &lt;Message Text="SilverlightApplications: @(ApplicationDefinition)" /&gt; &lt;Message Text="ProjectPath: $(MSBuildProjectFullPath)" /&gt; &lt;Message Text="AssemblyName: $(AssemblyName)" /&gt; &lt;Message Text="OutputPath: $(IntermediateOutputPath)" /&gt; &lt;Message Text="ShouldThrow: $(ThrowErrorsInValidation)" /&gt; &lt;Message Text="TargetFrameworkDirectory: $(TargetFrameworkDirectory)" /&gt; &lt;Message Text="TargetFrameworkSDKDirectory: $(TargetFrameworkSDKDirectory)" /&gt; &lt;Message Text="--------------- End: Build Hack -------------------------" /&gt; </code></pre> <p>... it looked like the ReferenceAssemblies were not correctly pulling in the correct references to the other silverlight projects, ValidateXaml seems to create an app domain and load in all those references to check if the types exist.... Anyway cut a long story short ValidateXaml wasnt getting passed the correct references as noted in visual studio thus we suspect it failed.</p> <p>We believed it to be something corrupt in our configuration, we fixed it in the end by simply removing all offending projects getting the build to run from the cmd line (i.e. msbuild.exe) and VS, then adding each project back. After it was all done we noticed some differences in the .sln, the problem code had a strange 'postProject' ProjectSection under one of our Silverlight projects.... but its largely one of those 'you'll never really know', the .csproj’s seemed to be the same. </p> <p>Remove the projects and add them back, worked for us. We suspect a corrupt solution file.</p>
    singulars
    1. This table or related slice is empty.
    1. POValidateXAML Failure on a TFS Build with a Silverlight 3 Project
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USKeith
    1. USKeith
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POValidateXAML Failure on a TFS Build with a Silverlight 3 Project
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAwesome, would mark yours as the answer, but SO won't let me for some reason.
      singulars
      1. PO
      1. USRay Booysen
    2. COno probs, welcome to Lab49 BTY :)
      singulars
      1. PO
      1. USKeith
    3. COHa, thanks Keith. :)
      singulars
      1. PO
      1. USRay Booysen
 

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