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
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
One thing that has always bothered me is how difficult it is to manage data structure contracts (read: types), throughout a large amount of code. To achieve application-level fidelity, you need a specialized library, that calls for specialized object factories—breaking away from all native syntax, and making useful documentation generation and structure a miserable chore. At least, that’s what it’s been for me.
The question, for me, has always been about bridging the gap: how do I posit stronger typing into my development, if not the language? At first, I was drunk with prototypes and closures, and tried to produce my own typing/inheritance model. Its quirks and desperate lack of syntactic approximation to stronger-typed languages left me to abandon it for something else.
I use these two together often, coupled with internal definition files for jQuery, JSON, and other common libraries. The stock definition files have done a great job, so these are the only two new ones that I’ve needed, so far. (Though, now that I’m getting into KendoUI, I’d love to see definition files for it.)
So, if you want to start learning TypeScript, the best way to start is to do the following:
I find the following tweaks to Visual Studio’s options handy:
Then, you can use reference tags in your own TypeScript files, to include the definition files from above and start enjoying TypeScript in CRM 2011 development:
Business Applications communities