English Whether you are serious SharePoint Apps provider or seasonal apps provider; you may have been experiencing the high complexity developing the apps. This is because in many cases, developing SharePoint Apps will require you to use from common JavaScript framework like JQuery, AngularJS, Reqwest to more specific JavaScript framework to JavaScript SharePoint Client Object Model. Many of SharePoint Apps developer will need to handle following challenges:
Create cross-domain call Create status notification REST call .
English We have request to support very old application, built using K2.NET 2003. K2.NET 2003 is a workflow engine (BPM) product by SourceCode Technology Holding Inc. It was initially released on 2003, before replace by the sucessor K2 Blackpearl in 2007 (see the history here). An 13 years old product, and yes we still have some application using it. While most of our development tools have been upgraded, the latest K2.
English There are more than 300 SharePoint PowerShell cmdlets and its growing and changing from time-to-time. How administrator or developer will be able to remember all of those cmdlets? The answer :
Using HELP (get-help) if you have access to PowerShell console and Microsoft.SharePoint.PowerShell snap-in ; PowerShell for SharePoint Command Builder (http://bit.ly/16masoE). The PowerShell for SharePoint Command Builder is a powerfull dictionary tools - build using Silverlight that lists all SharePoint’s PowerShell cmdlets.
English In case you have not tried Windows Azure to host your blog, I think it is time todo so; because Windows Azure is also capable to host many types of blogging platform such as Wordpress. I stumbled upon “Convert a Wordpress Site to Multisite” - when trying to figure-out how to host my blog in Windows Azure. Instead of using FTP or GIT as described in that article, I use WebMatrix and standard Wordpress configuration in Windows Azure.
_English_I have same experience with Arudell, who wrote SharePoint Installer Troubleshooting here, however with different path of achieving the success. Problem summary Among some servers in our farm, we had almost un-fixed issue. The problem is all server have been updated with SharePoint Server 2010 SP1 but the newer servers show version 14.0.6028.1000 and on the older servers show version 14.0.6029.1000. This is really stressing, since I can not re-deploy SP1 to fix the issue.
SharePoint 2010: Troubleshoot Language Pack 14.0.6028.1000 | Ideas For Free - Jan 4, 2013
[…] Subsequently apply other patches such as (install in correct order as following): - sharepointfoundation2010sp1-kb2460058-x64-fullfile-en-us.exe - officeserver2010sp1-kb2460045-x64-fullfile-en-us.exe - serverlanguagepack2010sp1-kb2460056-x64-fullfile-en-us.exe - serverlanguagepack2010sp1-kb2460056-x64-fullfile-??-??.exe (if you have other language pack) - wacserver2010sp1-kb2460073-x64-fullfile-en-us.exe (if you have Office Web Apps) - wacserver2010sp1-kb2460073-x64-fullfile-??-??.exe (if you have other language pack for Office Web Apps)When you install those patches, make sure to use PACKAGE.BYPASS.DETECTION.CHECK=1 option, to bypass version checking.
English Its been a history, that some early release of CU contains regression bug or a slip-streamed bits contains incomplete update. Early-adopter sometimes face a dead-end situation, where the early-release patch has been deployed and unable to install the new update. The reason is because every patch/CU also contains version checking mechanism that will prevent installation/patching to wrong system. Basically, it does your homework to read the pre-requisites in the system.
[Mike]( “mike70@hotmail.com”) - Feb 0, 2013
Hi and thanks for good info. I also found this great article on how to do it automartically: http://blog.viitaila.fi/2013/01/28/changing-the-product-key-of-windows-from-mak-to-kms-with-a-powershell-script/ [cakriwut]( “cakriwut@gmail.com”) - Feb 4, 2013
Thanks for the info.
English:
As MSDN Ultimate subscriber, we may have access to volume license installer. In order to activate volume license, one can use MAK (Multiple Activation Key) or KMS (Key Management Service). You can imagine MAK as out-premise activation Microsoft’s and KMS as in-premise activation; both requires Administrator authorization. When VL activation is unsuccessful you can identify the reason by looking at the Activation Error Codes and find the description in Microsoft website.