Managed Solution Stacking Fails: When One Managed Solution Relies on Another - PART 2

Visit Website View Our Posts

Ok . . . flash forward to continued development of Solution B on top of Solution A. Today I rebuilt my environment with Solution A and Solution B as Unmanaged. When I exported Solution B as a managed solution, and imported it into a live environment, I got the same mystical error as before. I rechecked the security stuff, and it was all-OK. Working on a theory alone, I re-imported Solution A as managed into my development environment, and then re-exported Solution B. Voila! Problem goes away.

So in addition to security roles, make sure your development environment is always working with Managed Solution A as its base.

Click here to read Part 1.

Written By Mark Rockwell, President of Rockton Software, Small Business Accounting Inside Microsoft Dynamics CRM. 

Show Buttons
Hide Buttons