Mihhail Maslakov
Mihhail Maslakov
Thanks, man! Just remembered. `AmmySidekick.dll` contains both runtime update logic and `ExpressionConverter` that is used for binding expressions. So, to exclude this dependency would mean binding expression not working anymore....
Ammy wouldn't require an open port in non-debug or `NO_AMMY_UPDATE` configuration. Port is opened as soon as the first element is registered with `Ammy.Register`. > could Ammy provide the code...
Yeah, separating binding logic into its own assembly seems like a good idea. Runtime update code is very platform specific, so bundling it with code that is not platform specific...
There is more code than just `ExpressionConverter`, so it isn't exactly compact. I can see a problem if there are multiple XAML-based projects inside the same solution that reference each...
Revealing `ExpressionConverter` code is not an issue. It's kinda open at the moment since you can decompile AmmySidekick. I like the idea of `ExpressionConverter` being included as an internal code....
Can you send me a sample project? Thanks!
It works fine for me in the WPF project. Maybe you have a firewall blocking the communication between Visual Studio and the application?
Hello @jregnier, Sorry, I missed your issue at the time. Do you still have this problem? MetroWindow should definitely work, it has been used with Ammy by a lot of...
Thanks, will investigate soon
AvaloniaUI doesn't have a separate platform library (AmmySidekick.dll) at the moment. We should probably create one, along with separate NuGet package, like `Ammy.AvaloniaUI`.