Hans | zevenseas | SharePoint Blog

SharePoint, IE7/8 and active scripting.

Hans Blaauw — Tue, 07 Oct 2008 13:43:40 GMT

How small problems can be so annoying.

I must confess, I hate fooling around with Windows installations nowadays :-) For two days I had a problem and of course it was very simple to solve. Suddenly on one day my SharePoint sites gave all kinds of Javascript errors and I couldn’t understand what happened suddenly. I tried a lot and sure I understood it was a client side problem. Even tried running regsvr32 jscript.dll but no luck the first time I tried that.

And then suddenly, oh stupid me!!! Yes I needed to run regsvr32 jscript.dll as and administrator (which I thought I was).

The biggest questions of course how this could happen suddenly. I really don’t know unfortunately :-(

Launch of SharePoint Marketplace

Hans Blaauw — Mon, 06 Oct 2008 14:07:17 GMT

Last week we launched the SharePoint Marketplace. It is our initiative to provide a local store for our customers and prospects.

The goal is to provide a very extensive catalog of free and paid tools in an easy to use format. Because we want to promote sharing we encourage developers but also customers to provide us with tools, templates, webparts and whitepapers that we can put in the store.

If you have developed something you can send an e-mail to marketplace@online.zevenseas.com with the product attached and a description of what it does.

SharePoint quick wins for the late majority conservatives

Hans Blaauw — Mon, 06 Oct 2008 12:19:39 GMT

When you want to turn conservatives into believers you need quick wins because you probably have one chance. A few quick wins that I came up with in projects is:

Document version control;
Use of META information instead of folders;
Full search like Google (kind of);
Possibility to get alerted when information is changed (push model from an end users perspective);
Meeting spaces;
Outlook connection or Shared contacts;
Freedom to create your own smart lists or even replace some old file system based simple spreadsheets.

For each of these quick wins people will reply to you. Below some of the replies:

I have document versioning, I always save my documents under a different file/version name.

Folders are my META information and I have a very advanced system that I build up in the last couple of years.

That is cool!

Interesting but I don't get it.

That is a handy feature because we have a lot of meetings.

We have all our contacts somewhere else.

I like Excel a lot.

The point is that you need to go out and talk to people about what they want. Just deploying SharePoint and doing nothing afterwards is a big mistake because people don't always get it that easy. You need to supply them with scenario's and how to solve problems with SharePoint. It can be a tough challenge!

SharePoint RPC protocol

Hans Blaauw — Mon, 06 Oct 2008 10:23:52 GMT

SharePoint has different protocols that you can use to do interesting things. One is the RPC protocol. Nowadays we are used to web 2.0 applications where we can popup information fast without leaving the current screen. SharePoint has none of this out of the box but with the RPC protocol we can do a trick to make it possible.

The result will be a very simple screen as shown below (no customization):

As you can see it has no theme attached so best would be to use this with a modal overlay like I explained in an earlier post. The URL to do this is:

_vti_bin/owssvr.dll?dialogview=FileOpen&location=Shared%20Documents

Interesting SharePoint features/solutions for Content Owners

Hans Blaauw — Mon, 06 Oct 2008 09:27:57 GMT

Content owners (people that publish information for others) are always looking for ways to target information more specific to certain groups of people or even let different people have different interfaces or default views. Out of the box SharePoint does have some capabilities (audience) but it can be improved.

There are two interesting features/solutions developed by Laurent Cotton that can improve this personalisation a lot:

The first one makes it possible to set default and availables views for different user groups:

The second one makes it possible to set advanced display, edit new rules on fields. That means that you can hide fields for certain groups when editing or viewing information.

This should have been in SharePoint right from the beginning on, it is awesome!

SharePoint and modal overlays

Hans Blaauw — Fri, 03 Oct 2008 14:20:03 GMT

A long time ago I built a small demo that used something called Greybox, a nice modal overlay that can show content. I just discovered a slicker and fast version called Clearbox.

Click here to open Google in a modal overlay. Cool, isn't it?

Oops, did not work now it works :-)

Pimp your SharePoint portal/pages!

Hans Blaauw — Fri, 03 Oct 2008 12:00:16 GMT

I know that many managers of SharePoint environments hate it but users love it, "Pimp your SharePoint".

For some reason a lot of users think that you need developers for pimping your SharePoint environment but that is not true at all, SharePoint is there for the end user (like Office) and "content is king" as we all know. So let's start pimping.

The number one tool for users it the content editor web part (yeah, don’t we all love it) and everyone with enough rights can use it. This web part can accept HTML and can be used to put interesting stuff on your website in a snap. There is one warning, sometimes your site can become slow if it embeds information from other sites.

What do we have to pimp:

Ustream.tv

Put a live broadcast on your site and stream from your cameras. You can embed it in the content editor webpart by using pasting the embed code in a content editor webpart.

Tokbox

Put live video calling in your site or better MySite to offer people video calling with you. Again, get the embed code and paste it in the content editor webpart.

Weather

Put a weather widget in your site.

Other widgets

You want to use hundreds of other widgets, move over to widgetbox.com.

Happy pimping and don't blame me if you get a call from your IT department :-)

SharePoint and licensing components, webservices etc.

Hans Blaauw — Thu, 02 Oct 2008 14:21:32 GMT

For a project that we are running I have done some investigation on how to protect developed work so that we can make a dime :-)

I always try to look for tools that offer the most complete solution, in this case that would be:

- Comprehensive Obfuscation features

- String Encryption

- Anti Tamper Protection

- Suppress ILDASM

- Strong Name Removal Protection

- IL Code Encryption

- Control Flow Obfuscation

- Invalid Metadata Injection

- License generator

- Key management

- Online activation services

- Different expiration/demo features

- Source code integration

- Payment gateway support

There are not many tools out there and the biggest questions also is which one supports SharePoint. Till now I found the following license protection systems that seem to be somewhat suitable:

- Intellilock

- .NET Reactor

- .NET Licensing Pro

- Infralution

- Manco .NET licensing

At first I thought that Intellilock would be a fit but it has no source code integration and it is not flexible enough to use. .NET Reactor is great to protect your developed stuff but again the licensing system isn’t great.

.NET Licensing Pro seems too complicated and the Manco license manager crashed.

For now it seems Infralution is a good way to protect components but I’m not sure if we can use it to protect for example webservices, I think we can.

ASP.NET, jQuery and SharePoint

Hans Blaauw — Thu, 02 Oct 2008 14:03:01 GMT

On the JQuery team blog we can find an announcement that both Microsoft and Nokia are going to add (and distribute) Jquery in some of their products, I think that is great news.

Microsoft starts to realise more and more that there are great folks out there (mostly open source) that invent fantastic stuff that is of use for others. I myself have been using Jquery for many things and it adds a lot of value to development projects.

I think that it will not take long before we can see SharePoint solutions that make use of the JQuery library.

SharePoint for endusers and content managers

Hans Blaauw — Wed, 01 Oct 2008 11:24:56 GMT

if you are a "normal" SharePoint user you should visit this site: http://www.endusersharepoint.com/, it is a great resource.

SharePoint and the adoption cycle

Hans Blaauw — Wed, 01 Oct 2008 10:40:48 GMT

A meeting with one of our US partners yesterday made me write this story about adoption cycle. One remark struck me “Europe lags in user adoption” with SharePoint. This was the one thing that our US partner noticed and in some way I agree. It seems that we focus a lot on the non-standard possibilities of SharePoint (as a development platform) and that we forget to teach our users how to use SharePoint. Teach? Yes, we need to teach because a lot of users complain about SharePoint that it is a geeky and non-standard interface.

This brings me to a presentation that I saw in Seattle, Bob Sutton talked about user adoption and how important it is to reach critical mass in your organization. I noticed this a few times in projects, end users struggle with standard out of the box SharePoint already and organizations ignore that and build new stuff all the time. Let me be clear, nothing against new SharePoint solutions but you shouldn’t ignore end users. My personal feeling sometimes is that developers have taken over the platform as a new playground for their applications. But SharePoint is more, besides a platform it is collaboration and publishing solution already and as anyone knows nowadays “content is king”.

A solution is a vehicle for the information that we want to transfer to a user.

If we look at User Adoption we can use the Adoption Cycle from “Crossing the Chasm”.

We can use this if we introduce SharePoint in an organization; it gives us a tool to calculate how much people (early adopters) we need to promote the product. The magic number is 5. Maybe you noticed it on the internet but 5 is a popular number:

· Refer 5 friends and get a free account;

· Hi5;

· Etc.

The first phase of the Adoption Cycle consists of 2,5% innovators/technology enthusiasts, these are the people that try SharePoint in a sandbox or even signup at a hosting company for a free account. In a large company you need 5 of them on 200 users. In every company you have innovators.

In the second phase we need to seek for 13,5% early adopters/visionaries. They are the so called “sneezers”, they spread the SharePoint virus. It is best to search for people with high level communication skills and influence in the company because that makes a quality “sneeze”. Later on we call this group of people “super users” because they are the SharePoint specialists.

After these two phases you are crossing the chasm, this is a very difficult phase in the adoption of SharePoint because you need to move from the technical interested group to the pragmatists. They only use SharePoint as a tool to do their daily work, if something isn’t like they are used to they will “bash” on the product and start spreading a “cold” instead of a simple “sneeze”. 35% of your users consist of pragmatists and you need them to move to the tougher group, if you succeed you have 50% of the end users being “believers” and you can start selling to the other 50%.

The next 34% is the late majority conservatives group, this is a tough group. They need to be convinced that SharePoint is a better solution for them to use. This group has a healthy view on changes and they need arguments why to use it. You need to feed them with time saving ideas and quick wins.

The last phase is the 16% laggards and skeptics. Don’t’ worry too much, this group is skeptical towards every application and you just need to be more convincing. Give these people more attention and try to find quality quick wins. Use you early adaptors to visit this group and talk about SharePoint, don’t force them!

SharePoint and mobiles, bad marriage?

Hans Blaauw — Wed, 24 Sep 2008 10:37:54 GMT

Isn't it weird that Microsoft owns two big platforms, Windows Mobile and SharePoint, and that is has such a non-existing strategy for using these two together. If you do a search on SharePoint and mobiles there is not much to find, I think that is weird.

Business users have mobile data plans everywhere but they still heavily rely on Exchange and sync. for delivering corporate data to the mobile workers. Not sure if I understand why that is.

SharePoint has all the corporate data available and nowadays this is all accessible from home, so why has nobody showed me a cool SharePoint mobile app. lately (or what about ever)?

I think there are a few reasons:

- The mobile browsing experience of SharePoint isn’t that great;

- Exchange is a tough competitor.

Both are true and I think we should not focus on a SharePoint browser experience although the new browsers (like the iPhone) could make it easier to show SharePoint content in a more decent way.

Exchange is indeed the de-facto standard for Microsoft customers but I start questioning it because SharePoint contains more valuable corporate information compared to Exchange.
E-mail shouldn’t be your only tool to run a business.

I think SharePoint is ready for it with its extensive webservices to do anything you can imagine and we only need more native Windows Mobile applications. We should dump the /m browsing experience of SharePoint because it sucks.

We could have some quick wins with SharePoint and a mobile app:

- Integrate sim card contact lists with remote SharePoint contact lists (possible through your data plan);

- Start workflows on your device;

- Add contacts from your sim card to a SharePoint portal or the other way around;

- Publish Twitter style messages from your mobile to a SharePoint portal;

- Track your mobile workers by storing GPS information and maps in the portal.

This isn’t rocket science and can all be done by using the webservices and some very lightweight native Windows Mobile applications. Who is up to it?

And for the people that don’t believe in downloadable apps for devices (yes Daniel you too), see the latest iPhone stats J

It took 74 days to sell the first million iPhones in 2007.

Then, on July 11, 2008, Apple launched the App Store, and everything changed.

- Three days to sell 1 million iPhones.

- Three days to download 10 million applications.

- Eleven days to download 25 million apps.

- 60 million applications downloaded in the first month.

- $360 million in applications sold to date, even though the majority of downloads come from free apps.

Potentially a $1 billion marketplace in the next 24 months.

Sure, consumers but my big guess is that the iPhone will empower a lot of business users.

Microsoft's data center for Microsoft online services goes online today

Hans Blaauw — Mon, 22 Sep 2008 14:48:27 GMT

The new most advanced data center of Microsoft is a 470,000-square-foot building that cost $550 mil. and it is located in San Antonio.

(source picture: InformationWeek)

So if anyone thinks that Microsoft isn't serious about online services visit this data center :-) After finishing the Quincy data center in Washington Microsoft has not stopped building data centers and there are even plans for a facility in Siberia.

Probably big parts of the capacity of these data centers will be used by the Microsoft Online Services (Exchange, SharePoint, Office livemeeting). In Seattle they talked about hosted SharePoint for even 100000 users and for that you need massive capacity.

Below is a screenshot of the architecture:

Wondering how rapidly Microsoft can sell big companies hosted SharePoint?

A new tool to use for designing SharePoint solutions

Hans Blaauw — Tue, 09 Sep 2008 18:40:01 GMT

It often happens during meeting with potential customers that they or we write down stuff to explain what users want. We use several tools to do this but there is a new solution just around the corner and it is called LiveScribe.

This is an incredible smart pen that can record pen movements and voice, these can be played back with what they call Paper Replay.

For me this sounds like a good tool for anyone that needs to sit down with customers to make notes and replay them later.

Back with a post on QR codes

Hans Blaauw — Tue, 09 Sep 2008 18:31:55 GMT

What?

A QR Code is a matrix code (or two-dimensional bar code) created by Japanese corporation Denso-Wave in 1994. The "QR" is derived from "Quick Response", as the creator intended the code to allow its contents to be decoded at high speed. QR Codes are huge in Japan where they are currently the most popular type of two dimensional codes. Below you see a QR code for our site http://www.zevenseas.com By using a QR code scanner, for mobile phone or webcam, you can easily browse to our site by scanning below code.

In Japan everyone uses QR codes to include in magazines, id cards, mobile tickets, billboards etc. Nokia delivers a qr code scanner on most phones in Japan.

You can imagine a scenario where mobile ticketing is used. Someone purchases an event ticket and gets the QR code on his phone to access the booth. At the entrance a scanner will read the QR code on the mobile phone screen and the visitor has access, voila!

What is the link with SharePoint?

Well, I thought it would be interesting to use a standard SharePoint link list to generate and show a QR code. For that I have created:

a list template with some extra fields;
a dataview webpart that shows the QR code.

To make it happen you need to do install this file in your list template gallery and this file into your webpart gallery. When you create a list based on the list template be sure to name it Links with QR code. Place the webpart in your site and it will work.

All this magic happens by using the Google Charts API, a very simple but great API!

SharePoint and Google Chrome, it works!

Hans Blaauw — Wed, 03 Sep 2008 00:11:24 GMT

Just tested the new Google Chrome webbrowser and I must say I like it because it is simple and it works with SharePoint without a problem.

Download it here

Some SharePoint Designer videos

Hans Blaauw — Thu, 24 Jul 2008 09:48:36 GMT

I came across a few interesting videos from the SharePointGuys:

	Custom Publishing Page Layouts in SharePoint Designer 2007
	Creating Publishing Page Layouts in SharePoint Designer 2007
	Using the CSS Task Panes in SharePoint Designer 2007
	Modifying Style Sheets in SharePoint Designer 2007
	Create a Cascading Style Sheet in SharePoint Designer 2007
	Managing Master Pages in SharePoint Designer 2007

Mockups vs the real thing

Hans Blaauw — Wed, 23 Jul 2008 13:04:31 GMT

As long as I can remember I have always been looking for a tool to quickly visualize what I think. Mostly because of the screen mockups that people needed to get the idea. Nowadays I rather just build the interface in SharePoint directly because basically that is what they get when it is finished. No complicated interaction designs on paper (where is the interaction, never understood that) because what you see is what you get in SharePoint. Or, what you want is what you don't get :-) What I mean is that SharePoint out of the box has an interaction interface. The way how you upload documents or add items is determined by Microsoft and that is how we should use it. Yes I know that sounds bad but even web 2.0 apps. all have their own interfaces and some are good and some are bad. So don't bother to create stunning interaction designs just on paper because it does not make much sense except in the situation that you want a public facing site with a completely different interface. But in that situation, pick a good tool!

When talking about mockups vs the real thing there are a few things to keep in mind:

The real thing needs expectation management, people tend to think a solution is finished when they see a operational SharePoint demo;
Mockups aren't really interactive when done on paper;
You need to have some drawing skills to do it on paper, not every designer is an artist;
Paper is sometimes faster because everyone can do basic drawing (we learn it on school when younger);
On paper you cannot run simulations or do mouse clicks to go to another screen;
Some people have a terrible handwriting (like me).

I prefer digital tools to do mockups and my favorites are listed below.

Create a mockup

Just very recently I discovered two very good tools to do mockups or even simulations:

Serena Prototype Composer;
Balsamiq mockups.

Serena Prototype Composer

For me this is the tool to use because it features process design, activity design and many more options you need. It even has version control and I have managed to hook it up to a SharePoint document library so that I can store projects directly on a collaboration site. Other people that have the desktop designer can open the project and see what I have done.

The simulation and demonstration part is great and you can build advanced demos that you can show on screen. Besides that it can create documentation in Word.

The Serena tool is very handy because you can capture the screens that you created in SharePoint, by using point and click, and use them in the composer as interface models.

Balsamiq mockups

What I like about this tool is that it uses hand drawn interface components but it lacks other important things like simulation.

Pick your favorite :-)

My new role as SharePoint Solution Designer

Hans Blaauw — Tue, 22 Jul 2008 13:29:37 GMT

Part 1:

For almost 10 years I have always called myself a Functional Designer but because of my SharePoint specialisation it is time to change this role name to a more suitable one, I present you "SharePoint Solution Designer".

Below I will explain the fine details of this role.

SharePoint Solution Designer - SSD in short

In current and past projects I noticed that several companies skip one step when hiring people, they start with developers and forget to add people that safeguard the overall design. Potentially that can end in disaster. Developers are great and creative people (see our team) but sometimes they tend to focus on a few issues only. In a project it is important that the broader scope is guarded and that the first vision of what the product should do remains intact. You know how it works, problems distract people from the original goal and you could end up in a lost focus situation.

A SSD is a diehard SharePoint specialist with multiple years of experience with end users and the business. In most cases he is the trusted man for a SharePoint project leader (together with an architect) and he supports the project with all SharePoint related solution issues. That said, he is also the main designer of the SharePoint solution. In some ways he is a traditional functional designer but because of SharePoint he designs a lot in realtime (does not mean that he doesn't document).

Skill set

A SSD has the following skills:

SharePoint front end specialist (not a Central Administration specialist);
Focus on what the users need;
SharePoint designer (webservices and DataView webpart);
Integration specialist;
Good verbal communication;
Sense for business;
Strong personality and a product vision guard;
Management capabilities;
Knowledge of features and solutions.

So how does this SSD approach a project?

First of all he needs to setup communication lines with the business, sponsors and project leader. Communication is essential because an SSD needs to grasp what people want and how they want it. During the conversations the SSD will try to collect as much user stories as possible to get a good understanding of the requested functionality. Later on these requests will be translated to real SharePoint solutions (out of the box or developed). Based on all this information he will build a very compact but clear document that transforms the user requests into a readable story. This document will be used as a starting point for the project. With this document the SSD and the project leader can make an estimate for time and budget. In this phase he also starts talking to an architect to see if the architecture limits proposed functionality.

My normal approach is to split up functionality into two blocks:

out-of-the-box
custom made

This is really important because for custom made you need real developers. Out of the box can be done by either the SSD (only a prototype) or junior developers.

Out of the box

The next step depends on the company and how they work. In some cases you need to build a complete functional design document but I prefer a POC in a real (test) SharePoint environment. Again, documentation is still needed. The SSD could start building a POC but in bigger projects he probably hands it over to another SSD or junior developer. The prototype is mainly used to showcase the discussed functionality. Be aware, because SharePoint is a fast point and click environment users tend to think that a solution is already finished, make sure you communicate this! The prototype will not contain any special made webparts in the first phase. In many organisations a prototype releases more budget because people get enthusiastic about what they see.

After the presentation of the POC it is really time to sit down and to process the feedback.

Custom made

Because SharePoint uses webparts (smallest building blocks) it is already possible to start building the basic foundation for all webparts. Things like:

logo for the site- and site collection feature list;
namespace and naming conventions;
configuration;
installer;
source control.

In the earlier mentioned document the SSD has defined the custom made components (probably webparts). These need to be defined in either a technical design or a more detailed functional design. A good developer can build based on a very detailed functional design. We want a developer to use his own brains too, don't we?

Documentation

There is a simple reason why I build a POC first, it has to do with the screen mockups. A real SharePoint environment is really the fastest way to build the needed mockups. But, right after that the documentation and process and activity design should start. A process is how information flows and a activity is one part of a process. Nowadays I use a tool called Serena Prototype Composer.

As a SSD I build all the diagrams and documentation for the whole solution.

Managing development

While there should be a lead developer in all projects a SSD can help out with managing the developers. They need to be managed because they sometimes tend to add non-requested features (creative blokes) or lose focus. A SSD keeps an eye on the overall progress and requested features.

to be continued...

SharePoint boolean search

Hans Blaauw — Fri, 11 Jul 2008 14:14:58 GMT

For a customer I was looking into custom search results and I really was not aware of how to do it, yeah yeah...

So below you see a custom search result and in the search box some stuff to search for. The Microsoft site says:

The search service interprets the space between terms that use different properties as an AND. For example, if you look for firstname:Ben lastname:"Smith", your search will return results for "Ben Smith," and for any other name that begins with "Ben", for example "Benjamin".

The search service interprets the space between terms that use the same property as an OR. For example, if the author property is available for content searches, and you search for author:"Ben Smith" author:"David Jones", the search results will show any item created by either person.

To exclude people from your search results, place a minus sign (-) before the name of an identifying property. For example, appending -firstname:"Ben" to your query excludes anyone with the first name "Ben" from your search results.

The biggest problem of course is that end users will have difficulties with that so it is probably best to build a special searchbox that makes it easier. Will investigate to see if someone has done it before.

Customizing SharePoint people search the easy way

Hans Blaauw — Tue, 08 Jul 2008 20:26:50 GMT

I hate digging through XLS stuff and customizing the search looked like a pain to me. But thanks to this guy's post I can customize fast and with a high quality. A bloody shame that the penny didn't drop before to use SP Designer for this. His presentation started me thinking and I just did some customizations, see below screenshot. This is all done by just replacing the XLS stylesheet.

Read his presentation but make sure you do this first:

create two Enterprise Search Centers (tabbed).

Use one Search Center to get the raw code and use the other Search center to test your XLS.

Some ideas I have are:

linking a profile Longitude and Latitude field to a Google Static map;
Skype call and chat button;
Conditional formatting;
Add a Youtube profile video.

This is great stuff!

Using Google Charts in SharePoint

Hans Blaauw — Sun, 06 Jul 2008 10:50:32 GMT

In SharePoint you have some possibilities to use KPI's but I'm not really blown away by how you can display this data. The Google Chart API can help out. In below screenshot you can see how I used it on a simple list:

There is a Gauge in a DataView webpart to show a value. Before you can use the webpart I provided you have to change a few things in the webpart XML. Open the .webpart file and search for:

DefaultValue="KPIData" Name="ListName"

Change KPIData to the name of your list and do that in the whole file and save it. Next add a column to your list called Value and use the type Number. Now you are ready to upload the the .webpart to your gallery.

You can now place the webpart on your site/page and you will see that the gauge takes the value of the Value field.

Note: Of course your site also needs an internet connection to use the Google Chart API.

SharePoint content deployment and far beyond that with RepliWeb Operational Synchronization

Hans Blaauw — Thu, 03 Jul 2008 12:50:22 GMT

I have had the honor this morning to watch a demo of ROSS (see title for explanation) and my first response is WOW. It is truly replication for sites and smaller pieces of content and I have never seen it before. Every organization that has a content/solutions deployment problem in a DTAP environment should investigate this product. Click here for the features.

Coming months we will investigate this product further and we will try to get customers involved in a early adopter program.

SharePoint usability

Hans Blaauw — Wed, 02 Jul 2008 21:43:17 GMT

Last week I attended a small party in Amsterdam to meet freelancers and a bunch of very good designers. It was a nice party but a few people from the design business started a discussion with me why the SharePoint interface is so bloody difficult to use. Let's be clear, they did not mean ugly just difficult to use.

This is not the first time I hear this and I must confess I don't like it too. In the projects I did, many people struggled with the SP interface. I guess that is because of the fact that they are used to Office and they expect something similar from Microsoft. Some people will say "train them" but I think that shouldn't be necessary. We don't train them for Web 2.0 stuff, do we? Overall it seems people favor the Web 2.0 apps.

This is probably not my last post on this because it is really an issue.

P.S. And yes there is a mill on the background :-)

Show SharePoint list fields based on certain conditions

Hans Blaauw — Wed, 02 Jul 2008 21:33:23 GMT

Codeplex has a wealth of information and tools/features and one I like is the conditional display of fields in the new, edit and display forms. Luckily a smart guy has started developing such a feature.

I think the idea is awesome because sometimes you only want to present fields to certain groups or users. This feature makes that possible.

Jump to the project and download it. I did not test it yet but I will do very soon.