The views and opinions expressed in this blog are those solely of the author(s) and do not necessarily reflect Microsoft’s current policy, position, or branding. For official announcements and guidance on Dynamics 365 apps and services, please visit the Microsoft Dynamics 365 Blog.
Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
Yesterday I read Hosk’s article about why experince is important for CRM Developers. As a developer I keep on having to learn this mysterious way of CRM development, and I will share you my ideas about this topic and focusing on the code complexity:
As far as I am concerned the code complexity is anything you “introduce” into your code that makes it hard to read and follow. Just look the following topics you might look for code complexity:
Developers tend to write long methods. The longer your method is, the more work it will be to keep track of the overall point of the method! If you are write a long method, when you come back from coffee break, you will be confused.
What is ideal metric? How many lines of functional code per method? 1, 2, 3, …, 7? How many items can the human brain deal?
Most developers might think that only if/else statement are conditions. What else? So are for/next, do/while and switch statements too. I mention your code should be written so that you only have THREE condition per method. Switch statements might loose their context because of theirs complexity. I would have one method that handles this kind of statements and each case statements call a function.
Are you using Visual Studio? Great! There is a tool in Visual Studio that could help you determine how bad your methods are. This tool is under the Analyze menu options.
Business Applications communities