Brief overview of some of the new features coming up with SharePoint v3:
- List item security
- Recycle Bin (user and admin level)
- Workflow! (using Windows Workflow Foundation)
- Other data source lookup columns
- UI improvements like better menu’s treeviews and configurable options
- RSS support
- (Custom) ContentTypes
- MasterPages (ASP.Net 2.0)
- Improved Definition structure
- Two-way Outlook integration
- Eventhandlers in every list
- Version history in every list
- Minor and major versioning
- Security on versions
- Email to lists
- Different authentication methods per domain (url)
Scott Woodgate and team – Announcing Windows Workflow Foundation
At the PDC Microsoft announced Windows Workflow Foundation. Here Scott Woodgate and team (Abhay Parasnis and Paul Andrew) demonstrate the power of the new Workflow Foundation. It’s all about business process.
It’s pretty interesting and is going to change how developers will be able to build systems to track and enable workflow services.
Very good presentation, a little long but interesting.
Asp.Net Atlas Forum
ASP.NET “Atlas” is a package of new Web development technologies that integrates an extensive set of client script libraries with the rich, server-based development platform of ASP.NET 2.0. “Atlas” enables you to develop Web applications that can update data on a Web page by making direct calls to a Web server — without needing to round trip the page. With “Atlas”, you can take advantage of the best of ASP.NET and server-side code while doing much of the work in the browser, enabling a richer user experience.
ASP.NET “Atlas” includes:
- Client script libraries that provide a complete solution for creating client-based Web applications. The client script libraries support object-oriented development, cross-browser compatibility, asynchronous calls to Web services, and behaviors and components for creating a full-featured UI.
- Web server controls that provide a declarative way to emit markup and client script for “Atlas” features.
- Web services, such as ASP.NET profiles, that can add useful server-side features to an “Atlas” application.
These application templates are tailored to address the needs and requirements for specific business processes or sets of tasks for organizations of any size. The applications are the first out-of-box custom scenarios for the Windows SharePoint Services platform, though they also provide a starting point for partners and developers looking to build deeper Windows SharePoint Services solutions.
Whe you have and error in Sharepoint that says that a Web Part or Web Form Control on this Web Part Page cannot be displayed.
You have to remove the Web Part thats causing the error.
In order to do this, simply append “?contents=1” to the URL of the page, for example http://myportal/myarea/default.aspx?contents=1, and you will have a Sharepoint Web Part Page Maintenance where you can remove the Web Part that is causing the error.
Personalize Your Portal with User Controls and Custom Web Parts
ASP.NET 2.0 comes with a built-in portal framework that brings two significant benefits to the table. First, it dramatically reduces the investment for building ASP.NET portal solutions. Second, it provides a consistent model for building ASP.NET-based portals.
|Web Part Primer
A page that is designed to host Web Parts is known as a Web Part Page. A Web Part Page requires exactly one instance of the WebPartManager control and one or more WebPartZone controls, as shown in the figure. A Web Part Page may optionally include an EditorZone or CatalogZone control. Note that the tag for the WebPartManager control must be placed in an .aspx file before the tags for any of the other controls associated with the Web Part infrastructure, such as WebPartZone, EditorZone, and CatalogZone. For better control over the layout and appearance of the Web Part Page, you can also lay out the different zones within the .aspx file by using HTML tables.
string hexString = txtHex.Text;
txtByteCount.Text = ((int)HexEncoding.GetByteCount(hexString)).ToString();
txtLength.Text = hexString.Length.ToString();
byte byteArray = HexEncoding.GetBytes(hexString, out discarded);