Announcing SharePoint Server 2010 Preliminary System Requirements
By rriley
We’ve heard loud and clear that you want system requirements information as early as possible to assist in your budgeting and planning, so today we’re happy to announce (and confirm) some preliminary system requirements for SharePoint Server 2010:
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)
Monday, June 01, 2009
Monday, May 25, 2009
Visual Studio 2010 and .NET Framework 4 Beta 1
Visual Studio 2010 and .NET Framework 4 Beta 1
Visual Studio 2010 Beta 1 as well as .NET Framework 4.0 Beta 1, for MSDN subscribers and general public both new technologies were released on Wednesday, 18th May 2009.
http://msdn.microsoft.com/en-us/vstudio/dd582936.aspx
Visual Studio 2010 Beta 1 as well as .NET Framework 4.0 Beta 1, for MSDN subscribers and general public both new technologies were released on Wednesday, 18th May 2009.
http://msdn.microsoft.com/en-us/vstudio/dd582936.aspx
Thursday, May 21, 2009
How Do I? Videos
SharePoint Products and Technologies "How Do I?" Videos
http://technet.microsoft.com/en-us/office/sharepointserver/dd353225.aspx
http://technet.microsoft.com/en-us/office/sharepointserver/dd353225.aspx
Thursday, May 14, 2009
CSS Reference Chart for SharePoint 2007
A comprehensive guide to identify and customize styles for your sharepoint sites
http://www.heathersolomon.com/content/sp07cssreference.htm
http://www.heathersolomon.com/content/sp07cssreference.htm
Plan for software boundaries (Microsoft Office SharePoint Server 2007)
A nice article on Plan for software boundaries (Office SharePoint Server) by Technet
In this article:
Planning and performance guidance updates
Test environment
Test results
Guidelines for acceptable performance
This article provides information to help you understand the tested performance and capacity limits of Microsoft Office SharePoint Server 2007, provides information about the test environment and test results, and offers guidelines for acceptable performance. Use the information in this article to determine whether your planned deployment falls within acceptable performance and capacity limits.
Click for details : http://technet.microsoft.com/en-us/library/cc262787.aspx
In this article:
Planning and performance guidance updates
Test environment
Test results
Guidelines for acceptable performance
This article provides information to help you understand the tested performance and capacity limits of Microsoft Office SharePoint Server 2007, provides information about the test environment and test results, and offers guidelines for acceptable performance. Use the information in this article to determine whether your planned deployment falls within acceptable performance and capacity limits.
Click for details : http://technet.microsoft.com/en-us/library/cc262787.aspx
Microsoft Office SharePoint Server 2007 Vs Windows SharePoint Services 3.0
It is very difficult to choice for organizations to select the Microsoft Office SharePoint Server 2007 Vs Windows SharePoint Services 3.0.
Here you can find the true difference:
MOSS comparasion with WSS
Comparasion from Microsoft Site
Here you can find the true difference:
MOSS comparasion with WSS
Comparasion from Microsoft Site
Monday, May 04, 2009
Wednesday, April 29, 2009
Business Data Catalog and MOSS
Business Data Catalog and MOSS
The Business Data Catalog is a very useful feature of Microsoft Office SharePoint Server 2007 that provides a way of integration of business data from back-end server applications, like SAP or Siebel, with your corporate portal to provide rich solutions for end users without writing any code. You register business data exposed in databases or through Web services in the Business Data Catalog by creating metadata that describes the database or Web service. The Business Data Catalog then uses this metadata to make the right calls into the data source to retrieve the relevant data.
The business data entities are available for use by any of the following business data features:
The Business Data Catalog is a very useful feature of Microsoft Office SharePoint Server 2007 that provides a way of integration of business data from back-end server applications, like SAP or Siebel, with your corporate portal to provide rich solutions for end users without writing any code. You register business data exposed in databases or through Web services in the Business Data Catalog by creating metadata that describes the database or Web service. The Business Data Catalog then uses this metadata to make the right calls into the data source to retrieve the relevant data.
The business data entities are available for use by any of the following business data features:
Business Data Web Parts- Business Data in Lists
- Business Data Actions
- Business Data Search
- Business Data in User Profiles
for more details .....
http://msdn.microsoft.com/en-us/library/ms546541.aspx
Business Data Catalog - getting started
http://www.lightningtools.com/bdc-meta-man/moss-business-data-catalog-getting-started.aspx
Tuesday, April 28, 2009
Ajax Update Panel in Publishing Portal
If ajax update panel are not working for you in Publishing portal try to move
asp:ContentPlaceHolder tag insde form tag.
In master page of publishing portal (BlueBand.master) this asp:ContentPlaceHolder is usually above the form tag , to make AJAX update panel work you can move this tag inside form tag by opening BlueBand.master in Sharepoint designer
asp:ContentPlaceHolder tag insde form tag.
In master page of publishing portal (BlueBand.master) this asp:ContentPlaceHolder is usually above the form tag , to make AJAX update panel work you can move this tag inside form tag by opening BlueBand.master in Sharepoint designer
HOW to use Microsoft AJAX in SharePoint webpart ??
HOW to use Microsoft AJAX in SharePoint webpart ??
Read it here
http://sharepoint.microsoft.com/blogs/mike/Lists/Posts/Post.aspx?ID=3
Read it here
http://sharepoint.microsoft.com/blogs/mike/Lists/Posts/Post.aspx?ID=3
Friday, April 24, 2009
Microsoft® Windows® SharePoint™ Services v3 (WSS) demo site
Avery useful site for Microsoft® Windows® SharePoint™ Services v3 (WSS) demos, articles, resources.
http://www.wssdemo.com/default.aspx
http://www.wssdemo.com/default.aspx
Thursday, April 23, 2009
A handy Visual Studio template for Windows SharePoint Services 3.0
A handy Visual Studio template for Windows SharePoint Services 3.0
http://blogs.code-counsel.net/Wouter/Lists/Posts/Post.aspx?List=c04a88a9%2Dd138%2D4ac3%2Da2bb%2Db95c9fdd114e&ID=78
Friday, April 17, 2009
Steps to Create & Deploy WSP
1) In your custom feature folder, create a file "feature.xml"
Following is the general format of the file:
Description="This is my feature containing a list"
Version="1.0.0.0"
Hidden="FALSE"
Scope="Web"
DefaultResourceFile="core"
xmlns="http://schemas.microsoft.com/sharepoint/">
(Change the GUID of the feature with your own)
2) Create %YourFeatureName%manifest.xml file for the feature in the following format:
Type="108"
BaseType="0"
OnQuickLaunch="FALSE"
FolderCreation="FALSE"
SecurityBits="12"
Sequence="999"
DisplayName="My List"
Description="This is my custom list based on the discussions list"
Image="/_layouts/images/itdisc.gif"/>
3) Create a manifest.xml file for the feature:
4) Inside the source folder, create a DDF file:
.OPTION Explicit
.Set DiskDirectory1="..\bin"
.Set CabinetNameTemplate="MyListSolution.wsp"
manifest.xml
; These directory names (DestinationDir) are used for the folders creation under 12\TEMPLATE\Features
.Set DestinationDir="MyList\ListTemplates"
MyList\ListTemplates\MyListManifest.xml
.Set DestinationDir="MyList\Messages"
MyList\Messages\schema.xml
.Set DestinationDir="MyList"
MyList\Feature.xml
5) Create a build.cmd file in the source folder:
build.cmd
@setlocal
@pushd.
@cd %~dp0
makecab /f wsp.ddf
@popd
@endlocal
5) Now, to deploy the solution; create the following steps:
DeployMyListSolution.cmd
@setlocal
@pushd.
@set PATH=C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN;%PATH% @cd %~dp0
stsadm.exe -o addsolution -filename MyListSolution.wsp
stsadm.exe -o deploysolution -name MyListSolution.wsp -local
@pause
@popd
@endlocal
6) After you have deployed the solution, go to Central Adminsitration > Operations > Solution Management. From here, deploy your solution on the web applications you want.
If you want to retract the solution you need to create the following file in the solution
RetractMyListSolution.cmd
@setlocal
@pushd.
@set PATH=C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN;%PATH% @cd %~dp0
stsadm.exe -o retractsolution -name MyListSolution.wsp –local
stsadm.exe -o deletesolution -name MyListSolution.wsp
@pause
@popd
@endlocal
-------------------------------------------------------------------------------------------------------------------------------------------------
If you want to know about the elements used in the above mentioned xml file formats, please view these links:
http://www.theartofsharepoint.com/2007/05/how-to-build-solution-pack-wsp.html
http://www.chrishines.com/techblog/default.aspx
http://msdn.microsoft.com/en-us/library/aa543741.aspx
http://geekswithblogs.net/evgenyblog/archive/2008/01/27/118966.aspx
Following is the general format of the file:
Description="This is my feature containing a list"
Version="1.0.0.0"
Hidden="FALSE"
Scope="Web"
DefaultResourceFile="core"
xmlns="http://schemas.microsoft.com/sharepoint/">
(Change the GUID of the feature with your own)
2) Create %YourFeatureName%manifest.xml file for the feature in the following format:
Type="108"
BaseType="0"
OnQuickLaunch="FALSE"
FolderCreation="FALSE"
SecurityBits="12"
Sequence="999"
DisplayName="My List"
Description="This is my custom list based on the discussions list"
Image="/_layouts/images/itdisc.gif"/>
3) Create a manifest.xml file for the feature:
4) Inside the source folder, create a DDF file:
.OPTION Explicit
.Set DiskDirectory1="..\bin"
.Set CabinetNameTemplate="MyListSolution.wsp"
manifest.xml
; These directory names (DestinationDir) are used for the folders creation under 12\TEMPLATE\Features
.Set DestinationDir="MyList\ListTemplates"
MyList\ListTemplates\MyListManifest.xml
.Set DestinationDir="MyList\Messages"
MyList\Messages\schema.xml
.Set DestinationDir="MyList"
MyList\Feature.xml
5) Create a build.cmd file in the source folder:
build.cmd
@setlocal
@pushd.
@cd %~dp0
makecab /f wsp.ddf
@popd
@endlocal
5) Now, to deploy the solution; create the following steps:
DeployMyListSolution.cmd
@setlocal
@pushd.
@set PATH=C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN;%PATH% @cd %~dp0
stsadm.exe -o addsolution -filename MyListSolution.wsp
stsadm.exe -o deploysolution -name MyListSolution.wsp -local
@pause
@popd
@endlocal
6) After you have deployed the solution, go to Central Adminsitration > Operations > Solution Management. From here, deploy your solution on the web applications you want.
If you want to retract the solution you need to create the following file in the solution
RetractMyListSolution.cmd
@setlocal
@pushd.
@set PATH=C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN;%PATH% @cd %~dp0
stsadm.exe -o retractsolution -name MyListSolution.wsp –local
stsadm.exe -o deletesolution -name MyListSolution.wsp
@pause
@popd
@endlocal
-------------------------------------------------------------------------------------------------------------------------------------------------
If you want to know about the elements used in the above mentioned xml file formats, please view these links:
http://www.theartofsharepoint.com/2007/05/how-to-build-solution-pack-wsp.html
http://www.chrishines.com/techblog/default.aspx
http://msdn.microsoft.com/en-us/library/aa543741.aspx
http://geekswithblogs.net/evgenyblog/archive/2008/01/27/118966.aspx
Wednesday, April 15, 2009
Here's a list of the top 100 sharepoint websites by Ian Morrish
Here's a list of the top 100 websites http://www.wssdemo.com/Pages/topwebsites.aspx selected by Ian Morrish
Friday, April 03, 2009
A nice SharePoint Tool (AD Self Service provides a SharePoint active directory web part)
A nice SharePoint Tool Which Reduces SharePoint Administrators Maintaining AD Users Profiles. SharePoint What they need do is just configure some specific permissions and then those job can be done by users themselves.
AD Self Service provides a SharePoint active directory web part that allow current login user to see and modify his/her own Active Directory information through SharePoint.
http://www.microsofttechnologies.blogspot.com
AD Self Service provides a SharePoint active directory web part that allow current login user to see and modify his/her own Active Directory information through SharePoint.
http://www.microsofttechnologies.blogspot.com
Wednesday, March 25, 2009
Required Validator for CheckBox List
Step by Step tutorial explaining how to add required Validator on Checkbox List
http://codeclimber.net.nz/archive/2007/07/19/How-to-add-a-required-validator-to-a-CheckBoxList.aspx
http://codeclimber.net.nz/archive/2007/07/19/How-to-add-a-required-validator-to-a-CheckBoxList.aspx
Monday, March 16, 2009
Oracle Developer Tools for Visual Studio
from Oracle.com..
The Oracle Developer Tools for Visual Studio (ODT) is a tightly integrated "Add-in" for Microsoft Visual Studio. ODT is free and it is available for Visual Studio 2008, Visual Studio 2005, and Visual Studio .NET 2003.
Integration with Visual Studio: Use Server Explorer to browse your Oracle schema and launch one of the many integrated Oracle designers and wizards to create and alter schema objects. Use Microsoft Query Designer to visually design queries.
Automatic .NET Code Generation: Use the Visual Studio 2005 Datasources Window, the Dataset Designer, and the TableAdapter Configuration Wizard to drag and drop and automatically generate .NET code.
Easy ASP.NET Web Development: If you're an ASP.NET web developer, ODT makes it easy to generate ASP.NET web applications with very little coding required.
Oracle Database Project with Source Control Integration: Generate SQL scripts for Oracle schema objects that your .NET application uses, manage them in an Oracle Database Project, check them into source control, edit the scripts in the Oracle SQL Editor, and execute them with a built in SQL*Plus execution engine.
PL/SQL Editor and Debugger: The fully integrated PL/SQL Editor and Debugger allows you to leverage all of your favorite Visual Studio debugging features from within PL/SQL code. You can even seamlessly step from your .NET code into your PL/SQL stored procedure code and back out again!
User-Defined Types (UDTs): Create UDTs in Oracle with multiple new designers. A powerful UDT Custom Class code generation wizard makes using UDTs from .NET code easy and fast. An application can be rapidly created that utilizes UDTs with almost no coding required.
NET Stored Procedure Deployment: The .NET Deployment Wizard makes it easy to deploy .NET stored procedures and functions into Oracle Database.
Data Editing, Stored Procedure Testing, Adhoc SQL Execution: When testing your .NET application you can use the Oracle Data Window to insert and update Oracle data. There's also a testbed for testing stored procedures and an Oracle Query Window for executing any SQL statement you choose.
Integrated Online Help System: The integrated context sensitive online help, including the Oracle SQL and PL/SQL Users Guides puts the Oracle documentation at your fingertips.
Import Table Wizard: This new wizard makes it easy to move tables and their data from external datasources such as Microsoft SQL Server, Microsoft Access and Excel spreadsheets into Oracle Database.
Follow the link for details ....
http://www.oracle.com/technology/tech/dotnet/tools/index.html
The Oracle Developer Tools for Visual Studio (ODT) is a tightly integrated "Add-in" for Microsoft Visual Studio. ODT is free and it is available for Visual Studio 2008, Visual Studio 2005, and Visual Studio .NET 2003.
Integration with Visual Studio: Use Server Explorer to browse your Oracle schema and launch one of the many integrated Oracle designers and wizards to create and alter schema objects. Use Microsoft Query Designer to visually design queries.
Automatic .NET Code Generation: Use the Visual Studio 2005 Datasources Window, the Dataset Designer, and the TableAdapter Configuration Wizard to drag and drop and automatically generate .NET code.
Easy ASP.NET Web Development: If you're an ASP.NET web developer, ODT makes it easy to generate ASP.NET web applications with very little coding required.
Oracle Database Project with Source Control Integration: Generate SQL scripts for Oracle schema objects that your .NET application uses, manage them in an Oracle Database Project, check them into source control, edit the scripts in the Oracle SQL Editor, and execute them with a built in SQL*Plus execution engine.
PL/SQL Editor and Debugger: The fully integrated PL/SQL Editor and Debugger allows you to leverage all of your favorite Visual Studio debugging features from within PL/SQL code. You can even seamlessly step from your .NET code into your PL/SQL stored procedure code and back out again!
User-Defined Types (UDTs): Create UDTs in Oracle with multiple new designers. A powerful UDT Custom Class code generation wizard makes using UDTs from .NET code easy and fast. An application can be rapidly created that utilizes UDTs with almost no coding required.
NET Stored Procedure Deployment: The .NET Deployment Wizard makes it easy to deploy .NET stored procedures and functions into Oracle Database.
Data Editing, Stored Procedure Testing, Adhoc SQL Execution: When testing your .NET application you can use the Oracle Data Window to insert and update Oracle data. There's also a testbed for testing stored procedures and an Oracle Query Window for executing any SQL statement you choose.
Integrated Online Help System: The integrated context sensitive online help, including the Oracle SQL and PL/SQL Users Guides puts the Oracle documentation at your fingertips.
Import Table Wizard: This new wizard makes it easy to move tables and their data from external datasources such as Microsoft SQL Server, Microsoft Access and Excel spreadsheets into Oracle Database.
Follow the link for details ....
http://www.oracle.com/technology/tech/dotnet/tools/index.html
Saturday, February 21, 2009
WebServices for Beginers
Those who just want to start of with WebServices , these step by step tutorial by Gopalan Suresh Raj are good reading for them
Building a Web Service Component using C# and .NET
Building a Web Service Client using C# and .NET
http://gsraj.tripod.com/dotnet/webservices/webservice_server.html
Building a Web Service Component using C# and .NET
Building a Web Service Client using C# and .NET
http://gsraj.tripod.com/dotnet/webservices/webservice_server.html
Subscribe to:
Posts (Atom)