CRM solution strategy for automated builds

(0) Share

Report

Posted on by PragmaticDevs

239

Hello,

I have setup Azure devops for my dev environment. For now I just have 1 unmanaged solution and all components are part of the same solution.

Should I keep all my plugins in a different unmanaged solution and include this solution after my main solution , assuming plugins would have dependencies on fields/entities etc.

What else can I do to make solution structure modular?

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

Dynamics365 Rocker 7,755 on at

Like (0)

Report

RE: CRM solution strategy for automated builds

Technically If you have only one solution then it will also works fine.

But as a best practice, You will have three solutions:

1. Customization - This solution has all entities and fields including web resource

2. Workflows - This solution will have all workflows.

3. Plugins- This solution will have all plugins.

Was this reply helpful? Yes No
Suggested answer

PranavShroti 4,510 on at

Like (0)

Report

RE: CRM solution strategy for automated builds

Refer to this blow: Its little old however will give you indicative max size.

alagunellaikumar.blogspot.com/.../maximum-size-of-importing-solution-file.html

Another thing is to increase the time out for deployments. This can be done by calling MS support (in case of online)

Hope this helps.

Was this reply helpful? Yes No
PragmaticDevs 239 on at

Like (0)

Report

RE: CRM solution strategy for automated builds

When you size of solution should not be high? What's the recommended size of a solution?

Was this reply helpful? Yes No
Suggested answer

PranavShroti 4,510 on at

Like (0)

Report

RE: CRM solution strategy for automated builds

Well there is no straight forward answer to this: Microsoft recommends to have multiple solutions for different type of components to avoid timeouts etc. However in my personal experience I found that if your customization are not too high, and size of solution is relatively low than best is to have single solution containing all components.

Hope this helps.

Was this reply helpful? Yes No
gdas 50,091 Moderator on at

Like (0)

Report

RE: CRM solution strategy for automated builds

If you are not using OOB solution patching then I would recommend to have only single solution if you have dependent component . This is because having multiple solution when you move the solution into another environment as managed you might face issue in future when you want to delete any component from one solution. This is because same component exists in two solution and you can not delete component from one solution .

Was this reply helpful? Yes No