Using the new 2013 Developer Toolkit to deploy code to CRM 2013 Online
CRM 2013 SDK is out and I comes with the new developer toolkit for Visual Studio 2012. If you just want to have a play and still donโt have CRM 2013 on premises, here is how you can start to play with some 2013 new features:
- Subscribe to CRM online
- Download CRM 2013 SDK
- Unpack the SDK file and go to SDK > Tools > DeveloperToolkit
- Install the developertoolkit and open Visual Studio 2012
- Go to File > New > Project. You will see a new set of templates under Dynamics CRM
- Select โNew Visual Studio Solution Template for Dynamics CRM 2013โ.
- That action will generate a CRM solution with the most common CRM components and prompt you to enter credentials. Here is where it gets a little tricky. For CRM Online, you will enter โdisco.crm5.dynamics.comโ regardless of your url.
- Select HTTPS and click โConnectโ
- Enter your 360 user login ( It should look like loginid@yourcrmsite.onmicrosoft.com)
- Click Log on
- At this point if you login you should be able to select your organisation and solution
- Click OK.
Once your login succeed, you should see this CRM Object Explorer:
If you expand a branch like โEntitiesโ, you should see all the entities available on your Crm.
Before you can use the Deploy command, remember you need to do a few tweaks. First, Create a Strong Name Key for Any Plugin or Workflow you create. (Please bear in mind that once you decide to use this for real development, you may want to add an appropriated name to your components before you deploy. Remember also that itโs not a good idea to use the Deploy feature of the developer toolkit to release code on later stages like UAT and Production)
You will also need to change the โRegisterFile.crmregisterโ Isolation level of any component that is set to anything but โsandboxโ. Remember even though workflows are now allowed as long as deployed on the sandbox.
If you build and Right Click CRMPackage, you should have a successful deploy
This was originally posted here.

Like
Report





*This post is locked for comments