search

microsoft / TemplateStudio

Template Studio accelerates the creation of new WinUI 3, WPF, and UWP apps using a wizard-based experience.
Other
2.7k stars 461 forks source link

SQLite as a data item #134

Open crutkas opened 7 years ago

crutkas commented 7 years ago

this would be a swell additional data item.

jamesmcroft commented 7 years ago

Agreed on this one

mrlacey commented 7 years ago

In terms of adding extra data items (e.g. this and cloud data) how are we considering the ability to add them compared with also including something that demonstrates how they're used.

i.e. If we add a 'data item', does it also need to include a View & ViewModel (as appropriate) that shows how to use them? To answer my own question, we probably want the optional ability to add a page that has the dependency like we do with the SettingsPage and the SettingsStorage feature. Right?

crutkas commented 7 years ago

you raise great discussion points @mrlacey that right now i don't have a solid answer to. I would honestly say we should have a skype call on it w/ anyone that would want to chat about it or talk about it at Build if you're there. I know Ginny is.

gcaughey commented 7 years ago

Yes definitely I'll be at Build and look forward to discussing it further. I think this type of discussion goes right to the heart of what would enterprise developers starting out with UWP need.

mrlacey commented 7 years ago

I'll be around for build too. Be good to talk

mrlacey commented 7 years ago

Added the 'Question' label as it's still not clear what this should actually do.

ArchieCoder commented 6 years ago

For the last 3 years, all my clients (2 enterprises and 1 customer) use SQLite. The pain point of integrating SQLite in a project is to find which good Nuget to use. There are a list of Nugets that are good and not so good (one that leverages async, some old, etc).

As @mrlacey said earlier, a settings page can serve as a good starting point for a SQLite template integration

crutkas commented 6 years ago

@ArchieCoder other than adding this, what would be a solid way to template this in. I think that is where we are a bit "how would this implemented in the best way possible". we know it is useful, just unsure of the implementation that would be generic yet not need a dev to delete 90% of it

ArchieCoder commented 6 years ago

@crutkas Would including a local analytics (i.e. no 3rd party) or local crash system logger based on SQLite a good example? Otherwise, I don't see generic implementation that could be useful for 90%+ projects.

ralarcon commented 6 years ago

It would be great for me to have a sample CRUD page where to understand how is an entity persisted, the better if the entity has a kind of "master/detail" relation... What about to base our sample data on SQLite? could this be a good scenario?

mrlacey commented 6 years ago

In terms of SQLite support, I am thinking we should provide the basis of a data access layer in the generated code. Having this point to the sample data would be a simple way of creating something that works and is usable.

CRUD functionality has some bigger blocking issues that are preventing us doing something in this area but which wouldn't prevent us adding SQLite based data.

mrlacey commented 6 years ago

Moved to 2.3 as this should really be done after we move to multi-project solutions and that won't happen until 2.3 at the earliest.

scottkuhl commented 5 years ago

Now that there is a SQL Server data service, is this also on track to be added?

mrlacey commented 5 years ago

Now that there is a SQL Server data service, is this also on track to be added?

No official time-frame yet but I expect it to come later this year. (I'm waiting to see if there's more feedback on the SQL Server option first.)