@ilann I've been busy with work for //Build, but I'm still investigating this. Don't worry, I'll keep everyone posted!
Thanks for the input @Theo! I've been investigating this, so I'll keep folks posted here once I have news. I hadn't expected such a large response to my tool when I released it, so I never thought about designing the UI to accommodate multiple XAML types. I think that will be the biggest challenge, so I want to make sure anything added isn't half-baked. I should have a bit of time later in February to finish my investigation in this area.
If we add this functionality to the app, it'd still only preview the UWP rendering of the Xamarin Forms XAML (vs. Android or iOS previews).
Would that still be of use to folks?
Thanks Javier and Rui, I'm talking to some folks on the Forms team already and planning to do some initial technical investigations. Will keep you posted here as plans unfold over the next couple of weeks!
Thanks Alec, It's something that's going to be looked at for sure! We'll keep folks posted as things go forward. Lots of requests and this is still a nights and weekend project for me at the moment. :)
3 votesin our backlogs · AdminMichael A. Hawker (XAML Studio Developer) (Software Engineer, Microsoft Garage) responded
Thanks for the suggestion James, I love the social sharing idea, as lowering that bar would be great to get more ideas and uses of the tool being shared. GitHub has been in my plan for a while, but I have a bigger plan around some of that work that got cut from V1. I’m thinking about all this though! :)
37 votesunder consideration · AdminMichael A. Hawker (XAML Studio Developer) (Software Engineer, Microsoft Garage) responded
This is going to need some technical investigations, but theoretically and hopefully possible. Lots of requests coming in, so keep voting!
@Christian these types of tools are for rapid prototyping and the ability to quickly test things out. Then you'd copy the result over to VS and hook up your code.
Thanks for the submission Andrew. It's theoretically possible with things like XAML Islands now, as it'd have to be recompiled to a WPF app to target loading WPF XAML. I used to work on WPF a lot when I was a developer for Microsoft Message Analyzer, I loved tools like XAMLPad and Kaxaml for this. I just have to load balance new features with the time I can spend on the project at the moment, so get your friends to up-vote this feature. :)
If we add WPF Support (https://microsoftgarage.uservoice.com/forums/918727-xaml-studio/suggestions/36549346-can-this-work-with-wpf-proper), I know this would be a good next step, please support that item as well!
Thanks Patrick, I think the new MSIX packager can help with this as well. Part of this is also a hosting requirement, so I'm not sure how that works as a Garage project. It gets a bit easier when open sourced, as then a GitHub release could have an installer. I'll keep folks posted here as things progress forward!
Thanks Patrick, I'll have to investigate this in the future when there's enough folks requesting it. I know it gets easier if we Open Source as folks can then run locally. But I know some environments are still locked down for traditional development too.
Thanks Theo, this isn't something on our roadmap at the moment. As a sandboxed app, we can't load dynamic assemblies. Our solution for this at the moment is to work towards open sourcing the tool. Then you can run it from Visual Studio and add in extra assembly references there.
@Wig would you mind sending us the XAML you're trying to use for us to test as well? You can e-mail us at xamlstudio at microsoft dot com. Thanks!
Thanks for the enthusiasm Tony! This is unfortunately outside the scope of the project at this time.
Thanks for submitting your idea. I'm not sure how feasible it would be to get the tool running on those platforms yet at the moment, but will keep an eye on this item as people vote and as these cross-platform technologies evolve.
Thanks for the suggestion Gianluigi, I just list everything through reflection, so it may be hard with so many entries to have an image for each one. I could think about if I could just show a preview of the control itself, but not all of them display something with no other data. I'll think about this a bit more.
9 votesin our backlogs · AdminMichael A. Hawker (XAML Studio Developer) (Software Engineer, Microsoft Garage) responded
Thanks for adding this suggestion. We know we have room to improve here on our custom IntelliSense implementation. we’ll definitely be looking into improvements moving forward.
2 voteshacking on this idea · AdminMichael A. Hawker (XAML Studio Developer) (Software Engineer, Microsoft Garage) responded
Testing if I can make sure this appears in the Toolbox with a small tweak. Otherwise will investigate more in the future. Will also look into how this can work better with DataContext Panel as it seems non-trivial.
v1.0.1 update will show DataGrid in the Toolbox. I'm going to follow-up with team about how to best set DataContext for it within XAML Studio still, so I'll leave this open.
Yeah, I was running from Debug in the Ch9 video. Looks like .NET Native optimized it out of the listing for the Toolbox, but it's still usable in the tool (I use it in the Settings panel so it's there!). It's just a hard control to databind the data context too. I should investigate a bit more. But will look to see about making sure it appears in the Toolbox in the future. Thanks!
Hi Giampaolo, thanks for posting. The control itself is supported, but are you referring to setting a DataContext to it dynamically in the DataContext window? If so, I'll have to investigate a bit more about that. Is it missing from the toolbox display as well? Any clarifications to your request would be great, thanks!
Thanks for the suggestion Paul. I was on the fence about including Syncfusion as they're a paid library. Once we can open source the project, then we can get a complimentary license to include in XAML Studio, but anyone wanting to use it would still need a license for their own projects (in most cases).
This'll be a great suggestion to have here though and see how other folks feel about this. And if in the Toolbox there was a filter for 'Open Source/Free' vs. 'Paid' libraries.
5 votesin our backlogs · AdminMichael A. Hawker (XAML Studio Developer) (Software Engineer, Microsoft Garage) responded
Thanks for the suggestion! This is definitely something I’ve thought about! I definitely want to improve these experiences and helpers like this in the future, so I’ll keep you posted when I get to it!
30 votesunder consideration · AdminMichael A. Hawker (XAML Studio Developer) (Software Engineer, Microsoft Garage) responded
Will definitely need to look into this in the future, but going to involve a lot of moving parts. I have some other ideas in the interim as well for your suggested scenario. Will post updates here as priorities get set moving forward. Thanks!
@Carl de Billy, see this item about Open Source https://microsoftgarage.uservoice.com/forums/918727-xaml-studio/suggestions/36548137-please-open-source-it
@Eric, I know it and am in contact. Will keep you guys posted as I know more about future plans. Lots going on to take in at the moment and this is still just a moonlighting project for me via the Garage.
Thanks Justin. We'll have to investigate how tech like Uno that bring UWP to the web could be leveraged for this type of thing in the future.
Thanks Matt and Oren. It's definitely something I think is super important and valuable. This being a Garage side-project for me and me being the core developer driving things, it was just a resource constraint for V1. I'll keep folks posted on the plan as things move forward with the tool and let you guys know!