Earlier this year

• Jun 24, 2009

  issue 9 (Twitter message ID's now exceed an int32) reported by rbanks54   -   What steps will reproduce the problem? 1. Try posting a status update 2. The returned status ID is longer than an int32 so you get an exception In Status.cs you need to switch the int?'s to long?'s

  What steps will reproduce the problem? 1. Try posting a status update 2. The returned status ID is longer than an int32 so you get an exception In Status.cs you need to switch the int?'s to long?'s
• Mar 01, 2009

  issue 8 (DirectMessageClient and reply to twett) commented on by tvoodoo   -   Also how do you follow a user for twitts (add to friend)

  Also how do you follow a user for twitts (add to friend)
• Mar 01, 2009

  issue 8 (DirectMessageClient and reply to twett) reported by tvoodoo   -   What steps will reproduce the problem? public DirectMessageClient D; . . D = new DirectMessageClient(UserName,Password); DirectMessage[] Msg = D.GetList(); And i get an exception on the DirectMessage[] Msg = D.GetList() : System.Runtime.Serialization.SerializationException: There was an error checking start element of object of type Amplify.Twitter.DirectMessage[]. CData elements not valid at top level of an XML document. Line 1, position 3. ---> System.Xml.XmlException: CData elements not valid at top level of an XML document. Line 1, position 3. at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke at Amplify.Twitter.DirectMessageClient.GetList at Amplify.Twitter.DirectMessageClient.GetList And my second problem is how do you reply to a twett. For example i received a twett from xxx and i want to reply so that the reply will show on his page. Hoping for a fast reply. Thanks in advance

  What steps will reproduce the problem? public DirectMessageClient D; . . D = new DirectMessageClient(UserName,Password); DirectMessage[] Msg = D.GetList(); And i get an exception on the DirectMessage[] Msg = D.GetList() : System.Runtime.Serialization.SerializationException: There was an error checking start element of object of type Amplify.Twitter.DirectMessage[]. CData elements not valid at top level of an XML document. Line 1, position 3. ---> System.Xml.XmlException: CData elements not valid at top level of an XML document. Line 1, position 3. at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke at Amplify.Twitter.DirectMessageClient.GetList at Amplify.Twitter.DirectMessageClient.GetList And my second problem is how do you reply to a twett. For example i received a twett from xxx and i want to reply so that the reply will show on his page. Hoping for a fast reply. Thanks in advance
• Feb 06, 2009

  issue 7 (DateTime.Parse fails on non-US locales) reported by fealebenpae   -   What steps will reproduce the problem? 1. Set the system locale to any other except en. 2. Call StatusClient.Create 3. DateTime.Parse will raise an exception about the string passed not being a valid DateTime. This happens, because the DateTime pattern provided is specific to an en locale. Changing CreatedAtString._setvalue in StatusClient to: this.createdAt = DateTime.ParseExact(value, TimeFormat, CultureInfo.CreateSpecificCulture("en- US"), DateTimeStyles.AllowWhiteSpaces); fixed it for me.

  What steps will reproduce the problem? 1. Set the system locale to any other except en. 2. Call StatusClient.Create 3. DateTime.Parse will raise an exception about the string passed not being a valid DateTime. This happens, because the DateTime pattern provided is specific to an en locale. Changing CreatedAtString._setvalue in StatusClient to: this.createdAt = DateTime.ParseExact(value, TimeFormat, CultureInfo.CreateSpecificCulture("en- US"), DateTimeStyles.AllowWhiteSpaces); fixed it for me.
• Jan 26, 2009

  issue 5 (Can not recieve direct messages.) commented on by jguadagno   -   Mike What else did you fix with the library? Joe

  Mike What else did you fix with the library? Joe

Older

• Dec 28, 2008

  issue 5 (Can not recieve direct messages.) commented on by mikelor   -   Hi, My address is mikelor followed by gmail dot com. -=mike

  Hi, My address is mikelor followed by gmail dot com. -=mike
• Dec 26, 2008

  issue 5 (Can not recieve direct messages.) commented on by mhern...@amptools.net   -   mikelor if you send me your e-mail, i'll add you to the dev list so that upload the patches.

  mikelor if you send me your e-mail, i'll add you to the dev list so that upload the patches.
• Dec 26, 2008

  issue 5 (Can not recieve direct messages.) commented on by mikelor   -   Hi, I ran into this problem as well. The solution to this is to modify the OperationContract for GetList(). According to the REST API documentation http://apiwiki.twitter.com/REST+API+Documentation#directmessages, these methods are GET's. Sooo... here's what you need to do to fix it. In IDirectMessageClient.cs modify line 33 to be a "WebGet" rather than "WebInvoke", this is also true for line 50 in the definition of GetSentList(). I have modified these in my code locally, plus a lot of other fixes as well. I'd be happy to upload them. Let me know.

  Hi, I ran into this problem as well. The solution to this is to modify the OperationContract for GetList(). According to the REST API documentation http://apiwiki.twitter.com/REST+API+Documentation#directmessages, these methods are GET's. Sooo... here's what you need to do to fix it. In IDirectMessageClient.cs modify line 33 to be a "WebGet" rather than "WebInvoke", this is also true for line 50 in the definition of GetSentList(). I have modified these in my code locally, plus a lot of other fixes as well. I'd be happy to upload them. Let me know.
• Dec 24, 2008

  issue 5 (Can not recieve direct messages.) changed by mhern...@opensourceconnections.com   -   i'll take a look at this and see if i can reproduce it.

  Status: Accepted

  Owner: mhern...@opensourceconnections.com

  Cc: mhern...@opensourceconnections.com

  i'll take a look at this and see if i can reproduce it.

  Status: Accepted

  Owner: mhern...@opensourceconnections.com

  Cc: mhern...@opensourceconnections.com
• Dec 19, 2008

  issue 5 (Can not recieve direct messages.) reported by jguadagno   -   Here is the code. DirectMessageClient directMessageClient = Twitter.CreateDirectMessageClient(); DirectMessage[] directMessages = directMessageClient.GetList(); foreach (DirectMessage message in directMessages) { Console.WriteLine("You received this direct message '{0}' from '{1}.", message.Text, message.SenderScreenName); } I receive the following exception ProtocolException: The remote server returned a unexpected response: (400) Bad Request.

  Here is the code. DirectMessageClient directMessageClient = Twitter.CreateDirectMessageClient(); DirectMessage[] directMessages = directMessageClient.GetList(); foreach (DirectMessage message in directMessages) { Console.WriteLine("You received this direct message '{0}' from '{1}.", message.Text, message.SenderScreenName); } I receive the following exception ProtocolException: The remote server returned a unexpected response: (400) Bad Request.
• Jul 27, 2008

  r12 (fixed up xml documentation. ) committed by mhern...@opensourceconnections.com   -   fixed up xml documentation.

  fixed up xml documentation.
• Jul 27, 2008

  r11 (Massive overhaul to use WCF service contracts and better exc...) committed by mhern...@opensourceconnections.com   -   Massive overhaul to use WCF service contracts and better exception handling for twitter, since it sends a 403 response along with the error message.

  Massive overhaul to use WCF service contracts and better exception handling for twitter, since it sends a 403 response along with the error message.