Mein zweiter Blick galt natürlich L²P und der Frage, ob es eventuell Probleme mit Chrome gibt. Microsoft SharePoint und insbesondere L²P läuft auf den beiden Mainstream-Browser Internet Explorer und FireFox weitgehend problemlos, zumindest in den höheren Versionen ab IE 6 bzw. ab FF 2. Bei Opera und Safari gibt es schon eher mal Probleme, insbesondere beim HTML-Editor RadEditor von telerik, der in L²P eingebunden ist.

Mein erster Befund: Google Chrome hat keine Probleme mit L²P. Das Design ist wie gewünscht und alle Webparts und Menüs arbeiten korrekt. Und tatsächlich wirkt alles etwas schneller.

Allerdings macht auch hier der RadEditor Probleme: die Toolbar wird nicht richtig angezeigt. Gleiches gilt für den Wechsel zwischen Desgin- und HTML-Ansicht im Editor. Zwar scheinen die Menü-Buttons zu funktionieren. Aber man muss raten, wo man hinklicken soll.

Das Problem scheint allerdings auch schon bekannt zu sein, siehe den telerik Blog von Vladimir Milev. Aberich bin guter Dinge: der RadEditor ist mittlerweile so weit verbreitet und Google Chrome wird sicher auch schnell einen ordentlichen Marktanteil erreichen, so dass telerik nachziehen und den RadEditor in einem Update entsprechend kompatibel machen wird. Wir sind gespannt.

If you are getting an unauhtorized access exception even after using this block then the reason could be as follows:

While using this construct: You cannot use the objects available through the Microsoft.SharePoint.SPContext.Current property. That is because those objects were created in the security context of the current user.

So the best practice for using the SPSecurity.RunWithElevatedPrivileges is to get the SPSite/SPWeb objects using the SPContext.Current and then create the SPSite and SPWeb objects seperately. See the code below:

SPSite siteColl = SPContext.Current.Site;
SPWeb site = SPContext.Current.Web;
SPSecurity.RunWithElevatedPrivileges(delegate() {
  using (SPSite ElevatedsiteColl = new SPSite(siteColl.ID)) {
    using (SPWeb ElevatedSite = ElevatedsiteColl.OpenWeb(site.ID)) {
        //Code to execute
    }
  }
});

The following code is wrong:

SPSecurity.RunWithElevatedPrivileges(delegate() {
    SPSite siteColl =    SPContext.Current.Site;
    SPWeb site = SPContext.Current.Web;
 //Code to execute
});

This design is almost a mirror image of the first where it may not be necessary to have the TimeData repository locally where retrieval isn’t performed often but still available if need. The TimeData repository is now located at the disaster recovery facility so operational recovery is still an option should the primary site go down and Double-Take is still used to provide high availability to the DR facility.

Either of these solutions is perfectly acceptable to provide disaster recovery in combination with operational recovery and each will help eliminate the length of time associated with tape restorations. The decision will come down to where you want to have your TimeData repository and that will depend on couple of variables:

q  How often will you need to recover lost or corrupted files? If this is a regular and common occurrence in your environment then it may make sense to have the repository local. Otherwise having the repository at the disaster recovery facility add protection from a site failure and still provides the ability to retrieve lost files.

q  What type of data will need to be retrieved? If you are only restoring an e-mail or word document now and then that is fine to transmit over a WAN but if you have retrieve regular CAD or other large image files then it may make sense to also have the repository local and on the same LAN.

The other option that isn’t displayed in these diagrams is having Double-Take at both local and remote facilities to provide both High and Remote Availability while at the same time protecting the revisions of the server data for that additional operational recovery.

For more information Marc LaFlure, TimeData Product Manager, will be presenting an in-depth look on how to use TimeData for operational recover and how to reduce tape restoration for business critical servers. Register here for Sept 4^th webinar at 11am EST.

Imagine users from all over your organization walking up to Multi-Function Devices (MFDs or Copiers), and scanning their documents. Only they are using barcode separator/cover sheets. How do they work? Well, the sheet can serve two purposes: separation and data. The separation function allows you to take a stack of 10 documents, put the separator sheets between each, and then scan the whole stack. The software finds the separator sheets and knows when one document begins and another ends. The data in the barcode can also be read, and populated into columns within the SharePoint application. An example?

Take this paragraph:

"Early on in his life as a midshipman at the Naval Academy, the most important lesson John McCain learned was that to sustain his self-respect for a lifetime it would be necessary for him to have the honor of serving something greater than his self-interest -- service to his country. John McCain has always put his country's interests before any party, special interest and even his own self-interest. He has always and will always do what is right for our country."

I know, I know, a technology BLOG is no place for political innuendo...sorry. ; )  Needed a quick paragraph and the covention was on.

Now take this barcode:

The entire barcode is the paragraph above encoded.  It can be read, and entered into a column in SharePoint.  Now this is an extreme example, but these 2D barcodes allow over 1000 characters in a thumbnail sized symbol.  Barcode generators will also allow a separation character, so you can embed multiple pieces of data for different columns within the symbol.  So think of the possibilities...

Each user assigned to a project within SharePoint could have their own cover sheet that has their name, project, location embeded.  All they need to do is scan their documents with the cover sheet on top, and the next thing they know, their paper document is on the SharePoint site with their name attached, and all the fields filled in.

No, not science fiction and very affordable.  Their are several applications that support this function, most notably, PSIGEN products and Kofax products.  Some good additional info on ScanGuru.

Podéis encontrar más información del proyecto CSP en la propia página de Codeplex y en los siguientes enlaces:

• http://www.microsoft.com/csp.
• http://www.citizenserviceplatform.com.
• http://www.microsoftpsdemos.com, dónde podréis encontrar una serie de demos para el sector público.
• Este post de Pedro Serrano en el que me enteré de la noticia.

Como muestra de uso de las tecnologías comentadas, podéis echar un vistazo a las plantillas de Agenda Management que utilizan MOSS.

It turns out the fix is not too difficult and I wanted to repost here.

1. Open up FireFox
2. Type about:config in the address bar
3. Locate the key named network.automatic-ntlm-auth.trusted-uris.
4. Set that key’s value to a comma separated list of servers you want NTLM auth for

This was posted on various blogs but wanted to point this out as the client couldn't seem to locate themselves.

Note: This is not a problem for those clients using Kerberos

For a browser that is developed from scratch (I don’t see any point in that by the way!), it has some wonderful capabilities – drag tabs between windows, improved security against phishing and malware, improved features for developers, pop ups to appear in the tab it originated from and much more.

The problem started, however when I opened our SharePoint intranet site. Given below is the list of issues I noticed in the few minutes of testing:

·         Minor formatting issues. Some of the tables where out of formatting.

·         The drop down menus for the top navigation appeared hidden behind the embedded images on the page. I think it has something to do with how IE use z indexing on IE 6.

·         You cannot edit a document in Microsoft word, excel etc (right click on a document and edit in Microsoft word). Error Message: “Edit document requires a windows SharePoint services compatible application and Microsoft internet explorer 6 or greater”.

·         Drag and drop does not work in the edit page view.

·         Silver light web parts do not work. I think silverlight does not support this browser yet.

I am sure there might be more issues noticed by others. I am not suggesting anyone to use chrome for sharepoint in my organization.

I went to the InfoPath class offered by SharePoint Solutions. It was three days long and covered InfoPath, SharePoint, and Workflows. The instructor was very nice and knowledgeable. I have a much better understanding of how to use IP to create forms and even mimic applications. I really thingk that IP will become a primary means for my group to create small apps, as most of the apps we build are just web versions of print forms. The savings in development time will be huge. I will post more as I remember-still have hurricane brain fog ;)

PRESENTER:
Andrew Connell
MVP Office SP Server
www.andrewconnell.com/blog

SILVERLIGHT OVERVIEW

Silverlight develops a rich user experience with zero postback

Some types of data Silverlight can provide:

• images, sounds, videos, rss
• custom web service
• existing intranet services
• public internet mashup APIs

HISTORY OF SILVERLIGHT

Silverlight 1.0:

• Silverlight 1.0 is the current production release (RTW) and was shipped in Q3 2007
• It defines the render(design) part using XAML
• Uses a WPF-based interface
• A Silverlight application lives inside of a webpage
• The webpage will include some custom JavaScript (AJAX) to talk to the Silverlight app and to the various web services.  I.E., the code-behind is 100% JavaScript-driven

Silverlight 2.0:

• Today: Silverlight 2.0 is in beta.  It doesn't need JavaScript to talk to Silverlight
• The Silverlight plugin deploys a tiny version into the .NET Framework, and now I can write C# or VB code and then complie the code into an asembly, and now the assembly will be part of the Silverlight file (control) and the assembly will be running on the client machine.  I.E., the code-behind uses managed code
• Some of Silverlight 2.0 runtime features include 2-D, graphics, audio, video, animations, text, controls, layout, styles/templates, data binding, networking, .NET Support, LIN1, XML API's, generics, HTML integrtions, local storage, Crypto APIs, and threading

Silverlight 2.0 SDK libraries include:

• Full support for dynamic languages
• Addition controls like sliders, grid controls
• LINQ for XML
• XML Serialization
• RSS feeds

SHAREPOINT AND SILVERLIGHT

Environment needed:

• WSS 3.0 SP1
• Config of IIS Web app

Server config needed:

• .NET Framework 3.5 if using Silverlight 2.0, or .NET 2.0 for Silverlight 1.0
• Deploy System.Web.Silverlight.dll in GAC
• Extend web.config if ISS web app with ASP.NET extensions and SL 2.0 config elements
• MIME type registration of the .XAP file extension for IIS web app (format: application/x-silverlight-2-b1

Dev environment needed:

• Visual Studio 2008 extended with tools for Silverlight 2.0
• Microsoft Expression Blend
• Silverlight 2.0 SDK (which would be included in VS 2008 tools)

Client prerequisites: Silverlight 2.0 plug-in must be installed

Scenarios for using Silverlight:

• Complex and dynamic interaction with dashboard data (visually impressive reports, etc)
• Visualize multimedia data stored in SP
• Rich navigation controls
• Interactive field types, Web parts, and pages
• Off-load more work to the clients (browsers)

SILVERLIGHT 2.0 AND SHAREPOINT

Host containers that can be used to trigger a Silverlight control:

• Web Parts
• App pages and site pages
• Custom field types
• Navigation control

Data can be passed in both directions:

• InitParameters - passes data into Silverlight (like if you were calling a method)
• Hidden Fields or XML Data Islands
• Web Services
• WPF

• Usar LINQ To SharePoint, que es una extensión de LINQ que traduce consultas LINQ a consultas CAML en SharePoint. El problema de esta extensión es que parece que está descontinuada, puesto que desde la versión alfa de noviembre de 2008 no ha habido nuevas versiones.
• Aprovecharnos la potencia que nos la clase List<T> que nos permitirá construir un objeto consultable mediante LINQ a partir de los elementos de una lista de SharePoint (que  no es consultable mediante LINQ).

En este post os voy a mostrar el segundo punto y como superar algunas limitaciones a trabajar con objetos de tipo List<SPListItem>. Lo pasos iniciales que he seguido son los siguientes:

• Añadir unos datos de prueba a una lista tipo Links de SharePoint.
• Crear un proyecto de aplicación de consola de Visual Studio 2008.
• Añadir la referencia a Windows SharePoint Services 3.0.

• En el código de la aplicación de consola, añadiremos las referencias necesarias para poder utilizar objetos de SharePoint por un lado, así como colecciones genéricas por otro.

• A continuación añadimos el código necesario para poder realizar la consulta a la lista de SharePoint:
  • Creamos una instancia de un objeto SPSite a partir de la url de nuestro sitio SharePoint.
  • A partir del objeto SPSite, creamos una instancia de un objeto SPWeb.
  • A partir del objeto SPWeb, creamos una instancia de un objeto SPList especificando además que sea la lista Links.
  • Definimos un objeto de tipo List<SPListItem> que si permite consultas con LINQ.
  • Añadimos elementos al objeto List<SPListItem> recorriéndonos la lista origen.
  • Realizamos una consulta LINQ.
  • Mostramos el resultado ejecutando la consulta con un foreach (recordar que LINQ aplica evaluación diferida de consultas).

• Sin más, mostramos el resultado:

Pero, no todo es tan bonito como parece...si os fijáis en el código, únicamente estoy mostrando la propiedad Name de la lista. ¿Se pueden mostrar más propiedades de la lista? La respuesta es que sí, pero no todas...esto lo he podido comprobar gracias al intellisense de Visual Studio. Por ejemplo, para esta lista no se muestra información como el usuario creador del ítem, la fecha de modificación, etc.

Entonces, ¿mi gozo en un pozo? La respuesta es que sí y que no...sí, porque no tengo accesibles todas las propiedades de manera indirecta, pero no porque si las tengo accesibles indirectamente gracias a que el objeto que almacena el resultado de la consulta LINQ ofrece una propiedad Xml en la que tenemos todos los campos de la lista de SharePoint...absolutamente todos. El código para comprobarlo es el siguiente:

Y el resultado que se visualiza por pantalla es:

Por lo tanto, tengo toda la información de cada ítem de la lista...en formato Xml, pero esto es tratable...con lo que lo tengo todo. Y hasta aquí llega este post sobre SharePoint y LINQ. Espero que os haya resultado interesante.

First I must admit I'm not running the update as the service account, recommended by Microsoft. This is because I'm working in a locked down environment where trying to get the permission to do this requires a lot of questions, moaning and red tape. However both my account and the service account (there's only one service account in use here) are local administrators.

The log file pointed to by the SharePoint Configuration Wizard contains this ever so helpful line: "An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown. Additional exception information: Failed to upgrade SharePoint Products and Technologies." However, with a little more digging there are details located at C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS. (This isn't actually the folder where I have directed diagnostic logs to, but for the purposes of an upgrade it seems SharePoint sometimes redirects it!) The logs contain errors over the several times I tried to upgrade...

Upgrade.log:

• SqlException: The default schema does not exist.
• SqlException: Cannot find the object 'MFN_Epm_GetAllCustomFieldsInformation', because it does not exist or you do not have permission.
• SqlException: Cannot drop the function 'dbo.MFN_Epm_GetAllCustomFieldsInformation', because it does not exist or you do not have permission.

Then in the ULS logs:

• The schema version (3.1.4.0) of the database SharePoint_AdminContent on server_x is not consistent with the expected database schema version (3.1.5.0) on server_x. Connections to this database from this server have been blocked to avoid data loss. Upgrade the web front end or the content database to ensure that these versions match.
• SqlException: Cannot find the user 'DOMAIN\myusername', because it does not exist or you do not have permission.
• Queue unable to interact with SQL. Queue type (Project Queue, Timesheet Queue etc): ProjectQ Exception: Microsoft.Office.Project.Server.BusinessLayer.Queue.QueueSqlException: PeriodicTasks failed ---> System.Data.SqlClient.SqlException: Invalid object name 'MSP_QUEUE_RENDEZVOUS'.

It appears that I don't have permission to the databases. However, my account is db_owner on every database The service account permissions haven't been changed. What's going on?!! It turns out the root of the cause was described this exception: The default schema does not exist.

I don't know a great deal about the schema feature introduced with SQL 2005, however with every user added to a SQL 2005 box, an accompanying schema with the same name is also created. A colleague of mine who was doing some spring cleaning on our databases removed the schema for our service account, however the service account's SQL user was still trying to use it as its default schema! The solution was to change the schema to dbo.

Unfortunately the upgrade still didn't quite complete since I was part of the way through the upgrade when it fell over... I also had to create a fake MFN_Epm_GetAllCustomFieldsInformation function in the Reporting database so the upgrade could find and drop it (fortunately replaced with the new version in the upgrade).

It was a big relief that this ended up working. The downside is that my user account and a schema for it have been created on the database server. It can't be removed right now because the new database objects that come with the update have my schema set as their owner! Now I have to change them all...

Weiterhin habe ich Herrn Dr. Thomas Lux von der Ruhr Uni Bochum getroffen, der dort am Competence Centrum für Data Warehouse und Business Intelligence arbeitet. Mit ihm habe ich lange über Problem von BI Lösungen im Krankenhaus gesprochen und wir haben uns über Microsoft BI Produkte und die Forschungsschwerpunkte des Competence Centrum unterhalten. Ich denke ich werde  mich nächste Woche auch bei Ihm einmal melden und schauen, ob wir hier vielleicht konkret zusammenarbeiten können, oder einen Erfahrungsaustausch anstoßen können.

Ich bin gespannt, was der morgige Tag so bringen wird...

So I have decided to just list my observations good and bad with Google Chrome, let me preface this with the fact I am very happy with how close to Firefox google chrome is, but that IE and even firefox are still better (at this early stage) than google chrome is for SharePoint.

The Nutshell: From an anonymous user and a web browsing perspective Google Chrome does everything you could want it to do. I didn't even see a single obvious styling issue (from anonymous perspective) with all of the SharePoint internet facing websites I have worked on.

The Cons:

• Clicking a file results in a "Save to" scenario instead of opening it in client applications.
• "Edit in" menu option results in a Windows SharePoint Services message asking for IE 6.0 or greater.
• Supports only single upload, not multiple upload in document libraries.
• Rich Text Controls (Content Editor and Page Editor) only display an HTML box.
• No drag and drop support for web parts.
• Minor styling things like the My Links shifting up and some tiny pixel like differences that I noticed.
• MySites also show some more styling differences - Personally the image being partly out of the left box made me snicker.
• No Edit in Datasheet for Lists and Libraries.
• No Open with Windows Explorer for Libraries.

The Pros:

• Speedy javascript. (Similar to firefox in terms of speed for JavaScript rendering).
• Love the "Create Application Shortcut" feature. Allows you to basically create desktop, start menu, or quicklaunch short cuts. These even open up in a sort of 'full screen view', which is pretty nice looking (and saves time).
• It's in Beta still.

That's what I have for now, I will try to keep this updated if I notice anything else.

Take Care,
Richard Harbridge

Why Do I Need It?

Over the years I have had to many customers ask me questions about operational recovery.

• What if I corrupt a database table?
• What if I get a virus? 
• What if I only need one file or a revision before the final version?

The truth is that business continuity does not translate into operational recovery or necessarily provide the option to recover at a very granular level. Business continuity is designed to resume business operations to a functional level in the event of a site wide disaster. You wouldn’t be implementing your BCP plans if you had a server failure or met the requirements from one of the questions listed above. In that case you would probably be restoring from your local back up copy which would likely be on tape if anything. And we all know what that restoration process looks like. Roll the dice, and ask yourself the questions.

•  Is the data there? 
• Can it be restored?
• And how long before I have that server up and operational?

Tape does what it is designed to but the effort involved with actually acquiring the tape and then restoring it is often tedious work at best. However, it does serve a purpose for those extensive archiving requirements defined by industry regulations such as HIPPA, SEC and or other Sarbanes Oxley requirements.

Here are a few options that you have available using TimeData to provide that TiVo® like operational recovery at a granular scale with out needing to restore from tape for everytime a user deletes a file.

TimeData Local Recovery Design

The first design includes the TimeData repository at the primary facility to easily retrieve data whenever needed. Double-Take is then also used to replicate the primary servers offsite to the disaster recovery facility. This solution design gives you the best of both worlds with local operation al recovery as well as offsite availability in the event of a site wide disaster. Below is an example of the design configuration:

For more information Marc LaFlure, TimeData Product Manager, will be presenting an in-depth look on how to use TimeData for operational recover and how to reduce tape restoration for business critical servers. Register here for the Sept 4^th webinar at 11am EST.

Stay tuned for part 2 of this TimeData Operational Recovery post.

SPSecurity.RunWithElevatedPrivileges(delegate()
{
// Code runs as the "SharePoint\system" user
});

Ещё одним важным замечанием является то, что SPSite необходимо инициировать внутри делегата, для достижения необходимого эффекта, если он будет инициализирован снаружи, то выполнение данного метода не даст никаких изменений.

Well, we've been patient, and Andrew has begun to share some of his thinking with us.  Andrew Chapman is a great person and lets his sense of humor show in his blog.  If you don't find it funny, you are doomed in the ECM world.  If there is any field that requires a sense of humor, it is ECM.

A Long Term Strategy

It has been said here, and elsewhere, that for the ECM vendors to survive SharePoint, they can't just offer architectural support.  They need to offer value that transcends performance and scalability.  Microsoft will eventually solve the problem and then what will the vendors do to coexist?  Well, last week Andrew started talking about the additional value that can be gained from combining SharePoint and an ECM system.

Andrew framed it fairly well.  While I don't think he place enough emphasis on the workflow and lifecycle benefits of placing content in an underlying system, he does get several benefits across:

• Hierarchical Storage Management: Store it cheaply when it is old and on expensive, fast performing, storage when it is young.  That simplifies it, but that is the gist.
• eDiscovery: Fancy word for the intersection of retention and search.  Okay, there is a little more than that, but it is something that resonates with businesses and that can lead to real ROI.
• Performance: Hey, while you gain all of these benefits, things will happen to start working faster now, not with the next two or three releases of SQL Server and/or SharePoint.

The performance goes from being the reason to a beneficial side effect.  That is a GREAT approach.  That puts things into the terms of an arms race that ECM vendors might possibly win.

Let us not forget, this solution should be transparent to the user, or as Andrew put it, non-invasive.

What is Coming?

If you have read Andrew's blog in the past, just reading the entry will give you a good idea.  The goal is to provide ECM functionality transparently to the user.  He mentions a few technologies and will be debating the merits of them in future posts.

I've actually talked to Andrew about the future about a month ago.  While I can't share anything specific, aside from telling you to read his posts and apply some brain power, I can tell you that it is very exciting.  I am excited, as are a couple of others in my organization that will remain nameless to protect them from the inquisition.  If you want to know, keep reading Andrew's blog and then do some research of your own.

I will say that the plans do not eliminate the need for the slew of products that are out there, both EMC and partner products.  Those are still complementary.  This approach just answers almost all of my challenges to the SharePoint products that I put to him at EMC World.  That is quite a feat as I can be quite annoying with questions about security and transparency.

I am forecasting good things in the upcoming future for those that use both Documentum and SharePoint.  Sooner would be better than later, but sometimes predicting software development is imprecise at best.

Time for some more patience.

Google Chrome is a browser that combines a minimal design with sophisticated technology to make the web faster, safer, and easier.

Click here to download.

Flying in the face of all the high-tech demo's, video's and animations, Google instead announced Google Chrome - and essentially a "white paper" - using a comic book format.

Click here to see the full comic (30+ pages). 

The comic details how the browser has been written from the ground-up, using a different memory management model (one process per tab - not just a new 'thread') - and that it's Open Source also !   

I'm only just starting to have a look/play with it - but seems very fast, and will be a decent match-up to Internet Explorer 8 (Beta 2 just been released).  And also needs to be as good as, if not better, than Firefox 3 (Mozilla).

For those who use SharePoint - how does the new Google Chrome browser stack-up ?    Eli Robillard has a post about SharePoint - with the conclusion that it "works for users" - but less so for administrators.

Today I downloaded and installed the just-released Google Chrome browser, ran it through some preliminary tests with SharePoint 2007 and so far, acceptable but missing a few key things.

Chrome supports NTLM authentication, uploads (though not multiple uploads), renders all the usual menus correctly, and generally does a good job of rendering SharePoint pages. And it's screaming fast.

Conclusion: not bad for an initial beta, but when you write anything from the ground up in a mature industry you can expect several releases to get the important parts right.

Source : Eli Robillard's World of Blog.

With that in mind, I'll have to try out some of the new features in Google Chrome - and see what the "developer tools" are like.

It will be hard to beat "FireBug" in FireFox - and "IE Dev ToolBar" in Internet Explorer.

But - some less than "flattering" ho-hum reactions from people like Paul Thurrott :

What we've really got here is an example of Google pulling a Microsoft: Creating an unnecessary me-too product that they can use for product tie-ins. All of the features here are present in exisiting browsers, all of them. So what does Google really bring to the table? Not much, it seems.

Source : It's real: Google to launch Web browser tomorrow

And this article :

Is there anything original in Google Chrome?

Most of the features look like "me-too", but then, that's what some people thought about Gmail....

As with Gmail, Chrome may be a big hit if it's brilliantly executed, especially given Firefox's general crashiness and bad memory leaks (which, to be fair, used to be part of IE too). But if it's more like Google Base, Knol, Orkut, Froogle and similar rubbish, it may not catch on.

Source : Is there anything original in Google Chrome?

Will have to try it out and see - expect to see some "chroming" in the office place today !    (and no - not the "inhaling fumes from spray-paint-cans" way !)

As an example I can hide controls or content from anonymous users, and show them for logged in users using the following code:

<SharePoint:SPSecurityTrimmedControl ID=”SPSecurityTrimmedControlID″
PermissionsString=”BrowseDirectories” runat=”server”>
<DIV>THIS TEXT IS HIDDEN UNLESS YOU ARE LOGGED IN</DIV>
</SharePoint:SPSecurityTrimmedControl>

This results in the DIV control and it's contents only being displayed to users who have the BrowseDirectories Permission.

There are many ways this can be used from hiding navigation items, to the hiding the Sign In link effectively.

The permissions you can select and use for this control can be found here: http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spbasepermissions.aspx

Hope this helps,
Richard Harbridge

maggiori informazioni le trovate presso il Microsoft SharePoint Team Blog

ed informazioni di dettaglio

Using the Content Query Web Part you can display a dynamic view of content from your site on a web page. The web part can be configured to retrieve items from a single list, a single site and subsites or the entire site collection. It builds a CAML (Collaborative Application Markup Language) query and uses the new Microsoft.SharePoint.SPSiteDataQuery class to query the server. Filtering, sorting, ordering and grouping can all be configured in the Web Part properties.

The approach to use if you are using a different style than the out of the box style is to deploy your own .webpart of the Content Query Web Part that references a different style sheet than the ItemStyle.xsl file. A Content Query Web Part displays a dynamic view of content on a page in your Microsoft Office SharePoint Server 2007 site. The Web Part runs a query that can span lists and sites in your site collection, and then presents the results of that query on the page. You can, for example, use this Web Part to display the five most recently published articles in your Web site, regardless of where they are stored.

Now edit the the template like you normaly do XSLT formating. I also included for example a JS funktion in the Style for custom Window Popup configuration.

Here is an example:

<xsl:template name="Name" match="Row[@Style='Name']" mode="itemstyle">
<xsl:variable name="SafeLinkUrl">
<xsl:call-template name="OuterTemplate.GetSafeLink">
<xsl:with-param name="UrlColumnName" select="'LinkUrl'"/>
</xsl:call-template>
</xsl:variable>
<xsl:variable name="DisplayTitle">
<xsl:call-template name="OuterTemplate.GetTitle">
<xsl:with-param name="Title" select="@Title"/>
<xsl:with-param name="UrlColumnName" select="'LinkUrl'"/>
</xsl:call-template>
</xsl:variable>
<xsl:variable name="LinkTarget">
<xsl:if test="@OpenInNewWindow = 'True'" >_blank</xsl:if>
</xsl:variable>
<div>
<tr>
<td id="linkitem" class="item link-item">
<a href="" target="_blank" onclick="javascript:customPopup('{$SafeLinkUrl}');return false;">
<xsl:value-of select="$DisplayTitle"/> -
<xsl:value-of select="@Name_x005F_x0020_Year" />
(<xsl:value-of select="@Languages" />, <xsl:value-of select="@Document_x005F_x0020_Type" />)
</a>
</td>
</tr>
<tr height="8px">
<td></td></tr>
<script type="text/javascript">
function customPopup(url)
{
Report = window.open(url,'Report','status=1,width=750,height=650,resizable=no,scrollbars=no');
Report.moveTo(0,0);
}
</script>
</div>
</xsl:template>

Note:

In the XSL file you'll find xsl:template elements for each selectable style in the Content Query Web Part style drop down. As a best practice I won’t modify any of the default styles, but rather adding my own style.

The easy approach is to copy the xsl:template element of the style that matches your style the most,and make alterations to it.

- Copy the <xsl:template name="Default" match="*" mode="itemstyle">element
- Change the name attribute to "DetailedStyle"
- Change the match attribute to "Row[@Style='DetailedStyle']"

Here you can select your template you created before. You have to add a simple CQWP to your page and select your site or list, type and aproriate Content Type. In the next step export the Webpart to your local maschine an edit the file.

By default, the XSL style sheet that controls the presentation of the Content Query Web Part renders the Title, Description, ImageUrl, and LinkUrl columns (if present) of the items the query returns. The Web Part renders the ImageUrl and LinkUrl columns as an image and as a hyperlink, respectively. The Content Query Web Part uses XSL style sheets to render these columns by default. If you want to query for custom content types and render specific columns from those content types in the Web Part, you need to perform some minor customization in the .webpart file.

You only have to do change the webaprt file, when you want to present your own columns in the style in adition to default values. Open the .webpart go to line <property name="CommonViewFields" type="string">. Follow the instruction from this post CommonViewFiled Types.

E.g. <property name="CommonViewFields" type="string">Previews, PublishingRollupImage;FileSizeDisplay,Computed;File_x0020_Size,Lookup;Product, Choice;ProductGroup, Choice;DownloadIT, String;</property>

Important Note!

You cannot use your columns' display names in this property. You can find the internal column names by checking the properties of the column in the list or document library. Right-click the column, and then click Properties. The internal name of a column appears in the Address (URL) property after 'Field='. In the Knowledge Base Articles scenario, the columns are Knowledge Base Article and Product and their internal names are KB_x0020_Title and Product, respectively.

In the next step, import your new webpart file to the CQWP. Choose your custom ItemStyle in the list and thats all.

Read more on

http://msdn.microsoft.com/en-us/library/ms551040.aspx

http://msdn.microsoft.com/en-us/library/aa981241.aspx

http://www.microsoft.com/belux/msdn/nl/community/columns/stevenvandecraen/contentquerywebpart.mspx