Thursday, February 19, 2015
Here is my presentation from today's webcast.
If you wish to see the webcast recording click here.
Thanks for joining me, please feel free to comment on this post if you have questions about this topic.
For more resources, please visit the last page of the presentation for additional links.
Tuesday, February 17, 2015
Just FYI, my speaking engagements for 2015 are posted here, If you are around – come see me!
If you were in one of my sessions, you can find links to the session code and presentation below.
Also – if you have any comments on my session – feel free to post it here!
February 19 – Online webcast - Building .NET Client Tools for SharePoint Online
March 19 – Victoria SPUG - The future of full trust solutions: Migration & Upgrade
June 6 - SPS Calgary - (2 topics) The future of full trust solutions: Migration & Upgrade ; How I built my first commercial SharePoint hosted app
June 17 - SPBiz online conference - Building .NET Client Tools for SharePoint Online
June 18 – Hamilton SPUG - Building .NET Client Tools for SharePoint Online
July 25 - SPS NYC - The future of full trust solutions: Migration & Upgrade
Thursday, February 12, 2015
FYI, this is a very strange bug I just stumbled upon in IE8, even other IE versions running in IE8 mode (which means – anyone using IE with SharePoint 2010)…
It appears while IE8 can handle a simple string split by character, such as “a,b,c,d”.split(“,”) – it is having a really hard time working with a regular expression split.
It is supposed to be supported, it is working on any other browser including IE9+…
Here is what I have, splitting a string by matching tokens inside [ ]:
var arr = str.split(/\[(.*?)\]/);
All browsers will return all text before, inside and after the matches.
IE8, it appears, is the only one out of the bunch not returning the text inside the token.
BTW, if you ask me – IE8 is the only browser who is actually doing what I asked – which is to split by the match, while I would say all other browsers are in the wrong – splitting by the matches themselves in the regex… but if all browsers do one thing and IE8 does another, it just makes it impossible to rely and use this API.
Well, off to find another solution.