I finally have a blog (again). Hopefully I won’t forget to renew my domain name and lost all my blog posts once more! Thank God I didn’t have many to begin with!
Based on proved statistics (feel free to google that yourself), things usually gets better on the second time (or never). I guess we’ll see!
Stayed tune!
I am one of victims too! When I woke up this morning, I discovered that my Galaxy Nexus was rebooting non-stopping. It got as far as loading up the Google logo and it died and started rebooting again. After going through many forums and blogs, I finally found this link in one of the forums and formatted only in plain text (I guess there is still plenty of room for improvement in my googling skill). I hope you guys will find it handy if you are one of the unlucky ones:
Hard Reset: http://support.verizonwireless.com/clc/devices/knowledge_base.html?id=51446&sayt=hard%20reset%20nex*
Just got my Galaxy Nexus on Ice Cream Sandwich yesterday and like it so far. The most compelling features to me are the improved speed, user interface, and the new notification bar where you can sweep each notification one by one (similar to the new feature on the iPhone with iOS 5).
The only thing that I’m not so sure about having the Power/lock screen button on the side. I have a Nexus One previously and have played with many iPhones before and they all have that button on the top. It’s going to take me a while to get used to new one.
Okay, I guess I’ll leave the detailed reviews and features of the device to the experts:
http://www.engadget.com/2011/12/01/android-4-0-ice-cream-sandwich-review/
It’s finally time to upgrade your MOSS site to SharePoint 2010. You may need to set the old MOSS site read-only right before migration but you are stuck with the much slower Stsadm -Setsitelock command because there aren’t any MOSS snap-in for PowerShell. I hope you find this handy:
param
(
[string] $webAppUrl = $(Read-Host “Please specify the url of the Web Application”),
[switch] $readOnly = $false
)
[System.Reflection.Assembly]::LoadWithPartialName(“Microsoft.SharePoint”) | Out-Null
[System.Reflection.Assembly]::LoadWithPartialName(“Microsoft.SharePoint.Portal”) | Out-Null
$spWebApp = [Microsoft.SharePoint.Administration.SPWebApplication]::Lookup($webAppUrl)
if ($spWebApp -ne $null)
{
$spWebApp.Sites | % {
$site = $_
$site.ReadOnly = $readOnly
}
}
Staying as up-to-date on as many patches as possible is usually a best practice, except when you run into something strange like this. If you have already upgraded your project to Visual Studio 2010 and your SharePoint 2007 environment is at a version beyond 12.0.6421.1000 (SP2), you will not be able to update any new SharePoint 2007 workflows. The existing code will still compile fine, but you won’t be able to modify it because some of the key shapes are missing in the toolbox when you open a workflow file; i.e., OnWorkflowActivated. And if you want to create a new MOSS workflow project, you will get this error message:
Exception of type “System.PlatformNotSupportedException” was thrown
This is a known bug to Microsoft, but unfortunately there isn’t a hotfix available for the problem. After speaking with Microsoft Support, we did came up with a workaround for people, like me, who are not ready to upgrade to SharePoint 2010, nor able to rollback the VS project to VS2008.
All you have to do is build a VM that has VS2010 and SharePoint 2007 with patches ONLY up to 12.0.6421.1000. Then download the workflow project from your source code system, open it in VS2010, and you are ready to build some custom MOSS workflows.