With Dynamics 365 for Finance and Operations(D365FO)/Dynamics 365 Unified Operations Visual Studio 2015 (Premium, Professional or Enterprise Edition) is the primary integrated development environment (IDE), and the MorphX studio has been deprecated.
Organizing Development Objects in Visual Studio:
With Visual Studio being the primary IDE for development, there is a lot of flexibility that’s being offered with regards to organizing the D365FO development objects.
The following are the list of take-away points when it comes to organizing D365FO development objects in Visual Studio projects:
1. Build a single project and add all the development objects into the same Visual Studio project. This is as depicted in the figure below (Fig 1 – Organizing development objects in a Dynamics 365 for Finance and Operations Visual Studio project).
Fig 1 – Organizing Development Objects In A Dynamics 365 for Finance and Operations Visual Studio Project
For example, if you are working on an Agile project, then you can organize the objects in Visual studio in a single project that is demo development.
Use a format:
2. Do not create multiple projects for each new task in the project. This makes it easy to do the build from the development environment onto the test/sandbox environment. Creating multiple projects for each task adds complexity to deployments from a development machine to a test machine.
3. Create objects that will be re-used like Data Types, Base Enums outside of the activity/task specific folder. For example, Create the re-useable objects outside the repository:
Manage all the D365FO implementation activities inside a single Visual Studio project.