In part four I mentioned that there would be a problem in the future with this solution. In the second part of this series we created a simple function that generated a HTTP request to send to the Twitter API. As part of that request we sent a username and password. This known as “basic
Category: Twitter
SharePoint as a Twitter Client. Sort of – Part Four
In part three I said there was bit of functionality left to clear up. We have to run the process manually. We actually did a little bit of the ground work in part two. One of the pieces of code was the main function that brings all the bits and pieces together – it was
Share this:
SharePoint as a Twitter Client. Sort of – Part Three
Following on from part two I commented that there were a couple of issues outstanding, It doesn’t automatically update the SharePoint list. We have to repeat the list creation process every time. We have to run the process manually. This post will cover the first item on the list and is really straight forward.
Share this:
SharePoint as a Twitter Client. Sort of – Part Two
I intended to follow on from part one a bit sooner but it’s been really busy at the office! In part one I gave a brief overview of what I was trying to accomplish and how to get a rough prototype working. While it did the job I highlighted the following limitations. It only fetches
Share this:
SharePoint as a Twitter Client. Sort of – Part One
This is going to be quite lengthy so I’ll split into a couple of posts. Back in March, Mark Wilson of MarkWilson.co.uk (if you’re not reading his blog….go check it out now!) asked the following on Twitter. Does anyone know how to read XML (i.e. Twitter updates) into a SharePoint List (not the XML webpart
Share this:
I’m on twitter
I’ve finally succumbed and signed up for Twitter (@AndyParkes) I still don’t quite get it just yet but then again I didn’t get Flickr or Facebook to begin with either so thought it wouldn’t hurt to give it a go Come say hi (or whatever it is you do there :-) )