Those of you who know me knows how much I don't get along with PowerShell.
When I will get some spare time I will write a "CSharpShell", which will basically allow me to use .NET syntax...
But in the meanwhile, I always find myself looking for that one line of STSADM command to enable developer dashboard in STSADM... so i thought i might post it here:
stsadm -o setproperty -pn developer-dashboard -pv on
or
stsadm -o setproperty -pn developer-dashboard -pv ondemand
enjoy...
Friday, January 15, 2010
Encode in JS Decode in C# problem
Just a quick one guys,
Recently we had a customer who complained about French tags that are not working with our tagging feature (field type, tag cloud for SP 2007 - pretty cool actually).
Well, apperantly we were doing some encoding of text in javascript using "escape()" and trying to decode it in C# on the server side using UrlDecode with no luck.
the text: "de l'entité" was not decoding correctly.
After trying to figure our whats wrong on the server side decoding function (I tried several alternatives) I almost gave up with no success whatsoever :(
So, I turned to look for alternatives in the Javascript encoding and found this new method called "encodeURI()". Apperantly this method can safely replace our "escape/unescape" in Javascript only it supports proper encoding and decoding with C# with no problems.
Works like a charm - from now on, use "encodeURI/decodeURI"!
Cheers, Shai.
Recently we had a customer who complained about French tags that are not working with our tagging feature (field type, tag cloud for SP 2007 - pretty cool actually).
Well, apperantly we were doing some encoding of text in javascript using "escape()" and trying to decode it in C# on the server side using UrlDecode with no luck.
the text: "de l'entité" was not decoding correctly.
After trying to figure our whats wrong on the server side decoding function (I tried several alternatives) I almost gave up with no success whatsoever :(
So, I turned to look for alternatives in the Javascript encoding and found this new method called "encodeURI()". Apperantly this method can safely replace our "escape/unescape" in Javascript only it supports proper encoding and decoding with C# with no problems.
Works like a charm - from now on, use "encodeURI/decodeURI"!
Cheers, Shai.
Subscribe to:
Posts (Atom)