Vladimir Kozlov

Hello! I just pushed a little fix to get rid of $(SolutionDir) as it might caused problems with building from command line. You can build it by using `C:\Program Files...

@sanderobdeijn thank you for reporting! I'm sorry for the late reply. I've never used XAML designer with this sample app (and not using XAML designer for long time as it's...

The ```target``` keyword is a great idea! I understand the logic behind combining stuff, but I don't like an idea of writing aliases for such a primitive thing as defining...

Yes, that's exactly what I need :-). Or at least be able to use alias overrides: ``` global alias Style(targetType) { ... } ``` And then we could use it...

Well, because I want to have some aliases to behave like a native language features. Like the ```@Style```. It will also help understanding and writing the UI code to our...

Common solution for such issues is to run a separate 64-bit process and communicate with it. So it could load any assembly without problems. I think many heavy VS plugins...

That's the idea I has proposed a month ago and there are my thoughts backing it: 1. `Lib.ammy` was conceived as kind of `BCL` - it should provide common set...

+1, we don't need this is in the release builds for WPF applications. So it would be great if Ammy doesn't include AmmySidekick if there are no `DEBUG` symbol defined....

@ionoy, I think it would be better to have separate assemblies for `ExpressionConverter` (`AmmyHelper.dll`?) and `AmmySidekick`.

@distantcam, have you seen the generated XAML code when the [inline binding converters](http://www.ammyui.com/documentation/syntax/#binding) are used? Ammy serializes C# code to the binding expression and uses `ExpressionConverter` as the binding converter,...