How to do it...

1. Under the Dynamics 365 menu, choose Model Management | Create model….
2. The model name is named as it would be in AX 2012, and should be named like a new type, such as <prefix><ShortName>.
3. Complete the first page as follows:

• Model name: In our case, our company is called Contoso, so our prefix will be Con, and we are writing a vehicle management solution. Therefore, we have named it ConVehicleManagement. You should use your own prefix and prefixes, as well as a unique name, which is explained further in the There's more... section.
• Model publisher: Your organization's name.
• Layer: ISV or vertical solution. Here, choose ISV. For partner projects choose VAR. Customers can use CUS or USR.
• Version: Leave as 1.0.0.0.
• Model description: A full description of the model for other developers to read.
• Model display name: This should be something like Contoso – vehicle management in our case.

The custom layers were traditionally used to segregate a customer's global solution layer from the requirements of each country's implementation. The layer technology is processed very differently for the extension projects and has lost some significance in this release.

4. Press Next.
5. On the Select package page, choose Create new package.

If you choose Select existing package, it will mean that your model will be placed under the package and is intended to over-layer the elements in that package. You cannot over-layer elements in extension projects, but unless we absolutely must over-layer, always choose Create new package.

6. Press Next.
7. We are now offered a list of packages that we can reference, listed as package names and the models that each package contains. Leave ApplicationPlatform checked. Additionally, check ApplicationFoundation, ApplicationCommon, and ApplicationSuite and then press Next.

Most of the elements in SCM are in ApplicationSuite; so, unless our package doesn't need any standard type, this will always be selected. The others would be selected based on the elements we know we will use. We can add more package references later, but if we know which elements we will use, it saves us some time.

8. The Create new project and Make this my default model for new projects checkboxes should both be checked.
9. Press Finish.
10. This opens the New Project dialog. The project name is usually the same as the package and model name. Now, enter the package name in the Name field.
11. The Location field must be changed; it will be created in the default project folder. Here, we linked C:\Trunk\Dev to source control. The project must be created under this folder. So, in my case, Location must be C:\Trunk\Dev\Projects.
12. The Solution name field should be left as the project name.

13. Ensure that both Create directory for the solution and Add to source control are checked.
14. Press OK.