Activities of "noah"

This has not occurred after starting a new project from template. Perhaps it was something random with the previous project setup? Thanks for following up.

Thanks. I'm going to try the route of copy/rename the Web project. It took a couple hours to fix up naming conflicts etc, but seems to run now.

Thanks. This is a web project to run as a separate web app but access the main database -- architecture is two websites, one as web project from template, and another running Hangfire as a scheduler. I can try copying the web project, although this seems like it could carry a lot of overhead just to get a simple web project working that doesn't require all the other infrastructure.

A simpler question: what needs to be done to ensure an entity can be eager loaded from a new project?

The question here actually might be how to handle dependency injection for a project that is not based on the ABP template. I've added a standard VS web project alongside the ABP projects in my solution. I've attempted to provide the IOC behavior this way:

protected void Application_Start()
        {
            AreaRegistration.RegisterAllAreas();
            GlobalConfiguration.Configure(WebApiConfig.Register);
            FilterConfig.RegisterGlobalFilters(GlobalFilters.Filters);
            RouteConfig.RegisterRoutes(RouteTable.Routes);
            BundleConfig.RegisterBundles(BundleTable.Bundles);

            AbpBootstrapper bootstrapper = new AbpBootstrapper();
            bootstrapper.Initialize();
            bootstrapper.IocManager.RegisterIfNot<IAssemblyFinder, CurrentDomainAssemblyFinder>();
        }

Is there a better way to ensure the functionality in other projects is resolved correctly especially for Entity Framework use?

Thanks. My application version shows as v1.7.1.1

Also noticed my ABP modules were 0.7.7.2, so I upgraded to 0.7.8. Issue still exists.

The GetRolesForEdit call seems to happen fine, returning the object with array of permissions. Nothing in the server log.

Here's what Chrome shows in console:

<a class="postlink" href="http://screencast.com/t/4O6yIbGDegk">http://screencast.com/t/4O6yIbGDegk</a> <a class="postlink" href="http://screencast.com/t/j0aDEU6Ua">http://screencast.com/t/j0aDEU6Ua</a>

(Also confirmed in IE 11)

After some further testing I notice that user permission inheritance from role does seem to work for users I create but is broken for the built-in "admin" account where I first noticed the unexpected behavior.

Thanks. So you would say that if using EF, only use "virtual" on navigation properties and not for primitive types?

Thanks. Perhaps then the question should be: when defining entity classes under ABP, is there a case where a member should not be marked as virtual?