New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add additional components from the Microsoft environment. #242

Closed
FSharpCSharp opened this Issue Jan 8, 2019 · 4 comments

Comments

Projects
None yet
2 participants
@FSharpCSharp
Copy link

FSharpCSharp commented Jan 8, 2019

When publishing the WPF components, it would be very good if the libraries of the following namespaces were also published, since some applications are based on them. Is it possible to include them?

        xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
        xmlns:i="http://schemas.microsoft.com/expression/2010/interactivity"
@batzen

This comment has been minimized.

Copy link

batzen commented Jan 8, 2019

I guess by http://schemas.microsoft.com/expression/2010/interactivity you mean the things from System.Windows.Interactivity.
If that's the case it's available at https://github.com/Microsoft/XamlBehaviorsWpf.
Only the namespaces changed and it's now http://schemas.microsoft.com/xaml/behaviors in XAML and Microsoft.Xaml.Behaviors in code.

@FSharpCSharp

This comment has been minimized.

Copy link

FSharpCSharp commented Jan 9, 2019

Oh, thanks for the tip. Indeed, that must have passed me by. Is there anything similar for the other namespace that I might have overlooked?

@batzen

This comment has been minimized.

Copy link

batzen commented Jan 9, 2019

That should, as far as i remember, already be part of wpf as it's used to define design time data etc.

@FSharpCSharp

This comment has been minimized.

Copy link

FSharpCSharp commented Jan 10, 2019

All right, thanks for the information. So much has happened here lately. I can change a lot in the product now to the new components, and thus almost exclusively on Open Source set. For this reason this issue is no longer necessary. I will therefore close it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment