Hi. I`m now in the process of integrating nopCommerce 2.40 with umbraco 5. Since both of them use MVC 3, it should not be a huge problem to combine them, however I got stuck at a point when each of applications use their own global.aspx.cs class to initialize context, so I decided to merge them in one and see if it`ll allow me to freely navigate nopCommerce and umbraco pages in one app. I frequently getting such errors: "The requested service 'Nop.Services.Common.IMobileDeviceHelper' has not been registered" when I try to initialize nopCommerce context and then umbraco`s in Application_Start method. Can you provide mw with some information if I`m working in correct way or I should do something more in addition to combine both frontends?

It's hard to determine where the issue. Could you share your solution?

There are too many code to just show it here, so I packed it and posted here: https://skydrive.live.com/redir.aspx?cid=1416dcb161315f5e&resid=1416DCB161315F5E!158&parid=1416DCB161315F5E!126

Description: I`ve made root web.config merge and partly Views/web.config merge, but still cannot get rid of problem with different namespaces of "pages" section in it.

There are four folders. Problem is in config files in "_exception" folders. It`s when I try to initialize both contexts of Umbraco and nopCommerce. In first case nopCommerce context goes first, in second - umbraco. So in case of when umbraco goes second, application uses default System.Web.Mvc.MvcHandler to handle pages thus making nopCommerce directory unavailable for browsing. And default view causes "'Nop.Services.Common.IMobileDeviceHelper' has not been registered" exception, like umbraco clears registered types before loading and vice versa if umbraco goes first.

The question is, how can context initialization of nopCommerce affect Umbraco`s? I know, this can be not the correct place to ask such questions, but maybe you already made some research and have some advice for me? And yes, I could`ve used russian, but in case this post maybe useful for someone, I won`t :)

Hi guys. Any suggestions? Why could ITypefinder not registered? (ContainerConfigurer.cs line: 32)  Or IMobileDeviceHelper at ContainerManager.cs Line: 108?

Hi

I started creating a package some time ago (umb 4.0 i think and umbraco 1.8). Unfortunately, and this isn't a criticism of nop as we use it for all of our ecommerce sites, the architecture is tied very tightly to EF. I found i couldn't use the xxService of the nop framework and basically had to create by own dal...suffice to say i never finished. Not sure if the umbraco 'hive' will help. i know this probably is not helping however I wasted a lot of time trying to shoe-horn nop into umbraco when it appears nop was not designed as a 'component' but rather a standalone application.

I`ve cleared the problem, but cannot get over it. The problem is in IoC containers LifetimeScope`s. Simply, once Umbraco creates its own registrations and builds the container it starts its own LifetimeScope. And after that nopcommerce`s container neither is not registering its dependencies in that scope nor can not create new one. I`ve tried tagging, but Scope() method always returns me the scope that was created first and vice versa if I change the initialization to Nop -> Umb. Any way around this?