Microsoft Dynamics CRM (Archived)

Brief knowledge about Early Binding vs Late Binding in MS CRM

(0) Share

Report

Posted on by rath.amit38@gmail.com

Early Binding vs Late Binding in MS CRM.

What are the uses, why and how?

If we have 500 entities in the organisation, which approach is better and why?

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (3)

Suggested answer

Adrian Begovich 1,027 Moderator on at

Like (0)

Report
Hi Amit Kumar Rath,

It comes down to personal preference. I prefer early bound development to late bound development as it is helpful to have type references checked at compile time. I develop late bound code in smaller projects where generating early-bound entity classes is overkill and when the existing code base is full of late bound code.

Read these articles for more on this topic.

Choose your development style for Dynamics 365

Use the early bound entity classes in code

Use the late bound entity class in code

Was this reply helpful? Yes No
PhuocLV 347 on at

Like (0)

Report

You can use PL.DynamicsCrm.DevKit ([View:https://github.com/phuocle/Dynamics-Crm-DevKit]) to generator Late Bound class

Was this reply helpful? Yes No
Verified answer

Alex Fun Wei Jie 33,628 on at

Like (0)

Report

Hi,

you can take a look the below article on early VS late binding.

community.dynamics.com/.../microsoft-dynamics-crm-early-vs-late-binding-advantage-and-disadvantage

develop1.net/.../Early-Binding-vs-Late-Binding-Performance-Revisited

From my own opinion , there is no winner. You have to select the most suitable solution for yourself.

Was this reply helpful? Yes No
Verified answer

Arun Vinoth 11,615 Moderator on at

Like (1)

Report

Some fabulous data points can be found in this SO thread.

[View:https://stackoverflow.com/q/15038699/7920473]

Was this reply helpful? Yes No
Verified answer

gdas 50,091 Moderator on at

Like (1)

Report

Hi Amit,

In simple words using early bound you can get all entities information( entity, attributes name) at the time of writing server side code so there is less chances to having typo error in compile time , You will get the intellisence support in Visual Studio. Secondly yo may face difficulties using early bound classes when you have a team with more people and everyone changing the datamodel in this scenario, each time you need to create early bound classes for any data model changes. Sometimes early bound is good to have to use LINQ directly over the entities.

Example of Early bound-2

Account acc= new Account();

Late bound concept is light weight you don't need create additional classes for that, you just simply define your entity,attributes where ever you need. In this case you need to write little more lines of code to declare them and you need to keep everytime names of entity and attributes to avoid typo while writing code. Late bound is always good as there is no dependency of classes and performance wise it's faster then early bound. Although it was prooved that for long running and large projects performance become same of those. I would prefer late bound if you have more people working in same project and data model changing continuously.

Example late bound-

Entity acc = new Entity("account");

Was this reply helpful? Yes No