Hi,

We use Mono.Data.Sqlite which we compiled against the version of sqlite included in mojoPortal. To use a newer version of Sqlite I will have to get the mono source code again and compile it against the newer version. It is not a high priority, if you are experiencing a bug in mojoPortal due to the version of sqlite let me know.

Features are in separate projects for several reasons, once upon a time it was all in the mojoPortal.Web projects but was moved into separate set of projects a few years ago.

The reasons are because some developers wan to use only the core of mojoportal plus their custom features without any of the features from mojoPortal.Features. If you have a clean copy of the source code you can use the mojoportal-core.sln and it will only have the core features. The trick is to never build the mojoportal.sln because that would run the post build events and deploy the features. By not doing that you can have a smaller lighter mojoportal package to bundle with custom features. While most people use mojoPortal as a CMS and do want all the features, others use mojoportal as a web app framework for other purposes. For example I know of one developer who built features for factory automation and he doesn't need or want any of the mojoPortal.Features stuff in his deployment.

Also having the features in separate projects illustrates how developers should organize their own custom features into their own projects to keep them separate from mojoportal code.

Hope it helps,

Joe