- Business Data Catalog Read/Write – Screencast
- Open with Windows Explorer not working in Document Library for WSS or MOSS
- Using the Business Data Catalog with Single Sign-On
- The BIG SharePoint Resource List
- Enhancing teaching and learning with SharePoint in Higher Education
- SharePoint Learning Kit: Part 2
- SharePoint 2007 – Calculated Fields
- MOSS + ECM or ECM = MOSS
- New Release of BDC Metaman!
- All the upgrades – except the one people seem to need the most
- Using workflow and policies to view only certain list items
- Mirroring, Log Shipping and High Availability resources
- SharePoint Installation/Configuration Guides
- Shortcuts in Document Libraries
- Using Delegate Controls as WebParts
- Article series – custom permissions with a site definition
- Meaningful conceptual mappings between entities for SharePoint programining/administration
- Sync Your Database to SharePoint Using SSIS – Discover how to import and export SharePoint list items using SQL Server Integration Services and the new Collaborative Application Markup Language (CAML).
- Thank you for a banner year for SharePoint! - from Tom Rizzo
Archive for July, 2007
Posted by Steve Pietrek on July 28, 2007
Below is a list of steps to turn off SharePoint custom error messages so you can see the “true” ASP.NET error message along with the callstack/stack trace. I would recommend only making the following changes in a development environment – not production.
- Navigate to the site directory.
- Backup web.config.
- Open web.config.
- Switch Custom Errors off. Search for “customErrors” and set the value to “Off” instead of “On”. You can also set the value to “RemoteOnly” to troubleshoot a production issue.
- Enable CallStack. Search for “CallStack” and set the value to “true” instead of “false”.
- Save web.config.
Posted by Steve Pietrek on July 22, 2007
For the past 13 years I have been working on a Business Intelligence product sold mostly to manufacturing companies world-wide. Originally the tool we used was Forest & Trees; however, spending too much time dealing with its shortcomings as a lesser development tool we switched to Delphi 1 a few months after it was released. What a great decision that was!
With the advent of .NET and C#, I realized it was important to update my skills so for the past 3.5 years I have been learning .NET in my spare time. The main reason for my original blog was to track interesting posts on mostly .NET so I could go back and search on them at a later time. Things changed however at last year’s DevConnections conference. I sat in on many SharePoint presentations and was instantly smitten with SharePoint. For the past 9 months, I have been reading up and messing around with SharePoint. I created a separate SharePoint-specific blog earlier this year to keep track of interesting SharePoint links.