Tuesday, December 22, 2009
Microsoft Ups The ALM Ante With Its Bet On Teamprise
Expect VS 2010 To Accelerate The Shakeout In The Application Life-Cycle Management Market
by Jeffrey S. Hammond
with Mike Gilpin and Adam Knoll
Microsoft’s Team Foundation Server (TFS) has proven very popular with .NET developers but not so much with Eclipse developers. This presents a problem for Microsoft, because many of its largest customers develop for both .NET and Java and want a consolidated application life-cycle management (ALM) solution that will support development teams regardless of what platform they use. Over the past few years, Microsoft has pointed to a partner’s product — SourceGear’s Teamprise Client Suite — as its recommended solution to the heterogeneity problem. This has proven unsatisfactory to many customers, so after a long internal debate, Microsoft has acquired the Teamprise code base. Microsoft will release an updated version of Teamprise as part of its Visual Studio 2010 release train and will reduce the new solution’s overall per-developer cost. The resulting product combination will prove much more attractive to large enterprises, which will now have the option of a lower-cost ALM solution for all the platforms they use, supported by the full force of Microsoft.
Friday, December 18, 2009
1. SharePoint Server 2010 will be 64-bit only.
2. SharePoint Server 2010 will require 64-bit Windows Server 2008 or 64-bit Windows Server 2008 R2.
3. SharePoint Server 2010 will require 64-bit SQL Server 2008 or 64-bit SQL Server 2005.
In addition to the requirements listed above we also wanted to share with you some preliminary detail about SharePoint Server 2010 browser compatibility.
To ensure the best possible experience across multiple browsers weâ€™re focusing our SharePoint 2010 engineering efforts on targeting standards based browsers (XHTML 1.0 compliant) including Internet Explorer 7, Internet Explorer 8 and Firefox 3.x. running on Windows Operating Systems. In addition weâ€™re planning on an increased level of compatibility with Firefox 3.x and Safari 3.x on non-Windows Operating Systems. Due to this focus Internet Explorer 6 will not be a supported browser for SharePoint Server 2010.
So, what can you do today to get into the best shape for SharePoint Server 2010?
1. Start by ensuring new hardware is 64-bit. Deploying 64-bit is our current best practice recommendation for SharePoint 2007.
2. Deploy Service Pack 2 and take a good look at the SharePoint 2010 Upgrade Checker thatâ€™s shipped as part of the update. The Upgrade Checker will scan your SharePoint Server 2007 deployment for many issues that could affect a future upgrade to SharePoint 2010.
3. Get to know Windows Server 2008 with SharePoint 2007, this post is a great starting point.
4. Consider your desktop browser strategy if you have large population of Internet Explorer 6 users.
5. Continue to follow the Best Practices guidance for SharePoint Server 2007.
6. Keep an eye on this blog for updates and more details in the coming months.
Below are a few common Q&Aâ€™s (which weâ€™ll add to as required)
Q: What about Internet Explorer 6 and SharePoint 2010 publishing sites?
A: The Web Content Management features built into SharePoint 2010 will provide a deep level of control over the markup and styling of the reader experience. These features will enable customers to design pages that are compatible with additional browsers for viewing content, including Internet Explorer 6. A standards based browser such as Internet Explorer 7, Internet Explorer 8 or Firefox 3.x will be required to author content.
Q: Is Internet Explorer 6 officially supported by Microsoft?
A: Official Microsoft Product Support for Internet Explorer 6 follows the lifecycle of the Operating System with which it was shipped. In order for customers to receive product support through the Mainstream Support and Extended Support phases, they need to have installed a supported Service Pack. For example, customers who are using Windows XP must transition to Service Pack 3 by July, 2010 and are eligible to receive support for Internet Explorer 6 until April, 2014.
You can find additional information on Microsoftâ€™s Support Lifecycle Policy including specific dates, product information and support offerings here: http://support.microsoft.com/gp/lifepolicy.
Q: Why are you only supporting the 64-bit versions of SQL Server 2005 or 2008 for SharePoint Server 2010?
A: This decision was based on our current test data for SharePoint Server 2010 and real world experience from customers running SharePoint Server 2007 with 32-bit SQL Server. SharePoint performance and scalability can benefit significantly from 64-bit SQL Server and the throughput increases are significant enough for us to make the difficult decision to only support SharePoint Server 2010 on 64-bit SQL Server 2005 or 2008. It has been our strong recommendation for some time that SharePoint Server 2007 customers take advantage of 64-bit SQL Server due to the inherent performance and scale benefits it can provide.
Q: Where can I find more information on the advantages of 64-bit hardware and guidance on how to migrate SharePoint from 32-bit to 64-bit.
A: These two TechNet articles are a good starting point;
Advantages of 64-bit hardware and software (Office SharePoint Server 2007)
Migrate an existing server farm to a 64-bit environment (Office SharePoint Server 2007)
You can connect external data from almost any data sources directly to SharePoint lists (no web parts) simply in the list settings dialog using the SharePoint Business Data List Connector (BDLC) found here:
All list features are available, e.g. alerts and workflows to start business actions in SharePoint, if external data is changed.
Just download and evaluate for free.
Download this guide as a Microsoft Word document (.docx).
Microsoft SharePoint Server 2010 Evaluation Guide (http://go.microsoft.com/fwlink/?LinkId=167123)
1) End User Evalution Guide - http://bit.ly/DM5mH
2) Developer Evaluation Guide - http://bit.ly/21ezZ2
3) IT Pro Evaluation Guide - http://bit.ly/1IENu4