192 replies
by rlbogue
OK, I give up. I keep getting asked if I have a blog. I get asked at work, at community events, and even in personal interations. So I give up. This represents the first entry in my new blog.
On a more positive note, as I've been thinking about what I would put on my blog, I've come up with some of the following ideas...
- Stuff I want to remember and be able to search for (so I'm selfish)
- Stuff that I can't get a publisher to pay for
- Personal updates that aren't appropriate for articles
I'll probably also post links to articles as they come up ... at least as I think about it just in case you want to see all I'm writing.
by rlbogue
I'm out at SharePoint Advisor Live!. It's good to get to talk to the other speakers to learn about how they're using SharePoint in their worlds and talking to the attendees to learn about their challenges. A few of the highlights from the day...
- Echo for SharePoint (www.winapptechnologies.com) - A winform based application to migrate lists and web part pages from one site to another. Currently only works on the local server (meaning they're using the SP API). No command line yet -- so it won't fit into automated deployments. It does, however, manage to get past some of the issues that the two migration utilities that I'm working on are still having.
- ParallelSpace (www.parallelspace.com) - Content migration utilities and security assessment utilities for SharePoint.
- Microsoft/Domino connection (www.msdomino.net) - Allows for Domino/Notes to be shown in SharePoint. Not clear on how it all works yet, the demo wasn't fully functional yesterday when I went by but it's definitely interesting.
There were some interesting conversations about off-line clients and rich clients for SharePoint. Mostly the idea that Access might be a front end to SharePoint. Specifically the thought of adding relationships to SharePoint list data was discussed.
by rlbogue
I've always avoided front page like the plague. In part due to the fact that I don't want to unghost my pages but also in part because I just dislike the tool. However, that's changed...
The ability to create data view web parts and more importantly to convert list view web parts into dataview web parts (with a simple right click I might add) is very cool. Add the list view web part to your page, right click in front page to convert to a dataviewweb part and you're done.
Of course using front page will unghost the page you're working with -- however, you can always export the DWP file and use it other places.
Another useful tool...
Rob
by rlbogue
I've been doing a series at developer.com which describes each of the roles in the software development process -- the latest article on the role of a developer has posted.
http://www.developer.com/java/other/article.php/3511566
by rlbogue
So, at Crowe we run Lotus Notes. (I hate Lotus Notes.) Sorry, it's an automatic response.
Anyway, I wanted to export my contacts to sync with my Exchange infrastructure here at the home office. No problem. Notes will export to vCards. Ok, there is a problem. Notes exports to one huge vCard file with multiple vCards. Outlook only recognizes files with one vCard. The net result is that you can only import the first record in the Notes vCard export.
So I wrote a utility which bursts a single vCard file into multiple vCard files so you can double click the ones you want and add them to outlook. It's really quick and fairly slick.
I'm working on getting a license created that I can use to distribute free stuff like this, but in the mean time send me an email if you need a copy of the utility (or the code). I'll send it to you if you email me. The standard disclaimers apply... I wrote it for me, it may or may not work for you.
by rlbogue
[Note: I wrote this a year ago, mainly as therapy for the frustration. I thought it might be interesting for others to see. Since the event of more than a year ago things have substantially improved and I like my service except for the occaisional quirk. I'm just glad I don't have to work through problems every day. --rlb]
No Service: Painful Portability
The plane lands and turns onto the taxi way. The flight attendants politely but firmly let you know that you should sit in your seat until the aircraft comes to a complete stop and the pilot turns off the fasten seatbelt sign. Then she informs you that cellular phones can now be used.
You turn on your phone to the startup tone. You look down at the signal bar. No signal. You try to check your voice mail and receive a message of no service. You look out the window and confirm you are in a large city. Looking back down again you realize that this is more than just some added delay in getting the phone to wake up.
The Saga Begins
A situation quite similar happened to me recently. I landed in Seattle, WA which is just about as far from my home in Indianapolis, IN as you can get without leaving the continental United States. Although concerned, I felt comfortable that this was just a minor glitch that could be easily resolved. I made it to the hotel, missing the opportunity to call my wife and let her know that I landed safely before she went to bed.
I picked up the phone at the hotel to call Cingular, the wireless carrier I had switched to only three weeks before hand. I was greeted with a prompt that told me that customer service was closed, but there was, luckily, an after hours support number.
After a brief interaction, and a technical support person who couldn’t locate the problem I was told to turn the phone off until the morning and things would probably work themselves out.
Broken from the Start
Three weeks prior when trying to activate the service I learned to be somewhat skeptical as I went through a week and a half of trying to get things working. I ordered the phone from TeleSales and activated service for two lines. One for my wife and the other to support my needs. I decided to port my telephone number from Sprint PCS to Cingular in no small part so I could see how bad portability really was. Sometimes writers have to do things that they know are wrong so they can remind others not to do it – or so I’ve been told by my similarly masochistic friends.
Things were broken from the start as my wife’s phone arrived on time two days after I ordered it but mine was nowhere to be found. A phone call or two later I was told that the phone hadn’t shipped because they were waiting on the portability department to OK the phone’s shipment. Over the course of the next few phone calls and countless hours wasted I realized that the process for shipping new service on a ported phone was completely insane since Telesales was waiting on portability. Portability was waiting on me to have the device so they could activate it in the system.
When two more days passed and I still hadn’t seen the device I called back in only to find out that TeleSales couldn’t track the phone. However, they were able to finally confirm that the phone shipped – a day after it was supposed to. By the time the phone arrived it was nearly a full week later. The device was ordered on a Saturday and arrived the Friday following. When I called in to activate the phone they couldn’t get the system to take it. They explained that something was wrong but they’d put in a ticket which might take two business days to get an answer to.
On a whim I called back on Monday and received an activation for the phone. While on the phone I made a quick outbound call. Success! At least that’s what I thought until I went to call the phone back and setup my voicemail. Neither one of them worked.
Another call back and a few more wasted hours got me no where. Over the next two days I logged literally hours on the phone trying to get someone who would resolve the problem. The first day I was told that the phone wasn’t “fully” in the system and that I’d have to wait until Tuesday. Tuesday came without voice mail or inbound calls.
I finally found a supervisor willing to commit to resolving my issues. A few hours later I had inbound calls. A few more calls from me finally got my voice mailbox setup correctly since apparently the device wasn’t setup right before it was shipped and there were some other configuration issues with the phone.
For the time after these problems and before my journey to Seattle all was well. I was enjoying the extended coverage area and service.
Disaster is in the Air
When the next morning of my Seattle trip came I still had no service. When I called back in I was told that they couldn’t see the device and would have to put a roaming ticket in and that those took two to three days to resolve. I was also told that it was most likely an equipment problem and that the phone should be looked at.
Over the next three days I wasted three or so hours trying to get them to identify a store that I could go into to get a resolution. It seems that the multi-mode (GSM/TDMA) phones that I had weren’t popular in the area so none of the local stores sold them or could diagnose them. The store which was less than a block from the convention center where I was going to be was useless because they didn’t have the ability to resolve the issue.
I was offered the ability to order a new device from TeleSales – which couldn’t send devices any faster than two day air and I already had experience with them not shipping the same day. Ultimately this meant that I’d be on my way home before a replacement device could get to me.
The end result was four days in Seattle without the cellular coverage I was paying for.
What’s wrong with this picture?
Perhaps the most frustrating part of the whole situation was the fact that there weren’t any quick solutions to the problems I was sharing. Everything was a two or three day wait. Every solution was presented with the caveat that it probably wouldn’t fix my problem.
Each solution that I presented was met unceremoniously with a reason why it wouldn’t work. They couldn’t reprogram the SIM card in my phone because I wasn’t in my home market. They couldn’t get me a SIM card with a Seattle local number because I didn’t live in Seattle and Indiana and Seattle use different billing systems.
It’s just too bad I can’t live without my cell phone.
by rlbogue
I've not yet had a chance to test ... I was wondering if the SQL Sniping script -- designed to kill blocking threads -- could be used to kill off the leftovers from a bad SPSBackup session so that the next backup could run successfully. The SQL sniping script can be found at http://www.integer.org ... I'll have to try it the next time SPSBackup decides to not close down correctly.
by rlbogue
So one of the things that I truly despise about debugging is working for a few hours trying to make something work only to find out later that it isn't that thing that's broken at all... Case in point. I was getting a Access denied type message while trying to write something to the registry. I thought it was code access security -- because that's normally what it is. It turned out to be that I forgot to ask for write access when I opened up the key... ARG!
Now I'm off chasing some enumerator problem from a base class...
by fritzler
A user calls with a possible problem on report output. I take a look at the code, and the rules of how the program is supposed to act is thoroughly UNdocumented. So I track down the programmer who wrote that code and he doesn't remember the rules. Okay. Half the time I don't remember why I coded something the way I did from a week ago. Anwyay, I go back to the user and ask them how they really expect the program to work...and they aren't sure either!! So is there something to fix or not? lol
by rlbogue
If you've been wondering what I've been up to, I've been in Alaska doing some work during the day and playing during the evenings.
It's been fun but it's meant that some of my technical issues (like the one around enumeration class casting, are sitting on a back burner.)
by rlbogue
Since coming to Alaska I've learned a lot about Glaciers. Yesterday's excursion was the Phillips 26 Glacier Cruse. It was very good, although I wish I would have seen some whales.
Here's what I did see!

by beth blakely
by jaqui
there be whales!!
north end vancouver island
there be OZ!!!
lower mainland ( Vancouver itself ) there be me.
by rlbogue
No single off-the-shelf system will exactly meet all of your organizational needs. The trick is finding the set of solutions that meet your organization's needs and that work well with each system within that set of solutions.
by rlbogue
The deployment role is one that is critically important to the initial impression of the software being delivered. A bad installation experience can sour just about anyone's taste. Because of this the role of the deployment professional is increasing.
http://www.developer.com/java/ent/article.php/3519186
by rlbogue
While working with a client yesterday we were discussing the idea of having email (or parts of your email) as a window in SharePoint. They were discussing how the limited space made things difficult while simultaneously discussing how it was important to have a one stop experience for the portal. Then the comment came up that one member of the group always started their day with email.
A light bulb went off. You can set an HTML (web) page as the default view for a folder in outlook. Simply right click the folder, select properties, select the Home Page tab, enter your URL, Click the 'Show home page by default for this folder' checkbox and click OK. Now whenever you click on the folder the web page appears.
Now they can decide whether they want Outlook housing SharePoint or SharePoint housing email via Outlook Web Access. While on that note. Send me an email if you'ld like to beta some utilities that are like the 'My Inbox', 'My Calendar', and 'My Tasks' web parts in SPS. I have written a set which don't require the user name to be set in properties so they can be deployed on a shared view. I'd like to get some testing done on them.
by rlbogue
I broke down today and bought Anti-Virus software for the primary computer that I use. I've had anti-virus software on customer computers, my son's computer, and my wife's computer. The reason I didn't have it on the computer that I work on is because I think it's an unnecessary evil. If you're suspicious and careful you should be able to avoid infection by a virus. OK, so I hedged my bets and occaisionally ran Trend Micro's House Call solution. Still, I didn't feel like it was necessary software -- and supporting an industry which has caused so many hours of problems with software that blocks things in unexpected ways has never been high on my list.
However, I realize that in today's environment, the only way for corporations to protect themselves is to ensure that the laptops connecting to their network have current anti-virus software and that the definitions are up to date. The goal being, of course, to provide some measure of assurance that the computer isn't infected.
So, I've joined the masses in using Anti-Virus software. Even if I don't like the whole concept.
-rlb
by rlbogue
I broke down today and bought Anti-Virus software for the primary computer that I use.? I've had anti-virus software on customer computers, my son's computer, and my wife's computer.? The reason I didn't have it on the computer that I work on is because I think it's an unnecessary evil.? If you're suspicious and careful you should be able to avoid infection by a virus.? OK, so I hedged my bets and occaisionally ran Trend Micro's House Call solution. Still, I didn't feel like it was necessary software -- and supporting an industry which has caused so many hours of problems with software that blocks things in unexpected ways has never been high on my list.
However, I realize that in today's environment, the only way for corporations to protect themselves is to ensure that the laptops connecting to their network have current anti-virus software and that the definitions are up to date.? The goal being, of course, to provide some measure of assurance that the computer isn't infected.
So, I've joined the masses in using Anti-Virus software.? Even if I don't like the whole concept.
-rlb
by rlbogue
I saw a sign that every parent has dreamed of...
Maybe they weren't talking about that kind of wake.
by rlbogue
I've got a series of web part packs and utilities of various sorts that I have on my radar to release in the next few months. As I'm getting geared up for that, I'd like to see if anyone would be interested in doing some beta testing. Here's what's on the plate short term...
- SharePoint URL Management - If you let your users enter URLs on your SharePoint sites then you know that they can and do link EVERYWHERE. The point of the URL management utility is to first, identify where users are linking to -- in every URL field in every list in every site in a site collection. The links are organized by server by URL and finally by where they are used from. The second feature of the application is to do wholesale replacements of URLs and parts of URLs. So you can change the server that a URL points to, the path of the page, or even everything about the URL including any querystring parameters provided.
- Exchange Web Parts - SharePoint Portal Server offers some basic Exchange Outlook Web Access web parts. From my perspective they have two fundamental flaws. First, they can't be used in Windows SharePoint Services. Second, they require that the user personalize the web part properties. This web part pack won't need the users to personalize the properties to be able to use it. Thus it doesn't require personalization at all. The web parts figure out who the user is based on their login name.
- Site Properties Pack - Site properties in SharePoint are very powerful. They are a quick way to provide some “state“ information about the site which can be used to connect to other applications. The site properties pack will contain a web part to visually display and modify site properties, a content editor web part which will take content and display it while doing property substitutions, and a list display web part that allows for display of a list with property substitutions in the URLs. Together they are a toolkit to get you started with working with site properties for integration.
There are more applications to come but these are the ones that I'm to the point of writing documentation for.
by rlbogue
While working with a client recently we were discussing the issues with the Exchange web parts that are shipped as a part of SPS. (This spawned the development on the new Exchange web parts, see my previous post.)
However, we came to the conclusion that it might be too small to include some email items in SharePoint. So I mentioned the idea of doing things the reverse way. Use Outlook to host your SharePoint site. It's a feature that's been around in Outlook for a while. All you have to do is...
- Create a folder in Outlook.
- Right click, select properties.
- Click the home page tab.
- Enter the address of your SharePoint site in the address text box.
- Select the show home page by default for this folder checkbox
- Click the OK button.
Now when you navigate to this folder in Outlook you'll see your SharePoint site. Not a bad deal when you're looking to have a single dashboard to the organization and you live in email -- as many of us do.
by rlbogue
Bil Simser posted on a problem with CAML where he mentioned reverse engineering the internal field name to the original display name that created it. I had to do just this thing for one of migration utilities. Here's the code (C#):
// Fixup an internal name back to the regular way that it should be so that we can get the same
// internal name back when we create a title.
private static string FixInternalName(string internalName)
{
// Get the most common one out of the way as quickly as possible
string f1 = internalName.Replace("_x0020_", " ");
int pos;
// while we have more processing to do
while ((pos = f1.IndexOf("_")) >= 0)
{
int chrVal;
if (pos + 6 > f1.Length)
{
chrVal = PartialEncoding(f1,pos);
}
else
{
chrVal = int.Parse(f1.Substring(pos+2, 4), System.Globalization.NumberStyles.HexNumber);
}
if (f1.Length > pos + 7)
{
// char isn't at the end of the string
f1 = f1.Substring(0, pos) + Convert.ToChar(chrVal) + f1.Substring(pos+7);
}
else
{
f1 = f1.Substring(0, pos) + Convert.ToChar(chrVal);
}
}
return (f1);
}
private static char PartialEncoding(string fix, int pos)
{
pos += "_x".Length;
if (fix.Length > pos)
{
string nw = String.Empty;
while(pos < fix.Length)
{
nw = nw + fix[pos];
pos++;
}
while(nw.Length < 4)
{
nw = nw + '0';
}
return (Convert.ToChar(int.Parse(nw, System.Globalization.NumberStyles.HexNumber)));
}
else
{
// Not even enough to start -- return a space it will get encoded
return ' ';
}
}
by rlbogue
As an organization begins to assimilate more and more servers, a reliable backup strategy becomes more challenging. Instead of one tape drive that backs up the entire network, libraries become necessary. Instead of doing one backup job and schedule, you need several. Here are four fundamentals for developing your backup strategy.
https://www.techrepublic.com.com/5100-9592-5797990.html
by rlbogue
I've been working on a basic rules based web service for InfoPath forms. The basic idea is to allow us to do “poor man's integration.” to some back end systems now and then swap that out later without modifying the forms -- since the forms will be adapted by several people and there may be more forms than we want to go back through. So a single web service that all InfoPath forms call on submission -- by the way one they call in addition to whatever else they want to do -- for instance, post themselves to a SharePoint site.
Anyway, so I needed a rules section in the config file where each rule had some attributes. The problem is that .NET isn't setup to easily hand you back the XML from a section in the configuration file -- actually it gets pretty upset about the section even being in the file. The solution is a IConfigurationSectionHandler. Here's what it takes to implement...
1) Modify the web.config file.
a) Add a <configSections> tag. Note this must be the first tag in the <configuration> node. This looks something like...
<configSections>
<sectionGroup name="customConfig">
<section name="rules" type="InfoPathRouting.Classes.XMLConfigurationSectionHandler, infopathrouting" />
</sectionGroup>
</configSections>In this case, I'm creating a new section called customConfig and adding a section in it called rules, which my class (InfoPathRouting.Classes.XMLConfigurationSectionHandler) in my DLL will handle. (InfoPathRouting is the ASP.NET project name)
b) Add the actual section in the file. In this case I'd add something like:
<customConfig>
<rules>
<!-- Whatever I want in here -->
</rules>
2) Add the class to the project. Here's the XMLConfigurationSectionHandler that I wrote. The only restriction is that it must support the IConfigurationSectionHandler interface. That interface only defines one method, Create().
using
System;
using System.Configuration;
using System.Xml;
namespace InfoPathRouting.Classes
{
public class XMLConfigurationSectionHandler : IConfigurationSectionHandler
{
public object Create(object parent, object configContext, XmlNode section)
{
return (section);
}
}
}
In this case I wanted the XMLNode back so I could do my own thing with the XML fragment, so that's what I returned.
3) Reference the configuration section in your code. The following line of code fetches the XMLNode for my new rules section:
XmlNode rules = (XmlNode) System.Configuration.ConfigurationSettings.GetConfig("customConfig/rules");
That's it. I now have a repeatable way to store any kind of XML configuration I want in my app.config and web.config files.
by rlbogue
Today I was forced to read some code for a developer that I loathe. Just when I believe I've seen every stupid thing you can do with code I am surprised by a new structure that he repeats everywhere through his code. Here's what I saw today...
string myString = (GetStringFromConfiguration(”keyvalue”) + “”).ToLower();
At first I did a double take, it doesn't make sense to add an empty string to a string ... that is unless you're trying to prevent the null reference exception from ToLower(). Adding null to any string results in that string. Thus, you *CAN* work around null references by using this technique. However, here is why you shouldn't.
When you do this you actually force the CLR to create an extra, unnecessary new string object. It creates a temporary string object which it concatenates the result of the function and the empty string into. Another string is created when the string is taken ToLower(). That one can't be helped, but the intervening one -- the one caused by the concatenation, can be eliminated.
OK, sure, it's a detail and it probably won't matter much to most people but it will perform slower, require more memory, etc. The biggest thing for me is that it's really odd from a readability/understandability perspective. (Did I mention that there are no comments in this code?)
Ideally, I'd create a GetStringFromConfiguration function overload that took a second parameter of what I wanted back if the entry wasn't in the configuration file. That way the code doesn't concern itself with the details, it knows that it will always get back a valid string. This is in fact what I do when I have to be concerned about getting back a null when I need it to be functionally equivelent of a default or an empty string.
As a sidebar, it would have been nice to see a String.Empty instead of ““ ... oh well, you can't win them all.
by rlbogue
In my previous post I highlighted a single bad idea that I had seen in some code. I want to offer up a few other things that I saw and why you shouldn't do them...
- Tightly nested Try/Catch blocks -- basically, put a try block, do one statement, add a try block in that block and repeat... See the code...
static public void LogRequestResult(string url, string status)
{
try
{
FileStream objFileStream = null;
StreamWriter objStreamWriter = null;
try
{
objFileStream = File.Open(cnstMyFilePath, FileMode.Append, FileAccess.Write, FileShare.Read);
try
{
objStreamWriter = new StreamWriter(objFileStream);
lock(objStreamWriter)
{
objStreamWriter.Write(Status + url);
}
}
finally
{
if (objStreamWriter != null) objStreamWriter.Close();
}
}
finally
{
if (objFileStream != null) objFileStream.Close();
}
}
catch
{
}
}
Ignoring the fact that we're not actually doing any error checking... Isn't the following much more straightforward easier to read, and less prone to errors? The moral to the story, try/catch blocks are cool but don't abuse them.
static public void LogRequestResult(string url, string status)
{
FileStream objFileStream = null;
StreamWriter objStreamWriter = null;
try
{
objFileStream = File.Open(cnstMyFilePath, FileMode.Append, FileAccess.Write, FileShare.Read);
objStreamWriter = new StreamWriter(objFileStream);
lock(objStreamWriter)
{
objStreamWriter.Write(Status + url);
}
}
finally
{
if (objStreamWriter != null) objFileStream.Close();
if (objFileStream != null) objFileStream.Close();
}
}
- Magic Numbers (or in this case letters), just stop -- I can't tell you how many times I'm looking through code and I come across an if statement that looks like “if myvariable == “A““ Why in the world would your variable is “A“. What does “A“ mean? In .NET we have enumerations and constants. Why can't we just them? I have no idea what “A“ means -- and neither will the author 2 months from now. If you put quotes around the same text twice it should be a constant. If you use a number for an if statement or as part of an assignment that isn't a 0 or a 1, you should have a constant. (Zero is a number to compare against, 1 is a number to fix a number of offset issues.)
- Comments -- Hey, there's a concept. And I don't mean one that says, // the following line adds one to the number. Thanks. I can read code. How about writing comments that tell me why you're adding one to the number? Oh, yea, those XML comment things that .NET supports. Those are useful. You can use them too, they're not expensive.
Do you have any pet peves about code that should go on this list?
by rlbogue
I was looking for how to perform a mail merge using a SharePoint list as a source and found Wayne's post asking the same question. There wasn't help there, however, amongst the comment was on from Yatin Purohit indicating that you could link to the SharePoint list as a table in Access and then use the Access table as a source for Word to use in a mail merge. It's a pretty useful technique -- too bad there's not an OLEDB driver for SharePoint lists. I suppose this will work for now.
by rlbogue
I finished a new web part kit over the weekend. It is called Link Tracking, and allows you to see how frequently that users are actually using the links that are in the portal. Most customers I've talked to are completely unaware of when the users are using the links on the portal, as a result it's hard to fine-tune the number and type of links on the site.
Link tracking fixes this by recording each link as it's clicked so you can go back and review the number of people who have used the link.
I'm looking for three beta participants with the commercial release being later this month. If selected for the beta, I'll give you a license to the final code when it comes out.
Rob
by rlbogue
I was speaking with Todd Bleeker who is still very excited about the possibilities of the Content Editor web part. Then I went to a client who was having a typical problem -- making it easy to find people in their organization.
The net result was that I created a web part that leverages the Content Editor web part to use the REST format of the search page to find people. I've made the dwp available here for those who might be able to use it. I'm starting to see why Todd likes this approach. It's good for some simple things that you want to get done without a lot of coding.
by rlbogue
One of the annoying things for me has been trying to get a web part that would show a random item from a list. I've wanted to feature projects, employees, questions/answer sets, etc. on the home page to keep it new without having to finely control what data was exposed on the home page.
I've completed the coding for a Random Item web part which takes a random item from a list and displays it using the formatting that the user/developer provides. It has the ability to support previous and next buttons as well as the ability to cache the results for a period of time so that the entire page isn't in a constant state of flux.
I've still got to finish the documentation and create a few example DWPs, but I'm looking for folks who are interested in beta testing the web part and letting me know what additional features it needs.
by rlbogue
I'm working on an article for IntranetJournal about the way that SharePoint actually uses meta data (fields) in a document library and as I was crawling through the details it occurred to me one of the reasons why SharePoint has to create a new version when you update the properties of the file. Many people have wondered why this causes a new version to be created -- including myself. However, I believe that I've stumbled across the answer -- Because it *IS* a new version in some cases.
In the case of Office documents, the document itself gets updated to reflect the new properties. You can see for yourself by checking File-Properties-File Properties on the file.
It's also storing the previous properties off if you needed to restore them, even if there is no way to see them. (It's not just recreating them from the properties in the document because it has the behavior of restoring the properties even for non-Office documents.)
by rlbogue
This is an old link, but one I seem to need from time-to-time. It's the MS document that explains (compares) what various versions of office can do with SharePoint.
by rlbogue
SharePoint's support for REST (query string parameters) on the search.aspx (Portal Server Search/Search Results Page) is very powerful. However, once you get past the basics of passing it a search string (k ... short for keywords) the documentation gets a bit fuzzy. Here's one thing that I was able to do with search.aspx...
First, a few parameters...
| Parameter | Description |
|---|---|
| k | Keywords - General Search |
| tp | Type of document (I've found Person and Document very handy.) |
| s | Scope -- Think Search Scopes from the search drop-down list |
| pt | Property -- Any of the custom properties that SharePoint indexes. IFilters put these in. |
| d | Date -- apparently required when you're searching for properties |
So the next bit is how to encode the properties. Here are a few ASCII/Hex Codes you may need
| Code | Punctuation |
|---|---|
| %3a | : (Colon) |
| %2e | . (Period) |
| %23 | # (Hash, Pound, etc.) |
| %2c | , (Comma)<.TD> |
So if you want to search for the word 'spacey' in any text in a document in a search scope nammed fuzzy you would have a URL like: http://server/search.aspx?tp=Document&s=fuzzy&k=spacey
It gets a tad bit more complicated when you want to search only in a property not in the full text. First, you have to find the property you want in Manage Properties, and then you have to setup the search ... When you add the property to the search you have to add a single character specifier indicating the type of the property before you start it's name -- mostly you're dealing with Strings so 'S' is appropriate. Then you have to put commas after the property name the keyword Contains and another comma -- all encoded of course. Next, once I search for a property I have to add a date specifier to the query. The title property is really urn:schemas.microsoft.com:fulltextquery.displaytitle. So if I wanted to find the same thing in only the title property I'd do this: http://server/search.aspx?tp=Document&s=fuzzy&pt=Surn%3aschemas%2emicrosoft%2ecom%3afulltextqueryinfo%3adisplaytitle%2cContains%2cSpacey&2cAnd%2c&d=All
Clear as mud right? It's not that bad, basically describing the property and url encoding all of the special characters makes it look ugly. If it weren't encoded it would look like this..http://server/scope.aspx?tp=Document&s=fuzzy&pt=Surn:schemas.microsoft.com:fulltextqueryinfo:displaytitle,Contains,Spacey,And,&d=All still not pretty but certainly much more readable.
I hope this helps when you want to be able to create links to property searches.
by rlbogue
Something I ran across the other day is that the default content index for Portal Content has an exclusion in it so that it won't search the actual pages of the Portal. If you have content editor web parts, or other content that you want to make sure that SharePoint does index, you'll want to go into SharePoint and remove the exclusion for pages. You can follow these steps to remove the exclusion
- Open the SharePoint Portal Server site
- Click on Site Settings
- Click Configure search and indexing
- Click Manage Content Indexes
- Hover over Portal Content, drop down the menu arrow that appears on the right, and select Edit.
- Click Manage rules to exclude and include content
- Find the entry in the list which is http://yourserver/*.aspx, hover over it, drop down the menu arrow that appears on the right, and select Delete.
The next time the portal content index is refreshed you'll start getting content from the web part pages as well.
by rlbogue
As some of you know, I write a weekly newsletter for Tech Republic -- Strategies that Scale. That newsletter is targeted towards IT managers of small and mid-sized organizations. The goal is to provide useful information that helps them grow their IT organization, and their organization as a whole.
I'm looking for your input for future topics. It can be a topic that you see done wrong all the time and want someone to write about the correct (or a correct) way of doing it. It can be something that you've seen someone do very successfully. I can even be something that you struggle with or that you've learned how to do. The doors are open, I'd love to hear what you have to say.
You can respond here via comment, or you can send me an email directly (rob[dot]bogue[at]thorprojects[dot]com)
by rlbogue
Another one of those lovely SharePoint error messages ... This one leaves me wondering what I do when it doesn't work the second time I try it.? (Or the hundredth since I'm getting it back from code running against the API.)
... I've got to get my library of least favorite SharePoint error messages up.
If anyone's interested this one came up when trying to get SPWeb from SPSite.OpenWeb with a GUID ... that is valid.
Rob
by rlbogue
It is possible to believe that there is nothing left to be done. That all of the roles outlined thus far is all that is needed to make the process work. However, the role of the development manager is critical to the long-term success of the software development team. The role that the development manager plays - particularly when interacting with the project manager - is essential to a continuously improving process. (If you've not been following the series, you might want to read Cracking the Code: Breaking Down the Software Development Roles.)
Read more of the article at http://www.developer.com/java/ent/article.php/3529081
[Author's Note: I really enjoyed the mental exercise that writing this series brought. It was a good way for me to clarify my thinking around the various roles in the software development process. I hope that it can provide a framework for understanding how people fit into the process in your organization. The next series is on Coding standards and starts in just a few weeks. I'm always happy to get input on what you think should or shouldn't be in coding standards.]
by rlbogue
The next time I see a requirements document which says they want “collaboration” my response is going to be to ask...
“Why do you want to cooperate treasonably with a foreign power?”
Maybe that will jar people into asking what they mean by collaboration. (Asking what they mean by collaboration doesn't seem to work in most cases.)
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
[Authors Note: There's a very interesting discussion brewing about what artifacts are good and what artifacts are bad. Check it out.]
https://www.techrepublic.com.com/5100-10878_11-5842424.html
by rlbogue
There are sometimes when your assembly almost has to be in the GAC and when you need to debug it. This was difficult since if you registered a .NET assembly into the GAC the debugger wouldn't break on it. This is because the .PDB file information didn't get loaded since it's not in the same directory as the DLL. Here's how to work around that.
1) Install the Assembly in the GAC
2) Start-Run, %SYSTEMROOT%\Assembly\GAC
3) Navigate into the folder with name of the DLL that you want to debug
4) Navigate into the folder with the version number and public key that you want
5) Copy the .PDB file into this directory
Now you'll be able to run a debugger against code running in the GAC.
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
A few weeks ago I posted on the IRuntimeFilter interface in SharePoint. Here are a few updates...
1) I've validated that IRuntimeFilter's CheckRuntimeRender() method is only called when the IsIncludedFilter property of a web part is non-null.
2) By default, Windows SharePoint Services will put administrators and web designers into a shared page view rather than in a my page view. The net effect is that the shared page isn't a personalized view and therefore IRuntimeFilter's CheckRuntimeRender() method isn't called. To fix this create a new site definition and add the following tag into the <HEAD> tag. <META name=”WebPartPageDefaultViewPersonal”> Then make sure you do an IISReset so it can take effect. (You'll have to create a new site to see this.)
3) ValidateRuntimeFilter() is called everytime the web part is serialized -- which is often. So keep the code that you write in this method very simple.
4) If you decide to do post backs in the chooser form that you create, you'll need to add a tag to the <HEAD> tag. That tag is <base target=”_self”> If you don't do this then the form will cause a new window to open.
My next step is to fix some impersonation issues with roles (the ones that Michael Donovan mentioned to in his post. From there, I'll be writing a IRuntimeFilter chain to allow the Portal audiences IRuntimeFilter to run side-by-site with our own IRuntimeFilter.
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Mike Donovan's post got me interested in how IRuntimeFilter could be used to replicate SharePoint Portal Server audience/targeting feature in Windows SharePoint Services. There are several situations I've run into where the SPS targeting is a compelling feature for Portal Server but the limitation of 10,000 areas was a problem. (By way of reference, I also found Serge van den Oever's reverse engineering of the interface which was very good.)
In thinking about the interface it also seemed promising as a potential way to secure web parts. In other words, with an IRuntimeFilter running you could potentially turn off web parts for certain groups of users. This might be effective at preventing them from seeing our using web parts from the gallery that some users needed but weren't suitable for everyone.
However, the actual implementation of the interface appears to have a few challenges. (I have a case open with MS PSS right now to verify some of these observations. I'll update this blog entry or more likely add a new one when I get more information.)
1) The filter is only called when the IsIncludedFilter property in the web part has a non-empty (non-null value.) In other words, you don't get the opportunity to inspect every web part as it's loaded, you only get to inspect those web parts with the property set. This makes it useful for user configuration but not very useful as a "traffic cop."
2) The interface doesn’t specify any information about the web part itself. It only returns to you a filter string that you presumably created with the user interface. The challenge with this is that there is no way (I've found) to determine just which web part is trying to be displayed. Again, maybe this isn't an issue for users configuring things for themselves, but it seems awfully limiting. One reason is because when a web part is exported and re-imported, the IsIncludedFilter property stays with it. That means that if you have site-specific data in the IsIncludedFilter property it becomes invalidated when it moves to the next site. This is a real problem when trying to move web parts between sites or punch out a template site. (The Microsoft provided ListViewWebPart andListFormWebPart both exhibit problems when you try to move them from one site to another due to this same fundamental issue of using site/area specific property values. This is why you are not allowed to export and import ListViewWebParts via the user interface.)
3) The ValidateIsIncludedFilter() method, which is called when the property is saved is called all the time. There's no event which fires when the user adds the web part or changes the configuration. This event fires every time the web part is saved. This appears to be happening on every page load – which is a bad thing in and of itself that I don't really understand. Why would we be saving a web part back to the database every time it's rendered? It seems to me that this would be a huge performance problem.
4) The IRuntimeFilter is only called in "personalization mode" The precise meaning of this eludes me – I can't find the definition in the documentation. However, based on observation it appears that it is only called in the personal view of the site. (This would be the view that few people actually see first, only those who have the permission to personalize the site and have done so default to a personal view of the site – almost everyone gets a shared view.) The net effect of this is that it's going to require some more work to force people into a personal view by default when they view a WSS page.
5) The IRuntimeFilter interface is only called for "global" web parts on a page. That means if the user adds a web part to their page while in personal mode the IRuntimeFilter will never control whether it is displayed or not.
As a sidebar, it appears that SPS enters personalization mode or the "my page" view by default since their IRuntimeFilter is turned on. I tried playing with this and observed that when I put a SharePoint Area into edit mode and then switched to personal view all of my menus disappeared. All I could do was return to Shared mode which would allow me to edit what web parts were on the page, etc. Based on these observations it looks like SPS is actually putting the area into a personal view every time the page is loaded but they also don't allow you to personalize the page.
So, I can probably replicate the SPS audiences using IRuntimeFilter if I can figure out how to force the WSS sites to default in personal view even for those without any personalization to the site.
However, without some way of inserting the web part storage key or some other value into the IsIncludedFilter property of a web part while it's being imported, I'm not sure how to make this interface any more useful than the SPS application of it. I've not found a way to inject properties to every web part as it's added yet…
Is anyone else playing with this interface?
by rlbogue
Two quick things ...
1) If you're trying to use XPath on XML you get back from SharePoint... don't forget you're going to need the XmlNamespaceManager object to use with SelectSingleNode or SelectNodes to get back what you're looking for. I repeatedly forget that SharePoint uses XML Namespaces extensively... and that using SelectSingleNode and SelectNodes does require namespaces in the XPath. (Today was lesson #3.)
2) Bad error handling. You may find it interesting to note that the WebPartPages web services' GetWebPartProperties method doesn't seem to throw soap exceptions. I ran into my favorite “Cannot complete...” error again. However, it didn't show up immediately because rather than throwing a soap exception this particular method returns the error as a comment node -- rather than throwing an error. So you'll have to look for comments one level down from the root. (Sidebar: It doesn't look like this web service even works against SharePoint Portal Server areas. At least - I keep getting an error about XML namespaces -- back as a comment.)
by rlbogue
For those of you who have been asking ... I'm not going to the PDC. I had a decision to make -- admittedly a tough one. The MVP Summit is at the end of the month. I don't have enough slack in my schedule to do two events in one month. So, as much as I wanted to hear about SharePoint V3 as soon as possible ... I had to decide to go to the Redmond campus at the end of the month. It gives me a lot more opportunities to talk with the program managers -- in a slightly more intimate setting.
So, keep the blog entries about the PDC coming, I'll be reading them intently.
by rlbogue
I was searching out some things and ran across an old blog entry from Bil Simser talking about the limitations of using folders because of path length limitations. Here are a few observations from a recent client experience.
1) The path limitation is indeed 255 (or 256 characters). It's documented in some of the planning documents (and in a KB article as well if memory serves.)
2) The idea of using meta data to categorize information instead of folders has at least two limitations ...
a) WebDAV doesn't natively support the assignment of meta-data during a save operation. Therefore saving with applications which are not fully SharePoint aware is a bad experience. The documents end up in the “root” of the view since they have no data to categorize them.
b) Retreiving files without context from a SharePoint document library can be very difficult without the property information. Since the WebDAV File-Open dialog doesn't understand the meta data it can be frustrating to find the right document to email to someone when the file name doesn't contain all of the useful information. One solution around this particular problem is to use the free Outlook Power Tool for SharePoint from Winapp Technology. Of course, that doesn't solve the problem when you're trying to use a file from another application.
In general... Use meta data if you need the ability to reorganize the data in multiple hierarchies. Use folders to make it easy to use within non-SharePoint enabled applications.
As a sidebar, the experience on SharePoint with WebDAV is much better in Windows XP vs. Windows 2000. Every application I've tested has been able to save to SharePoint via WebDAV in Windows XP. The same applications have trouble with Windows 2000's support for WebDAV. XP also allows files to be dragged from one WebDAV folder to another where Windows 2000 does not.
by rlbogue
There has been a fair amount of talk lately about how any web part page in SharePoint -- including many pages like list pages that people don't think are web part pages -- can have the web parts manipulated by simply adding parameters to the query string. Those parameters cause the ToolPartPane to appear even if there was no administrative control on the page to cause it to appear.
This is true of the existing pages, but you can create your own site definition that doesn't allow users to use the user interface to modify the web part placement or even add new items to the web part zone. The WebPartZone class (and consequently the WebPartZone tag) support three interesting attributes/properties...
- AllowCustomization - Indicates whether customization is allowed or not.
- AllowPersonalization - Indicates whether personalization is allowed or not
- LockLayout - Indicates whether the layout of the zone is fixed -- and can not be edited.
Quick testing shows that AllowCustomization must be set to true and LockLayout must be set to false for SharePoint to even show the web part zone in design mode. Further investigation has shown that using the web services calls to modify web parts in the web part zone still seems to work -- and editing the page in front page including web part placement still seems to work as well. In other words, it's possible to prevent users from modifying web parts in special zones, like navigation, while retaining the ability to control web parts in these special zones via code.
Trending After Hours posts
Sort by Trending