I updated my DLL today and have encountered a couple problems.  Code that has not changed since the begining is now throwing errors.  The code below is for sending a message.

Dim tempto, tempmsg As String

'Send the message...

MsgBox("Send:" & ex.Message)

End Try

The funny thing is the message actually sends but then throws a NullReferenceException.  As you can see the very last line sends so there is nothign else that could through the error.  On reviewing the SMS Folders the sent messages are not being moved to the SentItems Folder.  That must be where the error is occuring.  Also the the Folder list problem is still occuring.  The messages appear out of order.  The messages are being moved to the folder but they are added at position 1 (2nd Message) instead of position 0 (Top Message).

I'm looking into this and will post back with progress early next week.

Peter

It appears to be specific to the SmsMessage(to, body) constructor. A workaround in the short term is to set the From recipient manually before calling send e.g.

 SmsMessage sm = new SmsMessage("1234", "test");

sm.From = new Recipient(os.SmsAccount.PhoneNumber);

sm.Send;

Is there an ETA on the next release date?   The work around doesn't always function in the desired manor on all targeted devices.

The issue with the workaround is that some devices don't expose the PhoneNumber. You can set this to an alternative dummy value if the SmsAccount.PhoneNumber property is empty. At the moment I don't have an ETA for the next version, I won't have a clearer plan for the next version until after TechEd next month.

Peter

I can confirm I'm now getting this issue after updating the dlls from 3.1 to 3.2.1.

Code is: 

SmsMessage smsMessage = new SmsMessage(mobileNumber, message);
smsMessage.Send();

Now throws a null reference on the From. OutlookSession.SmsAccount.Phonenumber is blank on the device I'm using so I can't use the new Recipient workaround.

Having to set the phone number of the device for each of the 40 devices (in the config I'd think) that we're rolling out to is a pretty prohibitive installation overhead.

Any chance you know what was changed between versions that could have caused this, to fix it?

This issue is resolved in 3.3. I'm just finialising the installer and will be uploading it later today. The device will populate the phone number itself on sent messages, the SmsAccount.PhoneNumber property is no longer used but is still available if you need it for something else.

Peter

Awesome stuff, I'll keep an eye out for that. Thanks.

Version 3.3 is now available.

Peter