Answered by:
[CRM 2013] Multiple front-end deployment for devs

Question
-
Hi
I have been tasked with creating a dev environment for CRM 2013 development. The problem we face now is that we have one dev server and when someone is debugging a plugin (which happens quite a lot) it basically prevents anyone else from using the server.
I know that you can install CRM on multiple servers with multiple front-ends all connecting to a single database. Will such an installation be feasible for my needs, ie. if I create multiple virtual machines with only front-ends installed will it be possible to use those VM to install plugins and debug them?
Alternatly would it be possible to set up CRM to use multiple ports for a single organization, spawning multiple w3wp processes, so a single dev won't block the entire server?
I know I could give each dev an independent CRM install on a single VM to play with and then get all the finished stuff onto a single server after it has been tested, but we have some complicated test cases and we'd rather avoid having devs fill multiple large forms on their VMs when our test stuff has already done that.
Or maby there is a better way?
Regards
Grzegorz ZychTuesday, January 7, 2014 4:01 PM
Answers
-
Hi,
MSFT provided guidance in ALM for Microsoft Dynamics CRM 2011: CRM Solution Lifecycle Management (Still relevant for CRM 2013). Look under Working with Developer Environments.
Ronald
- Marked as answer by Grzegorz Zych Monday, January 13, 2014 11:59 AM
Tuesday, January 7, 2014 4:26 PM -
You can also still use the plugin profiler / plugin registration tool to debug plugins in CRM 2013. You just have to go into the plugin registration tool and set the profiler assembly from 'sandbox' to 'None' Obviously that won't help much if you're trying to use it on CRM Online. http://community.dynamics.com/crm/f/117/t/115368.aspx (post specifically discussing making it work with 2013)
http://support.microsoft.com/kb/2778280/en-us is the overview of the approach
- Marked as answer by Grzegorz Zych Monday, January 13, 2014 11:59 AM
Tuesday, January 7, 2014 7:34 PM
All replies
-
Hi,
MSFT provided guidance in ALM for Microsoft Dynamics CRM 2011: CRM Solution Lifecycle Management (Still relevant for CRM 2013). Look under Working with Developer Environments.
Ronald
- Marked as answer by Grzegorz Zych Monday, January 13, 2014 11:59 AM
Tuesday, January 7, 2014 4:26 PM -
You can also still use the plugin profiler / plugin registration tool to debug plugins in CRM 2013. You just have to go into the plugin registration tool and set the profiler assembly from 'sandbox' to 'None' Obviously that won't help much if you're trying to use it on CRM Online. http://community.dynamics.com/crm/f/117/t/115368.aspx (post specifically discussing making it work with 2013)
http://support.microsoft.com/kb/2778280/en-us is the overview of the approach
- Marked as answer by Grzegorz Zych Monday, January 13, 2014 11:59 AM
Tuesday, January 7, 2014 7:34 PM -
Thanks for your replies, I'll look into those.Monday, January 13, 2014 11:59 AM