MrDave's (David Yack) CRM Blog!

In case you missed it on the CRM team blog (post here) there's a new SDK that just got published at the end of the month.  (I've been out of the country so just now catching up on what I've been missing! )  There's a number of new things in the SDK including they now added a bunch of VB.NET samples  - I'd love to know how important that is to you,  drop me an e-mail  and let me know!

One of the things that I recommend looking at is the readme that comes in the root folder of the SDK - Scroll past the Contents of the SDK and you will find the "Known Issues" section.  Keeping this list in the back of your head can save you a few hours of research when you hit one of the problems.  The following are a few that I have hit and I would recommend keeping fresh in your mind!

- 64-bit version of IDCRL assembly is missing - this effects if you are trying to connect to CRM Online from a 64 bit server - workaround now that I have used is just forcing it to run 32 bit - that seems to work fine.

- New Role created from web client does not contain many necessary privileges -  This one will get you scratching your head for a while - the easiest thing to do for now is copy an existing role and then dumb it down as needed.  The readme also suggests another work around of calling the AddPrilvledgeRole to add the missing ones. I'd personally recommend just copying an existing role for now.

- Web Exception (Http 401 ) thrown in plug-in - Oh this is a fun one - if you have a space in your org name you can hit this one - SDK has two work around's -  change the org name to not have spaces or don't use the CreateCrmService - I typically prefer the change the org name approach but I keep hoping a hotfix will get created for this one.

There are a number of other ones on the list so you should take a look each time the SDK is published it will definitely save you a few hours in return!