Activities of "heifengwll"

Or maybe like <system.web>

<globalization culture="auto" uiCulture="auto"/>
<compilation debug="true" targetFramework="4.5.2">
  <assemblies>
    <add assembly="System.Runtime, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
    <add assembly="System.Collections, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
  </assemblies>
</compilation>

<httpRuntime/>
<customErrors mode="Off"/>
<pages controlRenderingCompatibilityVersion="4.0"/>

</system.web>

<cite>ismcagdas: </cite> Which version of ABP do you use ? Probably some assemblies depend on different versions of System.Collections. Adding a assembly redirect to web.config might solve your problem.

Thank you, ~~, have been resolved In my Web.config, node <system.web> <assemblies>, adding <add assembly="System.Collections, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />

Abp.0.12.0.2

I'll try this method Thank you ~ ~

<cite>hikalkan: </cite> They are just used in AccountController for login, register etc. Current AccountController code is a mixed with web logic. We can stripe web logic and move login/register logic to an application service. If you say "why", I don't have a very good reason. Maybe this habit comes from standard MVC startup template :) Maybe I did not think that we can use the same register/login code from any other UI (like a mobile app). Anyway, we should think to move some of this code to app layer. Thanks for pointing this.

Thank you for your answer. I have some ideas.This project named Boilerplate, I think this should be a standard specification, provides accurate realization of the project. But because the AccountController dependency undermines the idea of DDD, would be confusing for beginners. Anyway, I tend to firm use the DTO, I suggest it is best to ABP + module add a zero project, as you recommended the use of DDD, but here would damage the ddd. Thanks again for answer.