Here is another article I wrote for the good people at SharePoint Briefing entitled “Finding Great SharePoint Talent”. The article tries to give some advice on how to find truly good and well-experienced people when you’re looking to expand your staff.
Here is a teaser:
</end>
Follow me on Twitter at http://www.twitter.com/pagalvin
I was on a server and running a boring site collection backup command with the Backup-SPSite powershell cmdlet and got the following error:
Backup-SPSite : Cannot find an SPSite object with Id or URL: … (full message below)
I’ve had issues with this server so it made me think that the server was sick or something. I switched over to good old stsadm and this time I got a different error:
This operation can be performed only on a computer that is joined to a server farm … (full message below)
Of course, it it on the farm and all that, but it did occur to me that I was logged in with my own account and I normally log in as a system account onto this server. I did that and the backup succeeded. What I find interesting is that the cmdlet gave me a security trimmed error message. That’s kind of neat but didn’t help me much :)
<end/>
Follow me on Twitter at http://www.twitter.com/pagalvin
Last summer, I created a “straight to jail” list for the refrigerator. #1 on the list is Lawrence O’Donnell (for inaccurate predictions), but that’s way beyond the scope of this blog :) Today, I’m adding Cisco’s VPN client to the list, and that’s in scope by a nose.
A bunch of years ago many of clients used Cisco VPN to enable remote access to their site. Back then, I created virtual PCs for each of these clients and installed Cisco on that? Why? Because Cisco locks your machine up so that you can’t even browse local network printers, let alone dangerous tools like Skype, Communicator and the “~” key. But, if you install it on a VM, your VM is locked down but not your host.
I’m reminded of those glory days today because I have to use a Cisco VPN client *again* and it locks me and I have to use it in a minute. I’d rather blog about how much Cisco VPN client deserves to be in jail rather than use it…
</end>
Follow me on Twitter at http://www.twitter.com/pagalvin
I’ll be speaking in Denver at the SharePoint Fest event on May. I’m going to discuss some common business and technical want-to-do’s in SharePoint Designer workflows and outline some patterns you can use to solve them.
There’s a lot of other very interesting stuff going on at the conference, so check it out: http://www.sharepointfest.com/Denver/
It’s not a free event and I have a discount code handy, so leave a comment or ping me and I’ll gladly give out.
</end>
Follow me on Twitter at http://www.twitter.com/pagalvin
I wrote up an article for www.sharepoint.briefing.com entitled “Implement a Global Pop-up Notification System.” This function was implemented for a community college to communicate school closings due to snow and so forth.
It uses a custom list, out of the box SharePoint web services and some jQuery to do the work.
Here’s a teaser:
Read the whole thing here: http://www.sharepointbriefing.com/features/article.php/3918471/Implement-a-Global-Pop-up-Notification-System.htm
</end>
Follow me on Twitter at http://www.twitter.com/pagalvin
I wanted to receive information from a Text Field filter in SharePoint 2010 into my custom web part. I tried using this MSDN article as a basis but the article is either broken or I’m just not following it correctly.
A little more searching turned up Mike Smith’s MSDN contribution here (http://social.msdn.microsoft.com/forums/en-us/sharepointdevelopment/thread/72F1732A-7F93-441E-8644-2E82BBB153D9).
There’s a lot of stuff out there on connectable web parts but Mike’s article is as simple as it gets.
</end>
Follow me on Twitter at http://www.twitter.com/pagalvin
I’ve been working to get my dev chops back and to that end, working on a hobby project that has the following bits:
I wanted to rename the name space of all the bits to “Nivlag” and I was getting hit up with the following error when I deployed the web part to my test environment:
A Web Part or Web Form Control on this Page cannot be displayed or imported. The type could not be found or it is not registered as safe.
This is a beginner’s problem but I thought I’d jot down a note on this anyway. I caused the error when I right-clicked on the default name space (which defaulted to the project name), selected Refactor and then Rename like so:
That did rename things in a bunch of places in the project, but it’s not enough. You also need to make several other adjustments:
1. Manually open up and edit a file, “ShaerPointProjectItem.spdata”. That an XML file that has a <SafeControls> section. The namespace rename function isn’t aware of this file for whatever reason, so you need to update the Namespace there manually.
2. Manually edit the .webpart file. For whatever reason, Visual Studio doesn’t change this reference either. Change the "<type>” node to reflect your changed namespace there.
3. Lastly, depending on how you refactored the namespace change, visual studio may have also updated the string that references your .ascx file here:
private const string _ascxPath = @"~/_CONTROLTEMPLATES ……
You may need to change that back. You’ll because you’ll get an error similar to the following when you try and add the web part to a web part zone on a page:
Server Error in ‘/’ Application.
The file ‘/_CONTROLTEMPLATES/Nivlag/VisualWebPart1/VisualWebPart1UserControl.ascx’ does not exist.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Web.HttpException: The file ‘/_CONTROLTEMPLATES/Nivlag/VisualWebPart1/VisualWebPart1UserControl.ascx’ does not exist.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Fix the reference there and you should be good to go.
4. Lastly, the actual ASCX file still had a reference (for me) to the old original namespace (the refactor/rename function didn’t fix this). You’ll know about this error when you try and add the web part to the page and get the following message:
Server Error in ‘/’ Application.
Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.
Parser Error Message: Could not load type ‘RenameNameSpace.VisualWebPart1.VisualWebPart1UserControl’.
Source Error:
Line 6: <%@ Import Namespace="Microsoft.SharePoint" %> Line 7: <%@ Register Tagprefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> Line 8: <%@ Control Language="C#" AutoEventWireup="true" CodeBehind="VisualWebPart1UserControl.ascx.cs" Inherits="RenameNameSpace.VisualWebPart1.VisualWebPart1UserControl" %>Source File: /_CONTROLTEMPLATES/RenameNameSpace/VisualWebPart1/VisualWebPart1UserControl.ascx Line: 8
Version Information: Microsoft .NET Framework Version:2.0.50727.4927; ASP.NET Version:2.0.50727.4927
Edit the .ascx file directly and fix the broken namespace.
At this point, I finally had a web part living in the namespace of my choosing.
</end>
Follow me on Twitter at http://www.twitter.com/pagalvin
