I have been trying really hard to keep my customizations separate from the AC9 code. I'm now trying to create a custom Category Grid view that includes Products, Categories, Links, and Webpages, sorted by the OrderBy value in ac_CatalogNodes. I was going to register it as a Widget in my plugin, but tons of the Models and Helper classes (PageVisitHelper for example) reside in the AbleCommerce web project. One of the things that drove me nuts about AC7 was circular relations causing issues with building the application. Is it safe to reference the AbleCommerce web project from custom plug-ins, or will it create the same circular reference issues we experienced in the past?

Well, I tried adding the reference. There were library mismatches that had to be resolved by adding binding redirects in the app.config for the plugin. Not sure why since the NuGet package versions are the same for each project. It also broke my plug-in Intellisense again. I'm about to chuck plug-ins out the window and start coding in the main project.

I thought NuGet was supposed to help remove us from DLL hell?! :P

@judy, that is pretty much where we are at. We thought we would try to keep things as separate as possible to assist with future upgrades and potentially spin off the inventory and pick/pack as a 3rd party plug-in. We really liked how the plugin was integrated into the nav and we were able to wire up configuration screen and routes. However, the constant Intellisense issues we've encountered and library version mismatches are making it more of a headache than it is worth. Guess it is time to purchase the full source code version and get rolling :)