I checked out the demo site and the Admin Dashboard. Seems to have everything needed to host an ecommerce site... except, I didn't find any payment gateway integration. Even checked http://demo.simplcommerce.com/Admin#/configuration and didn't find it.
Any plans to integrate payment gateway or API (ex Stripe ) in the near future, or was I not looking in the right place?
P.S. Any recommendations for hosting this? Can this be deployed on Amazon Lambda? Or will I need Azure? How about traditional hosts like DiscountASP.Net? Any pro and cons you are aware of?
I second parent's suggestion here though, Stripe API is a great place to start.
Are there any parts of the project you could highlight as being much harder or easier as a result of building it in .NET Core over, say, .NET 4.6?
1. entity framework core code first does not support table per type inheritance, which makes database migration necessary
2. some libraries do not support .NET Core yet
These APIs are almost entirely coming from .NET Standard 2.0. See the jump in APIs in this table.
We often get asked if this is going against the promise of a light-weight development platform. Answer: not really. The new APIs are not being added to a single library, but several, including new ones. We will be updating our publishing tools to make it easier publish apps w/only the libraries you need. We are also looking at going one step further, which is publishing only the IL you need (intra-assembly optimization).
I am spending the week presenting at two Microsoft conferences in Europe (Milan, Amsterdam). I heard very similar feedback on EF yesterday in Milan. I will be passing this off to the EF team.
FYI: I'm a .NET Core team member.
Good to see these efforts, as some of the more popular open source e-commerce systems are showing their age (often aggravated by the underlying languages/ecosystems showing their age as well).
there are almost all open-source ecommerce platforms
Price, OldPrice, SpecialPrice, special price start and end dates properties are less than ideal for any non-trivial implementation. Prices should be driven by policies, not defined in the product itself (IMO.)