Welcome to EMC Consulting Blogs

Had been getting this recently in our builds, and have finally tracked it down to conflicting versions of the Microsoft.ReportViewer.Common.dll in our project references. This came about as one of our developers was using VS 2010, but the rest were still back on VS 2008.

Anyway, I thought I’d blog around how we traced this issue down in the end, as it has been perplexing us for quite some time now.

Step 1: Determine which project is causing the reference conflicts
Check your standard build output and make a note of the project file that was in the process of being built when the ResolveAssemblyReferences target failed.

Step 2: Turn on Detailed msbuild output for your build.
You can do this from within Visual Studio, under Tools, Options, Project and Solutions, Build and Run, MSBuild verbosity = Detailed

Step 3: Determine which reference is at fault
Do a build of the project file(s) that is/are causing these reference failures, and note the lines in the diagnostic build output, where you will see assembly references attempting to be resolved, but unable to find matching references. This should put you on the right track for resolving what has gone wrong with your solution.

I find that these settings work best for http://handbrake.fr/downloads.php for my HTC Touch HD phone.

Set picture size to Width 480 and Height 288

Set Video to MPEG-4(FFmpeg), and Target size (MB) to 800

Online events and recordings of previous events can be found here…

http://uktechdays.cloudapp.net/home.aspx

Thought I'd let you know how I managed to get the Windows 7 SP1 to finally install (it takes a while).

At first I had little luck, as it kept saying it was unable to install, and I was receiving this message

So then went online to find out how to fix this, and it told me to rund the following troubleshooter to fix problems with windows update here… (Start, Troubleshooting, Fix problems with windows update)

Which fixed two problems that it found with windows update…

And then after a couple of restarts and about 45 mins waiting around, finally it installed successfully…

Even though x:Name is a dependency property for a WPF framework element, you cannot the name of the control to a static resource in the code behind file

<Window x:Class="WpfApplication2.Window1"

        xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"

        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"

        xmlns:local="clr-namespace:WpfApplication2"

        Title="Window1"

        Height="300"

        Width="300">

    <Grid>

        <Grid.CommandBindings>

            <CommandBinding Command="local:AppCommands.Find"

                            CanExecute="CanFind"

                            Executed="CommandBinding_OnExecuted"/>

        </Grid.CommandBindings>

        <StackPanel>

            <TextBox Name="textBox1"/>

            <Button Command="local:AppCommands.Find"

                    Name="{x:Static local:Window1.MyControlName}"/>

        </StackPanel>

    </Grid>           

</Window>

…

namespace WpfApplication2

{

    /// <summary>

    /// Interaction logic for Window1.xaml

    /// </summary>

    public partial class Window1 : Window

    {

        public static readonly string MyControlName = "name";

Gives this compilation error

c:\Dev\.NET\WpfApplication2\WpfApplication2\Window1.xaml(17,21): error MC3079: MarkupExtensions are not allowed for Uid or Name property values, so '{x:Static local:Window1.MyControlName}' is not valid. Line 17 Position 21.