Shawn Cicoria - Solution Architect, Craftsman and Artisan - INauseous() - Main Blog Here: www.Cicoria.com
WSS and MOSS related
Keith Dahlby has a good post on creating a fake SPContext. Here’s the link and the code NOTE: This is not production safe code – use at own risk… http://solutionizing.net/20... public static SPContext FakeSPContext(SPWeb contextWeb) { // Ensure HttpContext.Current if (HttpContext.Current == null) { HttpRequest request = new HttpRequest("", web.Url, ""); HttpContext.Current = new HttpContext(request, new HttpResponse(TextWriter.Nul... } // SPContext is based on SPControl.GetContextWeb(), ......
The question came up today if we could use an “app_offline.htm” file along with HTML in that file that would reference images. First, I wasn’t 100% sure if the app_offline.htm would work, but it sure did. Since it’s just the Asp.net hosting process that detects the file, it circumvents loading any HttpApplications (SharePoint) beyond just serving up the HTML content. The second question was about having something more than text, specifically <img> tags. So, since the HttpHandlers are taking ......
In WSS 3.0/MOSS 2007 we had to resort to things like HttpModules [1] for errors, access denied, or for 404 errors updating the WebApp properties [2] Well, in 2010, thanks to Andrew Connell for pointing this out, Todd Carter blogs about what we now have in SPS 2010 here: http://todd-carter.com/post... [1] http://blogs.msdn.com/ketaa... [2] http://blogs.msdn.com/jingm... ......
During an installation issue, a client followed the TechNet article (http://technet.microsoft.c... and those instructions are misleading. It indicates to copy the “web.config” to the Layouts directory – what if fails to specify is it should be the “layoutsweb.config” file instead. While following the article does get you passed the issue that brought you there in the first place, you eventually end up with issues on provisioned sites that reference anything in _layouts ......
This is a continuation from Deployment of Theme and Resource files Resource File Deployment (Resx) The second item was deploying Resource files to the App_GlobalResource directory present as a subdirectory under each IIS site for each SharePoint Web Application zone. Remember that you can have multiple IIS Sites for each “Logical” SharePoint Web Application. The other requirement we had was that each Web Application needed to have its own set of resource files and were to be deployed and scoped as ......
Recently, we had a deployment scenario where we needed to deploy a custom theme and some resource files (resx) to the Farm and the Web Application zones respectively. Theme Deployment via Feature / Timer Job For the first feature, deployment of a theme, we initially went down the path assuming that we could scope the feature at Farm, and SharePoint would call the FeatureInstalled method in our Feature Receiver. Unfortunately, this all worked in development on our single machine environments. When ......
This has bitten me a couple of times. This error surfaced yesterday when running a scripted install with psconfig.exe – the error that appears in the log is: LookupAccountName failed to get the SID for account <domain>\LONG AC NAME > 20 chars When setting up SharePoint, we usually have a bunch of service accounts that generally are setup by different teams that manage the Active Directory accounts – well, that’s how it should work, but that’s another story. Many times organizations will ......
The industry it moving towards identity standards, and with the recent release of Windows Identity Foundation (fka Geneva), and the beta of SharePoint 2010, it’s important to take a look at the direction of how identity is being normalized into a “service” within the SharePoint object model. With SPS 2010, the SPUser object is now a claims identity. Identity management has been normalized to a approach that internally uses an STS that takes all “provider” or external STS identities, then creates ......
Ok, I’ve been bitten twice in the past week on this. If you have InfoPath 2010 Beta installed and you’ve also got SharePoint 2007 running, at least with the latest SP2 and October CU, you run into an issue that surfaces in the logs as follows One or more types failed to load. Please refer to the upgrade log for more details When you pull that log apart, you’ll see that it’s attempting to load a few types such as Microsoft.Office.InfoPath.S... from assembly 'Microsoft.Office.InfoPath.... ......
Many times, your coding, etc. SharePoint features. You’ll code something up, deploy, activate, etc.
Using WSP builder, while a convenient tool, it also leaves some orphans around. It forcibly deletes the solution leaving any place it’s activate with some “broken features”.
Fortunately, there’s a tool to help you cleanup those orphans.
http://featureadmin.codeplex.com/
Full SharePoint Archive