Quote from keith on August 15, 2018, 8:03 am

Graeme, what is your specific issue. I know it is still being developed but support is really not there.  I needed to update my NodeJS to the latest version and that fixed my primary issue. I am also looking for people to help add features and share a private Repository if they are interested and have a license.

Quote from Graeme Atkinson on August 15, 2018, 10:36 pm

Hello Keith, thanks for your reply.

At the moment I find that the logging and authorization functions of the latest release are not working (.NET core 2.0 release did not have these issues). I have returned to the .NET core 2.0 release for now, in the hope that these issues will be picked up and fixed before I migrate. However this release also has problems with the update-database commands (I find that any command issued hangs - a problem that, ironically, is not present in the .NET core 2.1 release).

We pick up projects like this to avoid having to deal with core wiring - so we can focus on the application we want to build.

What was the issue that you had (requiring the NodeJS update)?

Great idea to have somewhere to add additional features.

Quote from Eben Monney on January 9, 2019, 5:46 pm

@graeme_atkinson sorry you've had issues with the updates and with support.
We'll do our best to respond to all new posts within a day of posting so feel free to posts your issues here. You can also send them to support@ebenmonney.com and I'll have the opportunity to take a look at it.

For situations where something doesn't work well, you can post your logs, snippets, etc on this forum and we'll all help to fix it. You can also use the support email to send us a repo to work through. Thanks for your feedback Atkinson.

@keith what features would you want to see in  future updates? We can discuss them and see how they can fit well into a base template and reduce initial wiring.