Would be good to create a install action that gives the current user access to the new section. It's confusing when the section don't show up after install.
Then I would like to ask if there is any plan to move away from NPoco and use the Umraco Core APIs (PetaPoco) against the database? I'm thinking that this might open up for this to work with SQLCE.
Any plans of open source the code? Would be useful for the community and I think you will be able to get some good contributions as well!
Regarding NPoco: I agree that it would be better to use the Umbraco APIs, but Umbraco itself is moving to NPoco in v8, so perhaps Footprint is just a little bit ahead. It may be the case that PetaPoco has some limitations that make implementing Footprint difficult.
But the core implementation based on peta poco has a lot more to it than the "vanilla" version of peta poco - ie. it make it super easy to support SQL Server, SQL CE and MySQL. That hassel is not really figured out in the standard peta poco-implementation.
Not sure about NPoco but it obviously don't work with SQL CE in the Footprint package =D
@Markus
The problem is not NPoco itself, it's SQL CE. We can't use all the features that SQL Express gives us. We have a good experience in Novicell with NPoco so that's why are sticking with it.
I think we are going to opensource the project, right now we are focusing on catching as many bugs as possible.
We are really exited about this project, so we want to give it our best.
Installation and refactor to use core ORM?
Hi!
Just installed the package! Great stuff! =D
Would be good to create a install action that gives the current user access to the new section. It's confusing when the section don't show up after install.
Then I would like to ask if there is any plan to move away from NPoco and use the Umraco Core APIs (PetaPoco) against the database? I'm thinking that this might open up for this to work with SQLCE.
Any plans of open source the code? Would be useful for the community and I think you will be able to get some good contributions as well!
Cheers!
Would love to see this open sourced as well :)
Regarding NPoco: I agree that it would be better to use the Umbraco APIs, but Umbraco itself is moving to NPoco in v8, so perhaps Footprint is just a little bit ahead. It may be the case that PetaPoco has some limitations that make implementing Footprint difficult.
True story!
But the core implementation based on peta poco has a lot more to it than the "vanilla" version of peta poco - ie. it make it super easy to support SQL Server, SQL CE and MySQL. That hassel is not really figured out in the standard peta poco-implementation.
Not sure about NPoco but it obviously don't work with SQL CE in the Footprint package =D
/ m
@Markus The problem is not NPoco itself, it's SQL CE. We can't use all the features that SQL Express gives us. We have a good experience in Novicell with NPoco so that's why are sticking with it.
I think we are going to opensource the project, right now we are focusing on catching as many bugs as possible.
We are really exited about this project, so we want to give it our best.
is working on a reply...