Build fails and old nugets, many dependency issues about dwkit

[papyr]

[optimajet]

Dear Papyr.

We don't move to .NET Core 2.1. The task has been planned the next release.
Are messages from your screenshot warnings or errors?

[papyr]

They were errors, but I fixed and manged to build. They were not major, but took a little time. This is great improvement over the last one. This version seems to understand user needs much better.

I liked how grouped functionality, with roles and users, good idea! But a side note, some of the ideas behind could use some polish.

The idea for the forms management and form builder for workflow review, was also very nice, but creating a new one did not save/show up.

For e.g. if the power user wants to create a form, then put a workflow behind it, and publish it, he has to jump around in the navigation. 1) power user needs a checklist/concepts or something to know what all has to be done to publish that form with the workflow. 2) developer needs to know how to implement items so the show up as the tasks for the power user, this also needs a checklist. Lastly, when new forms are created are they blobs or do they get a new entity/vm/model/table?

I am curious why did you choose react over ASP core/jquery. There is a much bigger audience/dev/customer base in the latter.

[optimajet]

Can you share your experience? How did you fix these errors? Other of our customers didn't have them.

but creating a new one did not save/show up

What does it mean? Do you suggest to add todo list in the admin panel?

I am curious why did you choose react over ASP core/jquery. There is a much bigger audience/dev/customer base in the latter.

The main reason is react/redux is the most modern technology stack for web development.
We suppose many customers will migrate to react technology when they start new projects.

[papyr]

Sorry I was busy.

1. The issue was the BCL classes in core, with core 2.1.3 its fixed, there is something called project rebindings or something VS did this automatically for me.
2. I was trying to create a new form using the form builder and put into a workflow to test it. I am uncertain if its my mistake, but the forms I created did not show up. it would be helpful to the user, if he has a checklist on what is pending to do, after he created a new form. In a way, you would use your own engine to drive his process. Just make sure he doesnt confuse it with his own processes/schemas he created
3. If you look just at github or dice etc.. there are more jobs in asp mvc core than react/redux, i.e .more dev/companies. Just a recommendation thats all.

thanks I will close this

[optimajet]

Yes, we think about a wizard for doing main operations in DWKIT. This feature is in our backlog.
React/Redux is the better technology for creating rich web-apps. We did a big work for isolating users from complicated things. Basically, developers won't face react/redux if they don't drop into core-modules or source codes.

Coming soon we publish some video tutorials for each feature.

Anyway, thanks for your feedback. I hope you investigate the product successfully. If you decide to use DWKit in a commercial project, make sure our support service will help you.

[papyr]

Yes absolutely, I think there is a need, but its also big concern to recommend to company, because I will be on the hook to deliver and cannot fail.
So for projects that are already on ASP core with JS/TS/Jquery, I have questions on integration.
Understanding the concepts, for e.g. applying your domain concepts, and then using the corresponding domains objects to do our specific internal work is also needed. Currently I have developed my own simple UI on stateless which is working so far. But for more flexibility and resuability I am considering your app. I honestly dont know the answers to all. But if you build out a simple good easy to understand sample on focus on that, you will get more traction. The other thing is the pricing is also not reflective of the ease of developer use, at least from my mgr. perspective. Just sharing feedback!