Microsoft announced the IIS Search Engine Optimization (SEO) Toolkit Beta – a brand new free toolkit that helps Web developers, hosting providers, and server administrators improve their sites’ relevance in search results by recommending how to make them more search engine-friendly. The SEO Toolkit Beta is available for installation via the Microsoft Web Platform Installer 2.0 Beta at http://www.microsoft.com/web/downloads/platform.aspx
Let’s try it out and see whether it will work with SharePoint. By the way Scott Guthrie has post of details of the toolkit here.
The speakers for the session just uploaded their slides on Enovade’s company website.
Local SharePoint User Group had their meeting at KL Sentral’s MDEC CyberCenter this Wednesday. This was a joined effort from MDEC, Microsoft, Enovade and SPUG to make the event a success.
Theme of the meeting was about SharePoint backup and recovery strategies. 1st session speaker is Chloe Chua from Enovade to presented a strategy and plan for SharePoint’s disaster recovery followed by Dr Jiang (COO of Avepoint) who shared on how to bring the DR strategy further by using tools from Avepoint.
More than 30 attendees came and the overall (regular Microsoft style) rating such as effectiveness of speakers and relevance of topics are around 7.5.
Thanks for Enovade for the sponsorship of snacks, Microsoft for providing marketing and logistic support and MDEC for allowing SPUG to use their venue.
Below are some photos from the event
 |
|
 |
|
| Almost full house with more than 30 turnouts |
|
Tianyi Jiang, COO Avepoint |
|
 |
|
 |
|
| Chloe Chua from Enovade |
|
SPUG co-founder Matthew Khaw |
|
Rahimah from Microsoft Innovation Center
Just to announce that Malaysia SharePoint User Group (MySpug) has our own URL and website hosted by Office Live at http://spugmalaysia.org
Look forward for more features inside Office Live to enhance the feature while at the same time I got to plan how to consolidate the websites in Facebook and ISPA into spugmalaysia.org
When you try to install a ClickOnce VSTO application you got the follow error saying your .NET Framework version is not correct (however Windows 7 ships with .NET 3.5 SP1)
Thanks to a blog post from the VSTO product team, I realize that Windows 7 RC left our a file in C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.5\RedistList
When I start up my Windows 2008 VPC, I see there is a FrameworkList.xml file inside
So I copy it out from my VPC, then I restart Visual Studio (it is not mentioned in the blog) and republish the VSTO app. The installer is now working!
A lot of complains gone out in the web pass week after MOSS SP2 was released. For a number of customers, after they installed the service pack they notice the server license becomes a trial license and will expire in 180 days. You can check it out by going to Central Admin site and look out for Upgrade and Migration section, look for an option called Convert Licence Type. If you are impacted, you will see a the word Office SharePoint License Trial
There is nothing much to panic according the the knowledge base article 971620 here as this ‘bug’ in SP2 does not corrupt your data, nor does it impact your MOSS functionalities (unless you don’t enter the license number after 180 days). What you need to do is just to reenter the license number
This is something I notice because I got a VPC built by a friend that seems to be slow even with Hardware Virtualization enabled. Then I check out he display setting properties and realize the color quality has been set to 16bit while my host machine is running at 32bit.
I feel like things are faster now after setting the color quality to 32bit on the guest VM.
Today I am trying out JQuery on Visual Studio 2008 for the first time. I go to the website at www.jquery.com and downloaded the library as well as the document for Visual Studio.
So I imported the JQuery library into my VS project
But when I want to try to the intellisense, I notice it is not working!! It should be able to recognize the famous $!!
Then I realize at the bottom of the VS IDE, there is an error message -
Warning 1 Error updating JScript IntelliSense: D:\workspace\Projects\JQuerySample\JQuerySample\scripts\jquery-1.3.2.js: Object doesn’t support this property or method @ 2139:1 D:\workspace\Projects\JQuerySample\JQuerySample\Default.aspx 1 1 JQuerySample
But this is not a bug inside the JQuery library itself. So I went back to scottgu’s blog post about on JQuery I notice something very difference with his library (besides the fact that he is using version 1.2.6).
I notice mine has got an extra number 2 at the end of vsdoc there. So I go back to the Google code side where I downloaded the file and I found out en they release a new vsdoc file to replace the exisiting deplecated one, they ‘tangan gatal’ change the name to jquery-1.3.2-vsdoc2.js. VS Interllisense only programmed to regconized [Javascript file name]-vsdoc.js without the 2 at the back there.
That vsdoc2 is the cause of the problem here! Just rename it to jquery-1.3.2-vsdoc.js and you got JQuery Intellisense working!
I know this is not the place to blog about family relationships (where are the codes?!) but when you have Raymond Chen (author of the book Old New Thing and developer in Windows Shell team) talked about this topic and finding out that he can write in Chinese then this is awesome.
Normally we Asians think that in English there are no word/ vocabulary to tell you want relationship you have with i.e. your father’s sister in law’s daughter. Chinese have word for every relationship but in English an uncle is just uncle, outsiders of your family won’t know when you call your uncle it’s your dad’s side or mum’s side. But here in Raymond’s blog post, I actually find out there is.
http://blogs.msdn.com/oldnewthing/archive/2009/04/27/9570320.aspx
I added MSMQ to my WCF web service (which was running OK) by adding the following endpoint to the service in web.config file
<endpoint
address="net.msmq://server/private/queue1"
binding="netMsmqBinding"
bindingConfiguration="MsmqConfiguration"
contract="ITestQueue" />
I also added the following binding
<netMsmqBinding>
<binding name="MsmqConfiguration"
exactlyOnce="false">
<security mode="None"/>
</binding>
</netMsmqBinding>
Once I deployed the Wcf service on Windows Server 2008, I also enable net.msmq on the website using the following command
appcmd set app "localhost/service" /enabledProtocols:net.msmq
However when I try to point to the svc file from my browser I got an Error 503 instead. Removing the MSMQ endpoint and I have the service up and running again.
After that I have a look at the website via the IIS Management Console and I realize that http protocol is not enabled for the website anymore
A normal web app will have http protocol such as below
At last I figure out that the appcmd actually overwrote the settings instead of adding on to it. So the correct appcmd command is:-
appcmd set app "localhost/service" /enabledProtocols:net.msmq, http
And I have the site running again with both http and msmq protocol enabled.
