thanks joe,

haha... yes of course I realise the difference between deployment code and source code, just thought using the web installer might setup my database for me and save some time. I found all the config files in the setup folder though, just thought there might be some .sql versions, something a little more hands on for developers to play with. Having said that I can just change the extensions.

I am seriously modifying the code to use EF with the stored procedures and ditching all the other database options. I didn't want to have to run the setup bit. I will probably ditch the UI bits too and replace with MVC, but for now I just want to get the db objects loaded.

Thanks anyway

no... understood and wouldn't expect any support with my dev of course. I appreciate your rationale for advising not doing so, but forking it is very much on my mind. If any good comes of it I'll give you the source as a possible start point for next generation mojo. Got this skin idea of using bootstrap as the layout guide, all ajax through web api and routing through MVC.

I was thinking of using nop as my start point but can't abide di and ioc... just seems wrong. mojo seems fairly well set out and easy to follow and has all the e-commerce assemblies I need.

Thanks

quite right...that's exactly what I did. I just ran the setup in iis, separately from vs. the db is fully loaded now.

thanks for that

Stu