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 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 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
I am working as a CRM developer for a large project which will be developed on a full time basis.
We have a number of online environments, however I was thinking it would be useful to have local dev environment as we have other developers as well working on this, what are the pros and cons of this?
I imagine in the long run it would be cheaper as its not using Azure.
Secondly if we did have local environments should we install a local on prem verion or a VM, would be interested to know what developers are doing out there and any best practices we can adopt here...
If you create an OnPrem development environment - one of the biggest pros for this would be that
- you have direct access to the database / crm platform traces and you can easily troubleshoot any issue - compared to CRM Online
cons (which i am afraid that are way bigger than the pros)
- Microsoft doesn't always release the CRM Online build to CRM OnPremise - so you wouldn't be able to develop in OnPrem the same features as you would in Online
- You might face challenges testing integrations with other products part of your Office365 / Azure tenant
- Microsoft might not provide you with a copy of your DB - I personally haven't went through this process for quite a while, however i heard that since CRM 9.0 the Online to OnPremise DB copy is no longer shared with the customer (yet i can't say for sure if this is 100% accurate)
In my opinion the above cons could prove to be show stoppers.
A year ago when i was developing for CRM Online (8.2) i had also a OnPrem copy - which i ended up mostly using to fix data related issues or debugging plug-ins by attaching VS directly to the process (is a lot easier than with the plugin profiler) - but most of the stuff i did on a sandbox environment
Hope this helps
You need to think that the solution you will be provide should be align with online instance only as you will be delivered solution into online version only end of the project .So for me proceed with online sandbox instance , you can access online instance from anywhere without any restriction and do your development activity.
I agree that there are few advantages using on-premise , compare to online, but using on-premise you have to maintain lot of things with the VM , AD and also require additional cost.
Business Applications communities