Closed mrlacey closed 2 years ago
how is this different than #229?
This issue is a request to be able to create a Xamarin.Forms app from the start. The output from this would be a shared library (or PCL) and multiple platform heads (iOS, Android, Windows, & others?) as if doing File>New>Xamarin.Forms. This is the request for the ability to do for Xamarin.Forms, what WTS does for UWP.
It appears something might be happening in this area....https://github.com/Microsoft/WindowsTemplateStudio/tree/xamarin
Added wiki page https://github.com/Microsoft/WindowsTemplateStudio/wiki/Xamarin
Is it support Xamarin-forms now?
We have multiple aspects of this built out, we are forming a plan of exact execution. We'll be sharing shortly for feedback
@crutkas Thank you
@nguyenthanhliemfc what, specifically, do you want from Xamaring.Forms support? What should (and shouldn't?) it include or enable you to do?
I would use this, and this would definitely help us. We now suffer a lot from 'set up costs' and it makes apps too expensive compared to web apps.
@mrlacey I think that bring Prism for Xamarin.Forms templates could be a great start point considering that Prism Template Pack already exists. https://marketplace.visualstudio.com/items?itemName=BrianLagunas.PrismTemplatePack
I would like to see push notification supported, When creating a new cross plat app, that's one of the things need platform specific code to get up and running.
How extensible is Windows Template Studio? I need to cache data on device and needs to be encrypted. If I wanted to add LiteDB support to bring that fucntionality in, can WTS be extended to make that an option?
@anotherlab what you're proposing are features. yes those would have to be thought about in terms of how that would work for xamarin and a dev but right now we're really looking for feedback on the actual implementation for the base.
@LocalJoost so you're ok with the hybrid approach we outlined here: https://github.com/Microsoft/WindowsTemplateStudio/wiki/Xamarin-approach
@jesulink2514 prism was one of the frameworks we were going to have for for Xamarin, but right now, we are heavily interested in the hybrid approach model we are proposing: https://github.com/Microsoft/WindowsTemplateStudio/wiki/Xamarin-approach
Would WTS support all of the current features for all platforms? IMO it would be potentially misleading if they weren't all supported.
Also what about naming. Supporting Xamarin branches outside of just Windows so Windows Template Studio wouldn't be an accurate name for the extension
@jamesmcroft I wouldn't focus on the name. That will solve itself.
are you talking if we did the hybrid approach, would UWP workflow have more options than a xamarin one, yes that is possible. The wizard would have to work that into the design.
There are very desktop specific scenarios and features.
@crutkas thinking back on this around Xamarin support, why couldn't this be its own thing that evolves on it's own. Windows Template Studio has this incredible system that backs it for creating these projects from the provided templates which leans well to having separate UI for the different platforms.
I can see possibilities where there are things developers might want/need for UWP but having this application for Xamarin that cannot support it or vice versa.
I also want to refer to #1311 where @bartlannoeye commented on supporting Xamarin Native. Is this something that will be considered?
@jamesmcroft It can be its own "thing" but at some point, someone has to do the work. We've had this as a work item for almost a year. We're proposing a solution that allows us to maximize our current investments and allows for companion iOS and Android applications. i'm fine with the system's ability to support native as well but UX has to be considered for these scenarios.
If you're proposing that you (or others) are willing to do the work, lets figure out where we can help and let you guys lead the effort :)
Would love to have a one-stop-solution for a cross-platform app.creation-tool using C#/.Net/Xamarin! Keep it coming!
Did this die on the vine?
Closing out this stale issue. Any potential future investment here would be in MAUI.
See the updated roadmap for our latest priorities.
From #319
Please add any specifics about what you'd like to see for Xamarin.Forms below.
https://github.com/Microsoft/WindowsTemplateStudio/wiki/Xamarin