Activities of "hikalkan"

Hi,

Thanks. I hope you make use of it.

Module-zero is almost production-ready. Implemented parts are working. We're using it in two production products in my company. I'm actively developing it. But some parts of it may change, and is not documented yet. Documentation will be written in a very near future. If you can understand it from sample project (<a class="postlink" href="https://github.com/aspnetboilerplate/module-zero/tree/master/sample">https://github.com/aspnetboilerplate/mo ... ter/sample</a>) and discussions on forum and github, you can use it now.

Have a nide day.

Hi,

Startup template is just a minimal template, you should change it upon yor needs. See header.js and header.cshtml in App\Main\views\layout folder of SPA (or Views\Layout_TopMenu.cshtml in MPA). You can change it freely.

For your other questions:

• ABP uses EntityFramework or NHibernate. You can search web to find articles on working oracle with EF 6. This is not directly related to ABP. Probably you will change connection string and add come dlls to your project.
• Create a custom repository method (<a class="postlink" href="http://www.aspnetboilerplate.com/Pages/Documents/EntityFramework-Integration#DocCustomRepositoryMethods">http://www.aspnetboilerplate.com/Pages/ ... oryMethods</a>) and call your stored procedure using Context.Database. You can find many documents on web about that.

Have a nice day.

Yeah, you found it :) Creating a well structured, domain-driven and layered application is not easy. ABP tries to make it easier and straightforward. You can have different models for registration. Simple one is to create users by an admin. Other one is to allow users register themselves using email activation. This is completely upon your needs.

Hi,

You can extend and use AbpUserManager as shown in module-zero sample. It has all methods to manage (create, update, delete, list, add to roles...) users. You can also use RoleManager. Even you can use repositories if you really need.

I agree that. I'll try to prepare more rich DDD examples in the future.

Yes, it's like that.

What do you mean to deploy entire project? There is only single application (web app) in the solution?

Hi,

Some questions:

• Did you started from template generated by aspnetboilerplate.com?
• Did you add your entity to your DbContext?
• Did you derive UpAttach from Entity?

Hi,

Thanks a lot.

Entities and DbContext: You can generate code-first entities using Visual Studio from an existing database (search web for it). Then you can modify them to derive from Entity class. Repositories: No need to create repositories since you can inject and use IRepository<TEntity> without creating a repository class (see <a class="postlink" href="http://www.aspnetboilerplate.com/Pages/Documents/EntityFramework-Integration#DocImplRepositories">http://www.aspnetboilerplate.com/Pages/ ... positories</a>).

ASP.NET Boilerplate is first designed for new application with empty databases rather than migrating existing databases or applications. ASP.NET Boilerplate is not a code generation tool. Also, in DDD, you should think carefully on Entities, DTOs and application layer. They are not things can be automatically generated (At least I think like that). Creating a repository, a DTO, CRUD application service and an entity for a database table is not DDD. Even it's possible, you will change a lot after creating. Yes, maybe we can create a tool to firstly creating these classes to help us. It may be a starting point. But there is no such a tool in this moment If you build such a tool, please share with us since a few people also asked this question before :).

Have a nice day.

Hi,

I published v0.5.8.1 to fix it. I just was not register email sender. Now, just inject IEmailSender or ISmtpEmailSender and use it. It will work if settings are correct.