Enabling Anonymous Access in SharePoint isn’t just a matter of flipping a switch in IIS manager. Anonymous Access must be enabled in IIS and then configured in SharePoint. But there are also situations where this basic configuration isn’t sufficient. In this talk we’ll review how to enable and configure anonymous access for SharePoint web sites, lists, and libraries. Then we’ll turn our attention to strategies that can be used overcome specific problems with SharePoint anonymous access. We’ll demonstrate solutions and workarounds for questions like:
- How do you require authentication for some items while maintaining anonymous access for the rest?
- What content from a personal MySite can be accessed via anonymous access?
- How do you enable anonymous responses to a discussion list?
- Can BLOGS and Wiki sites be used in an anonymous access site collection?
The establishment of a new SharePoint Portal frequently involves the temporary or permanent migration of an existing ASP.NET application to the new SharePoint environment. There are at least four different ways that this can be accomplished. Choosing the correct method is a matter of balancing the amount of effort involved against the resulting functionality and performance. In this talk we’ll demonstrate the following four approaches and discuss the strengths and weaknesses of each approach.
- Using a Page Viewer web part to display the existing website from inside SharePoint.
- Configuring the ASP.NET website to run from a Virtual Directory inside the SharePoint Web Application
- Converting the existing ASP.NET web pages and code beside files to run inside a SharePoint web site.
- Refactoring the ASP.NET web site as a set of Web Parts in the SharePoint site.