I think it would be better to get rid of the IronPython references as it's a pythonnet demo. Having it work with both might be nice, but I think it could be seen as a bit confusing.

The reason why ironpython is added - to make sure that Visual Studio XAML
designer can be used to design and check for errors interactively and with
intellisense using PTVS.

@tonyroberts, PTVS is officially supported by Python team at Microsoft.

So is there any alternative to not reference ironpython, e.g. to design
XAML without project? apparently this was possible in older versions of VS:

http://stackoverflow.com/questions/28375682/edit-standalone-xaml-with-visual-studio-intellisense

On Tuesday, March 15, 2016, Tony Roberts notifications@github.com wrote:

I think it would be better to get rid of the IronPython references as it's
a pythonnet demo. Having it work with both might be nice, but I think it
could be seen as a bit confusing.

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#185 (comment)

XAML is just a text file, so you can edit it using whatever text editor you like - VS is not required. I've used http://www.kaxaml.com/ in the past.

@tonyroberts I only agree partially with you. XAML is not just text file - it is rendered as GUI and for newcomers this visual part of designing in VS is essential. In VS 2015 you can even debug XAML! People may have success with kaxaml, but it has not been developed for 5 years - no issues, no pull requests! if there is any other alternative to VS WPF XAML designer, please let me know?

https://github.com/thinkpixellab/kaxaml

vim? notepad? My point is that these demos should be what you minimally need to demonstrate a feature. If you want to write blog posts or whatever about how to debug xaml using visual studio then that would be great, but cluttering code with reference to ironpython when it's not strictly necessary (and with no explanation of why it could be desirable) isn't the best way to highlight features.

@tonyroberts apparently it is possible to switch the interpreter in PTVS, so no issues with removing ironpython refs:

microsoft/PTVS#1156

@tonyroberts I removed ironpython refs long ago

BTW, here is another WPF demo:

https://github.com/hhspiny/WPFPy

I think a WPF demo should include some data binding.

According to contributing guidelines this pull has to be open for 2 weeks
for addressing comments, before closing.

On Thursday, June 23, 2016, Tony Roberts notifications@github.com wrote:

Closed #185 #185.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#185 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AHgZ5Xine4sdiaqwITdMEybQxb-3l2RZks5qOlbhgaJpZM4HvfsC
.

It was closed as a side effect of the develop branch being deleted. Please feel free to re-open against the master branch.

Which reminds me... I need to update the contributing file to say that PRs against master are now preferred!

Thanks for clarifying!

On Thursday, June 23, 2016, Tony Roberts notifications@github.com wrote:

Which reminds me... I need to update the contributing file to say that PRs
against master are now preferred!

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#185 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AHgZ5ZykDowtInDvBxegQIusDd5KcuxDks5qOmqhgaJpZM4HvfsC
.