search

runceel / ReactiveProperty

ReactiveProperty provides MVVM and asynchronous support features under Reactive Extensions. Target frameworks are .NET 6+, .NET Framework 4.7.2 and .NET Standard 2.0.
MIT License
903 stars 101 forks source link

EventToReactiveProeprty from Assembly "ReactiveProperty.NET45" is built with an older version of Blend SDK #9

Closed TaviTruman closed 9 years ago

TaviTruman commented 9 years ago

This code results in an error when I'm using Blend 2015 and that's too bad because you can't use Blend to design WPF UI if you're using ReactiveProperty!

Here's the error message: Type type 'EventToReactive' from assembly 'ReactiveProeprty.NET45' is built with older version of the Blend SDK, and is not supported in a Windows Presentation Framework 4 project.

coreInteractivity:Interaction.Triggers

        <coreInteractivity:EventTrigger 
                x:Name="DataCardIsLoaded"
                EventName="Loaded" 
                SourceName="UIProgramInfoData">

            <reactiveProperty:EventToReactiveProperty
                    x:Name="ReactOnLoaded" 
                    ReactiveProperty="{Binding ReactOnLoaded, UpdateSourceTrigger=PropertyChanged}" />

        </coreInteractivity:EventTrigger>

        <coreInteractivity:EventTrigger 
                x:Name="FieldLayoutReactor"
                EventName="FieldLayoutInitialized"
                SourceName="UIProgramInfoData">

            <reactiveProperty:EventToReactiveProperty 
                    x:Name="ReactOnInitialized"
                    IgnoreEventArgs="False"
                    ReactiveProperty="{Binding ReactOnInitialized, UpdateSourceTrigger=PropertyChanged}" />

        </coreInteractivity:EventTrigger>

    </coreInteractivity:Interaction.Triggers>
runceel commented 9 years ago

Thank you for your feedback.

We have changed "project reference" and re-packaging the ReactiveProperty v2.2.5. Please confirm. (However we cloudn't reproduce your issue in our environment...)

TaviTruman commented 9 years ago

Thank you the problem seems to have been resolved.

Tavi

TaviTruman commented 9 years ago

Guys this problem has returned in the latest build.