Microsoft release on February 23, 2010 the February 2010 Cumulative Updates, they are available for download:
Have also updated the list of the SharePoint Levels in a previous post – Determining the current SharePoint Level, in order to make it easier to keep track of all the versions.
As mentioned in the previous post: “Issues when developing with Visual Studio 2010 RC and SharePoint 2010 Beta 2” the process was not as smooth nor as polished as it was expected.
While the uninstall and re-installation process was easy enough, there were some items left behind. After spending a considerable amount of time and though thinking what the issue at hand could be the solution ended up being answered with the following questions:
What was the version of the Framework that was removed?
Where was that Framework installed to?
That said, the numbers of the RC version are: 4.0.30128 and they were installed to \Windows\Microsoft.Net\Framework64\. It would not hurt to check the other folder to ensure that everything is back to normal ( \Windows\Microsoft.Net\Framework\ ).
The solution is
Once this is accomplished, the errors disappeared immediately even while the Visual Studio 2010 Beta 2 instance was still open.
Hope this helps others as much as it did help me getting back into developing with Visual Studio 2010 Beta 2, not to mention avoiding the rebuild of the entire Virtual machine.
Recently, since development with SharePoint 2010 Beta 2 had been going so well; decided to jump into installing Visual Studio 2010 RC.
Followed the common steps:
Immediately assumed that SharePoint 2010 Beta 2 and Visual Studio 2010 RC would get along well and for the most part they did.
While in the IDE was able to perform pretty much all the necessary tasks a developer does:
The issue would arise when attempting to Debug or Run the application:
The error is caused because the Frameworks are not the same, in other words to develop solutions with Visual Studio 2010 RC and SharePoint 2010 you must have also SharePoint 2010 RC. At the moment of this posting SharePoint 2010 RC is only available to selected partners.
The solution or so I thought was to revert back to:
After reverting completely to a complete set of Visual Studio and .Net Framework Beta 2, was still receiving errors.
That’s the price you pay for being on the bleeding edge, right?
It has been a frustrating experience, but in the end I found a solution.
Will post it on soon; stay tuned!
12.0.0.6036 | August 24, 07 hotfix |
12.0.0.6039 | October Public Update |
12.0.0.6219 | Service Pack 1 |
12.0.0.6300 | Post-SP1 Hotfix (KB941422) |
12.0.0.6301 | Post-SP1 Hotfix (KB941274) |
12.0.0.6303 | Post-SP1 Hotfix (KB9418945) |
12.0.0.6318 | Infrastructure Update (KB951695 & KB951297) |
12.0.0.6327 | August 08 Cumulative Update (KB956056 & KB956057) |
12.0.0.6331 | October 08 Cumulative Update ( KB957691 + KB957693, KB958567 and KB958569 ) |
12.0.0.6335 | December 08 Cumulative Update ( KB960010 + KB960011 ) |
12.0.0.6341 | February 09 Cumulative Update ( KB961755 + KB961756 ) |
12.0.0.6421 | Service Pack 2 ( KB953338 + KB953334 ) |
12.0.0.6504 | Service Pack 2 + April 09 Cumulative Update ( KB968850 + KB968851 ) |
12.0.0.6510 | Service Pack 2 + June 09 Cumulative Update ( KB971538 + KB971537 ) |
12.0.0.6520 | Service Pack 2 + October 09 Cumulative Update ( KB974988 + KB974989 ) |
12.0.0.6524 | Service Pack 2 + December 09 Cumulative Update ( KB977027 + KB977026 ) |
12.0.0.6529 | Service Pack 2 + February 2010 Cumulative Update ( KB978396 + KB978395 ) |
12.0.0.6535 | Service Pack 2 + April 2010 Cumulative Update ( KB981043 ) |
12.0.0.6539 | Service Pack 2 + June 2010 Cumulative Update ( KB 983311 + KB983310 ) |
14.0.4536.1000 | SharePoint 2010 Beta 2 |
The SharePoint December 2009 Cumulative Update was released on December 15, 2009, it consists of two particular updates WSS 3.0 – KB 977027 and MOSS 2007 – KB 977026.
Once the updates are applied the new version is: “12.0.0.6524”, as always make sure you backup properly your Farm in case of any possible disaster.
In case you are interested in finding in more details about the current SharePoint Level the following links are very useful:
Recently, I came across a blog posting that a T-SQL Script that generates a Christmas Card. It is the best one I have encountered yet.
Hope you enjoy it as much as I have:
If you have had the chance to download either SharePoint Foundation 2010 or SharePoint 2010 it is most likely that you have attempted to install with a local account on a Single Server Install. Odds are you have probably gotten disappointed because the wizard did not allow the installation with a local account. You were not the only one disappointed, although that disappointment did fuel the need to find a solution.
After some research, I did find a useful blog posting from the field that had the exact solution to my dilemma. The solution consisted in using PowerShell and a script named: “New-SPConfigurationDatabase”; this script is to be executed through the SharePoint 2010 Management Shell.
The step-by-step process would be like this:
1- Open the PowerShell Management Shell
Entering the prompted items:
DatabaseName
DatabaseServer
FarmCredentials
Passphrase
The process will take a while, when completed the cursor will appear in the command line.
2- Open the Configuration Wizard
Click Next Button
3- Restart the Services
Click Yes Button
4- Leave the Do not disconnect from this server setting selected
Click Next Button
5- Continue the normal course of the Configuration Wizard
There you go, now you have a Single Installation Server with a local account, this will work for both SharePoint Foundation 2010 and SharePoint 2010.
The details regarding SharePoint 2010 have long been awaited and while many have listed or blogged about it, this a compilation of many of these changes and enhancements.
While it is not in depth, it can be expanded with your comments and suggestions; feel free to leave comments so that we can improve upon this list.
