MsDevelopers

Sitios de proyectos basados en el template “Team Site” de Sharepoint y algo mas…

2012-02-14T08:06:00.001-08:00

A medida que fue pasando el tiempo hemos usado el template “Team Site” para manejar y trabajar en proyectos, usandolo de diferentes maneras:

Proyectos simples: 1 solo team site
Proyectos recurrentes: 1 team site con algunos subsites
Multiples proyectos – Sitios PMO
Multiples proyectos – Coleccion de Sitios

1-Para los Proyectos simples. En la mayoría de los proyectos que son simples, proyectos a corto plazo se utiliza un Team Site sobre todo para compartir documentos, y tal vez un calendario para las reuniones y los plazos. Todo el mundo con una lógica empresarial podría pedir un Team Site. Se lo dejamos a la gerente del proyecto para configurar, pero rara vez lo hace, o cuando lo hacen el proyecto esta terminando y el sitio ya perdio el interes de mantener su contenido y estructuras. La configuración básica es en general suficiente y la audiencia es pequeña.
Es ideal que el sitio no tenga tabs, que antes eran muy usadas, pero lleva bastante trabajo configurar correctamente, sobre todo con contenidos intuitivos. Para un proyecto a corto plazo no era eficiente.

2-Proyectos recurrentes.También hay equipos que tienen un proyecto tras otro, como el desarrollo de productos y de IT. Algunos de los responsables del proyecto querían tener una configuración estándar para su Team Site para cada proyecto. Por ejemplo, un campo de búsqueda estándar en cada biblioteca de documentos con las fases del proyecto, una lista personalizada para administrar el tiempo , o un reloj mundial, ya que estaban trabajando con gente de todo el mundo. Como no nos gusta configurar sitios independientes en todo momento, creamos generalmente una plantilla , que nosotros o ellos pueden activar cuando sea necesario. Asi, los responsables del proyecto tienen el beneficio adicional de que todos los sitios de los proyectos se encontraban bajo su Team Site.

3-Multiples proyectos – Sitios PMO. Como todas las grandes empresas, solemos tener proyectos globales con sub proyectos locales o funcionales. Se podría pensar en un proyecto sustentable, el seguimiento de la Encuesta de Satisfacción de los empleados , o el programa de reduccion de costos de una empresa . Es esencial que el progreso de estos proyectos puedan ser controlados de una manera fácil.
Muchos de esos proyectos fueron facilitadas por un Team Site simple con una lista Seguimiento de asuntos como el componente principal. Cada proyecto es un elemento , que el jefe de proyecto correspondiente tiene que actualizar de forma regular. Configurando la lista y las vistas podemos dar un gran panorama de los avances del proyecto al Gerente.
Los proyectos individuales pueden ser manejados en un subsitio, un sitio independiente, o de una manera diferente.
Las primeras veces habia empujar esta funcionalidad a los directores de programas diferentes, pero después de unas pocas implementaciones exitosas, la gente nos pide esto inmediatamente cuando un proyecto global de nuevo fue planeado.

4-Multiples proyectos – Coleccion de Sitios.Para otros proyectos globales más importantes se puede crear una colección de sitios dedicada. Sólo se hizo cuando era absolutamente necesario, por ejemplo, cuando muchas personas tuvieron que contribuir (aumentando el riesgo de sobreescritura accidental), un montón de documentación tuvo que ser compartido, y / o que era importante que un país o ciertos roles no tengan acceso a la información.
En esos casos se utilizó un subsitio plantilla por país y / o rol para cada uno. Para esto se necesito funcionalidades de Content Management. Por ejemplo, los anuncios y los manuales se publicaban en un sitio, y bajaban a todos los subsitios, mientras que los resultados del proyecto se puso encima de todos los subsitios en otro sitio para la presentación de informes.
Todos estos resúmenes influyeron en el rendimiento del sitio. Junto a esto, es indispensable pensar en la seguridad, porque había muchas personas que necesitan acceso a un sub-sitio u otro, y si querian ser capaces de ver el conjunto de los resultados, había que tener acceso a todos los subsitios. En estos casos a veces es necesario mantener los templates para reusarlos con funcionalidades que vamos agregando.

Para concluir , estos son algunos approachs de distintos tipos de sitios para manejo de proyectos. A veces usados para mantener nuestro orden en el proyecto, a veces para cumplir con PMO a veces para mostrarle al cliente que trabajamos ordenadamente,o todo esto junto.

Asi como nosotros podemos hacer cambios en estos sitios, tambien tenemos gente que se dedica a desarrollar variadas funcionalidades muy buenas para este tipo de sitios como la gente de Brightwork

Sharepoint en dispositivos mobile

2012-02-07T05:46:00.001-08:00

iOS – iPhone + iPad

Android

Blackberry

Windows Phone 7

Microsoft SharePoint Workspace Mobile

Recuerden que con Nintex Forms pueden generar formularios Web y para cualquier dispositivo Mobile

Los 10 mejores sitios Sharepoint del 2011

2012-02-02T05:34:00.001-08:00

1	http://www.fiatspa.com/en-US/Pages/Home.aspx
2	http://www.ataturkairport.com/en-EN/Pages/Main.aspx
3	http://www.volvocars.com/Pages/default.aspx
4	http://www.embraer.com/en-US/Pages/Home.aspx
5	http://www.sharpie.com/Pages/GlobalLanding.aspx
6	http://www.faurecia.com/Pages/Default.aspx
7	http://www.kempinski.com/en/Pages/Welcome.aspx
8	http://www.pousadas.pt/historic-hotels-portugal/en/pages/home.aspx
9	http://www.trincoll.edu/Pages/default.aspx
10	http://www.360-5.com/Pages/default.aspx

Fuente:

http://www.topsharepoint.com/top-rated-sharepoint-sites-for-2011

Enviá mas correos Con Office 365 para individuos y pequeñas empresas

2012-02-01T18:00:00.001-08:00

Microsoft ha anunciado hoy que su suscripción de Office 365 para individuos y pequeñas empresas - o lo que se denomina Plan P - ha sido mejorada para permitir a los usuarios enviar tres veces el número de mensajes de correo electrónico por día. Ahora, los usuarios pueden enviar 1500 correos electrónicos por día , en comparación con el límite anterior de 500.
El cambio se hizo en respuesta a los comentarios de los clientes.
"Los límites de destinatarios existen para disuadir a los usuarios el envío de grandes volúmenes de correo electrónico comerciales no solicitados, comúnmente conocido como spam",escribió Steve Chew de Microsoft en el blog de Office 365."Estos límites protegen nuestro servicio en línea de que se convierta en una fuente de spam y, como resultado de estas protecciones,queremos mantener los mensajes de nuestros clientes de correo electrónico fluyendo.

Mejoras del DataCenter nos han permitido aumentar este límite manteniendo el mismo nivel de protección".

Microsoft ofrece una solución interesante si estás llegando al límite : Usá las listas de distribución.Al parecer, Office 365 considera un simple correo electrónico a una lista de distribución enorme para contar como un solo correo electrónico enviado.

Para mas informacion visitar Politicas de Mail

SharePoint 15 – Lo que se sabe hasta ahora

2012-02-01T06:13:00.001-08:00

Como era de esperar, el anuncio esta semana de Office 15 (fijate lo que te perdiste) dió lugar a un montón de rumores y conjeturas a través de la web de SharePoint 15 (o SharePoint 2013 ) y como está tomando forma. Así que veamos que pensamos con lo que sabemos hasta ahora:

Microsoft ha prometido una versión beta pública este verano boreal. ( fuente )

La documentación del SDK de SharePoint 15 CTP ha sido liberada. ( fuente )

Office365 recibirá una actualización como parte de Office 15. Esto significa que va a haber cambios para el servidor de SharePoint en línea. ¿Cómo encaja esto con el programa de actualización más adhoc de Office365 , no lo sabemos todavía. ( fuente )

La especulación sugiere que Office 15 no se basará en la interfaz del nuevo Metro de Windows 8, es seguro asumir que SharePoint 15 no tomará ninguna clave de diseño del Metro tampoco. ( fuente )

Sin embargo, Steve Ballmer, se ha negado a descartar que Metro tiene una influencia sobre las nuevas interfaces. Es probable que las interfaces de las aplicaciones de Office 15 se acerquen a algunos indicadores de Metro, pero no serán "Aplicaciones Metro". ( fuente )

Podrian las Webparts ser reemplazado por "Aplicaciones Metro"? Es una especulación basad en lo que dice CMSWire. ( fuente )

Los rumores de un "Office para iPad 'siguen extendiéndose. ¿Será esto parte de Office 15? ( fuente )

Todavía no se sabe si se llamará SharePoint 15, SharePoint 2012, SharePoint 2013 o lo que sea. Si la beta es el verano boreal, y la conferencia oficial de SharePoint es en noviembre 12 hasta 15 , entonces una versión 2013 tendría sentido. SharePoint 2010 siguió un camino similar (beta a finales de 2009, RTM en abril de 2011, y publicado en mayo de 2011)

Sharepoint the point – Buenos Aires Slides

2012-01-25T11:03:00.001-08:00

Pude recolectar algunas slides de nuestros amigos

I gathered a few slides from our friends.

Speaker	Link to Slides
Joel Oleson	Social Intranets : Transforming traditional portals
Michael Noel	Building the perfect Sharepoint 2010 farm: Real World Best practices from the field
Dan Holme	Architecting Sharepoint for scalability and enforceable Governance

2011-12-28T07:44:00.000-08:00

Fernando Hunth
From: Argentina
Fernando Hunth has been working with Microsoft technologies for over fifteen
years. He has participated in several projects working with Sharepoint from 2003
versions and writting web parts with C# language. Fernando also has experience
with WebForms, WinForms, Web Services, SQL 2000/2005, stored procedures,
triggers, replication, reporting services, etc.

Fernando has also been working for over four years with WSS 2.0, 3.0
Sharepoint Portal Server 2003 & MOSS 2007 & Sharepoint 2010 & Nintex
Workflows 2007 - 2010. He has experience in project administration.

Today, he’s a Information Worker Tech Leader & Sharepoint Architect at
Baufest. His session on SharePoint Branding will be delivered at the Buenos
Aires, Agentina STP stop.

Sharing The Point South America Tour 2010 Speakers

El ecosistema de InfoPath o “La Oficina sin papeles”

2011-11-03T09:01:00.001-07:00

Introducción

Hay una enorme demanda de conversión de formularios en papel a formularios electrónicos. Al utilizar el término "en papel" lo que se quiere decir es cualquier formulario que es llenado a mano y enviado a través de alguno de las siguientes maneras:

Entrega en mano
Fax
Un correo electrónico con el formulario adjunto como un documento digitalizado.
Formulario preimpreso.

A propósito de esto, casi todos los pdf en uso hoy en día entran en esta categoría. La razón no es que Adobe no tiene un adecuado proceso para formularios electrónicos, ya que Adobe lo hace. Pero Adobe no ha sido tan exitoso como Microsoft en la participación de la comunidad para utilizar su suite. Este post no es acerca de la comparación de herramientas, pero si para resaltar que es allí donde es significativamente más que un formulario, el formulario en sí.

En el caso de InfoPath, la mayoría de los clientes vienen con la esperanza de convertir un formulario en papel a formato electrónico. Mucha gente piensa que esto es un asunto trivial. Debería serlo, pero hay una gran variedad de expectativas justificables e implícitas que tienen los usuarios de formularios electrónicos que son a veces sutiles y a veces se pasan por alto. En el "El Ecosistema InfoPath" las partes constitutivas del modelo son:

El formulario electrónico (InfoPath)
Páginas de lanzamiento y de inicio
Presentación de informes
Workflows automatizados

La figura 1 ilustra el ecosistema de InfoPath.

Figura 1: El ecosistema de InfoPath

1. Los formularios electrónicos (InfoPath)

Algunas de las sutilezas que la gente no piensa cuando están convirtiendo "papel" a formularios de InfoPath son:

Guardar vs Enviar
En casi todos los proyectos, los clientes dicen que quieran un formulario muy sencillo. Cuando se les pregunta si que quieren la funcionalidad de “Guardar”, dicen que no y se les explica que una vez que se envía un formulario, los datos no se deben cambiar. Después el usuario comienza a trabajar con el formulario durante un tiempo, y casi todos piden agregar la funcionalidad de “Guardar” . Por “Guardar”, me refiero a que el usuario es capaz de guardar el formulario para modificaciones posteriores y los destinatarios no se notifican todavía. Además, si existen workflows automatizados que se supone que no comiencen correr, hasta que realmente se envía el formulario. Una vez que se envía el formulario, el iniciador puede volver atrás y mirar el form, pero ya no puede modificar el formulario.
Pre-filling inteligente
La gente tiene poca paciencia para completar formularios electrónicos. Menos aún que los formularios en papel. Consiguen frustrarse rápidamente. Por lo tanto los formularios deben completarse automáticamente con tanta información como sea posible. Por ejemplo, en un sistema donde el usuario está registrado o logeado, una gran cantidad de información personal puede ser completada. InfoPath permite añadir lógica sofisticada, que permite a muchos de los campos de formulario para ser rellenados con las respuestas más probables y además hacer conjeturas excelentes en cosas como las fechas y horas.
Ocultar y desactivar controles inteligentemente
Por ejemplo, el botón enviar debe ser deshabilitado, hasta que se rellenan todos los campos requeridos.
Mostrar y ocultar partes diferentes dependiendo del usuario y el estado del formulario
Por ejemplo, el propietario de un proceso puede tener privilegios especiales que no tienen un usuario normal. Otro ejemplo es proporcionar una página vista preliminar que muestra un resumen de todas las respuestas antes de que el usuario envía el formulario. La página de vista previa no permite editar, sólo muestra el usuario las respuestas que han dado a las preguntas del formulario. Esto es similar a la función de vista previa de impresión en muchas aplicaciones.
Controles importantes para una experiencia fácil
Por ejemplo, si el usuario tiene que seleccionar una respuesta de un gran número de opciones, como todas las universidades en los Estados Unidos. Un control ideal para esto es un cuadro de texto con Autocompletar.

Todo lo anterior mencionado, con excepción del último elemento, pueden implementarse por un usuario experimentado de InfoPath. El último elemento requiere un desarrollador de "nivel medio" que sabe cómo escribir Javascript, llamadas a servicios Web y jQuery (o similares).

2. Páginas de inicio
No es deseable exponer a los usuarios a una lista o biblioteca de formularios de SharePoint nativa. En la figura 2 se muestra un ejemplo de una biblioteca de forma nativa. A veces es demasiado confuso. Es una buena práctica proporcionar una página de inicio que proporciona instrucciones junto con un botón de lanzamiento. Del mismo modo esta bueno tener una página donde los usuarios pueden ver sus propios formularios. Para los formularios más simples, se puede usar una sola página como panel de control. Para los mas complejos, un panel de control mas complejo, mostrando por ejemplo los formularios en cada etapa del ciclo de vida. Un panel de control para nuevas solicitudes se puede hacer creando una página con las funcionalidades Out-of-the-box de SharePoint con un poco de html personalizado en un elemento Web Editor de contenido.

Figura 2: Es una captura de pantalla de una biblioteca de formularios que contiene las solicitudes . Para un usuario que empieza a conocer o usar el formulario, es hostil y confuso. Esta es la razón por la que necesitamos construir una página

3. Presentación de informes

El dueño del proceso a veces quiere ver las estadísticas de resumen de los datos. A veces piensa que es una simple lista, pero a veces viene con requisitos de un dashboard, lindos diagramas y gráficos. En este aspecto se puede ahondar bastante. Lo más sencillo es utilizar páginas de elementos Web de SharePoint con DataView WebParts , Graph Web Parts y Excel. Hay numerosos complementos de terceros que pueden permitir muy rica visualización y análisis de datos. Algunos ejemplos son: Spotfire, Tableau (herramientas de visualización) y Knime (una herramienta de código abierto que ayuda con análisis de datos.)

4. Workflows automatizados

Ya se habló de páginas de inicio para utilizar en workflows. Los Workflows para, revisores, aprobaciones, sofisticados procesos de negocios, o sólo workflows de notificaciones pueden ser difíciles de diseñar e implementar. Los workflows deben ser cuidadosamente diseñados y documentados. Generalmente se escribe un diagrama de estado tradicional. Estos diagramas de Estado se asemejan a un grafo dirigido de matemáticas (véase la figura 3.) A la hora de aplicar los workflows, hay muchas opciones. Los workflows de SharePoint Designer son una tecnología libre y te puede ayudar bastante en ciertos procesos.

El tema es cuando es necesario diseñar workflows profesionales y sobre todo sin código. En ese momento es cuando usamos Nintex Workflows que cubre el 99% de las necesidades de los usuarios.

Figura 3: Grafo dirigido

Conclusión

Las personas a veces hacen trivial el diseño de formularios electrónicos y no se dan cuenta que hay un importante ecosistema que se necesita para hacer los formularios más fáciles de usar, y que los resultados sean fáciles de analizar.

En Baufest podemos ayudarte a crear tu propio ecosistema.

Nintex Forms, aplicaciones móviles en SharePoint

2011-10-14T06:26:00.000-07:00

Noticias Nintex

Nintex Forms 2010 se presenta en Microsoft SharePoint Conference

Nintex dio a conocer Nintex Forms 2010 en el primer día de la Conferencia de SharePoint en Anaheim, California.
Nintex Forms es un diseñador web que permite crear formularios dentro de SharePoint de forma rápida y sencilla.
Los formularios pueden ser consumidos en los dispositivos móviles más comunes desde Internet, en cualquier lugar y en cualquier momento.
Nintex Forms se integra perfectamente con Nintex Workflow para automatizar procesos de negocio y entregar aplicaciones ricas de SharePoint.
El lanzamiento de Nintex Forms 2010 llega despues de la conclusión de un programa beta multi-etapa de participación de una gran base de usuarios de los partners Nintex y clientes de todo el mundo que proporcionan información muy valiosa y se aseguró de Nintex Forms es funcional y versátil.
Mike Fitzmaurice, vicepresidente de tecnología de producto en Nintex, comentó sobre la visión del producto, "Los clientes nos dijeron que necesitaban un producto de formumarios que fuese fácil de usar y más accesibles para los usuarios de negocios, incluso a los clientes con herramientas de formularios existentes para los escenarios de desarrollo avanzado. Fitzmaurice agregó:" Hemos hecho Nintex Forms tan fácil de usar como arrastrar los componentes del diseño sobre un lienzo basado en el navegador, reflejando la experiencia que nuestros clientes ya tienen con Nintex Workflow ".
Nintex Forms ofrece la posibilidad de diseñar formularios una vez, y que estén disponibles en múltiples dispositivos, además de la opción de combinar con Nintex Workflow.
Esto ayudará a nuestros clientes a automatizar procesos de negocio con las aplicaciones móviles en SharePoint, y ya ha entusiasmado a nuestros socios de soluciones en el programa beta que han creado escenarios de pruebas de concepto , dijo Fitzmaurice.
Los formularios pueden ser publicados en internet, a través del servicio Nintex Live, y acceder por cualquier persona ajena a la red corporativa con un solo clic y sin necesidad de hardware adicional, software o configuración de la infraestructura.
Wayne Woolston, director de gestión de Nintex, se refirió a esto, "Nintex ha realizado una inversión considerable en nuestro servicio Azure, Nintex Live, y esto permite a los formularios que se publican en Internet y abrir nuevas oportunidades para los clientes y socios para ofrecer y acceder formularios. "
Además de su facilidad de uso y la posibilidad de publicar formularios en internet, Nintex Forms incluye un gran número de características en la caja que ayudan a los usuarios de negocios a crear formularios, incluyendo diseños de dispositivo predefinidos, botones personalizados y formato HTML enriquecido.
Un precio promocional de introducción está disponible para los actuales clientes de Nintex Workflow 2010 y los que compran Nintex Forms 2010, junto con Nintex Workflow 2010.

La información completa del producto Nintex Forms 2010, el acceso a una prueba gratuita de 30 días y la inscripción para el seminario publico en Noviembre , una demostración de 60 minutos de cómo funciona Nintex Forms y cómo se puede utilizar para diseñar formularios de SharePoint están disponibles en www.nintex.com/forms .

Intranet Social en su compañia

2011-10-05T14:21:00.000-07:00

Se sabe que el interior no es como el exterior . En encuestas a empleados de algunas compañías, dijeron que su intranet actual no funciona como ellos esperan. El 71% cree que es más fácil encontrar el conocimiento en la Web , y se dice que cada empleado usa 9,5 horas por semana para buscar información.

Hay encuestas que consideran que el 36% de los empleados dicen que su intranet no cumple con las necesidades de su trabajo diario. En la misma encuesta, el 45% de los empleados dice que su intranet no crea comunidad ni solidaridad. El conocimiento es la nueva moneda de hoy y es hora de comenzar el desarrollo de las intranet sociales que expone los conocimientos especializados internos y capital intelectual en la organización. El conocimiento es hoy en día transmitido de forma anónima e ineficiente por correo electrónico, teléfono y conversaciones de pasillo,etc . Las intranet sociales generan un 20% mas de innovación y la accesibilidad de un 35% mayor al conocimiento y expertos.

Las Intranet sociales ofrecen muchos beneficios para su organización:

Un lugar mas rápido para los nuevos empleados (ahorro de tiempo)
Un lugar mas rápido para encontrar la información correcta (ahorro de tiempo/eficiencia)
Eliminar otros lugares para recibir informacion incorrecta (aumento de la calidad)
Un lugar mas rapido para encontrar las habilidades (ahorro de tiempo)
Un lugar mas rapido para resolver los problemas (eficiencia)
Un lugar mas facil para trabajar juntos (sinergia)
Mas informacion valiosa y nuevas ideas (ganancia de compromiso)
Una comunidad mas familiar y solidaria (ganancia unitaria)

Hay calculos que muestran que la rentabilidad de invertir en una intranet social es rentable en el primer año para una organizacion con 500 empleados. Aún mas rapido para las grandes organizaciones.

Las plataformas de colaboración como Sharepoint tienen como objetivo aumentar los conocimientos en una intranet, y ayuda a encontrar argumentos para convencer su gestión, y facilitar el trabajo para implementar de forma segura su propia intranet social.

Actualmente en podemos ayudar a implementar su Intranet para hacerla +Social.

Sharepoint certified x 5

2011-07-26T10:07:00.000-07:00

I got my fifth Sharepoint Microsoft Certified Technology Specialist (MCTS).
Now I am certified in:

Skills Being Measured

This exam measures your ability to accomplish the technical tasks listed below.The percentages indicate the relative weight of each major topic area on the exam.

Creating an Application Design (19%)

Evaluate application data access and storage

This objective may include but is not limited to: SharePoint List and relationships, Document Library, SQL Database, BCS, web service, file system, remote BLOB storage, and all other external data sources
Identify artifacts from application requirements

This objective may include but is not limited to: web parts, event receivers, list definitions, list templates, workflows, site definitions, custom actions, content types, site columns, mapping artifacts to application requirements
Select a deployment model

This objective may include but is not limited to: identifying artifacts and execution appropriate for sandbox and farm (i.e. GAC vs. BIN) implementation, designing solutions for single server or multi-server environments, dividing artifacts between sandbox and farm
Select the appropriate execution method

This objective may include but is not limited to: in-page, workflow, event receiver (asynchronous vs. synchronous), timer job, and service application, selecting which logic execution model to use for a problem, determining where code or artifact runs

Designing UX (17%)

Determine presentation page type

This objective may include but is not limited to: Web Part page, application Page, publishing page, page layout, static page
Determine SharePoint visual components

This objective may include but is not limited to: web parts, silverlight, AJAX, ribbon, visual web parts, delegate controls, custom field types, dialog
Plan branding strategy

This objective may include but is not limited to: determining usage of themes, templates, enforce consistency via site definitions, master pages and page layouts, determining usage of CSS styles and JavaScript, designing usage and role of Styles Library or Site Collection Library
Design application customization strategy

This objective may include but is not limited to: supportable customizations allowed through SharePoint UI, SharePoint Designer 2010, VS 2010 (site columns, content types, page customization, themes, page layouts, personalization)
Design navigation strategy

This objective may include but is not limited to: identify inclusion of navigational items (global/current/custom), consume an existing site map provider vs. create a custom provider, determine depth and inclusion of pages/sites, dynamic vs. static navigation, consume an existing navigation control vs. create a custom navigation control

Managing Application Development (18%)

Design for localization and globalization

This objective may include but is not limited to: use and implementation of resource files, variations (content creation and workflow, multilingual content), selecting locales, date and time, regional settings, RTL vs. LTR
Develop a security approach

This objective may include but is not limited to: authentication (NTLM, Kerberos, Forms-based Authentication, claims, Single Sign-On, Anonymous), authorization (SharePoint groups, AD groups, claims, permission levels) enterprise-wide security policies
Define application configuration approach

This objective may include but is not limited to: defining "web.config" modifications, Lists as a configuration option, Property bags, declarative vs. programmatic, SP persisted objects

Optimizing SharePoint Application Design (15%)

Optimize page performance

This objective may include but is not limited to: View State, Inline JS, Inline CSS, HTML output, AJAX, Client side cache, .NET cache, BLOB Cache, Session State, IIS compression
Optimize data access

This objective may include but is not limited to: SPQuery, SPSiteDataQuery, Large lists, Search (managed properties), SharePoint 2010 query throttling, Client object model vs. web service/rest/SOAP/RPC, Linq
Design for logging and exception handling

This objective may include but is not limited to: Determining appropriate level of logging to include in a custom code project, Evaluating SharePoint log data, Instrumenting code to improve the ability to maintain the system, Determining when exceptions are raised, error values returned, and what should be written to the SharePoint ULS log, Debugger, and Event log
Identify and Resolve deployment issues

This objective may include but is not limited to: single server vs. farm vs. multi-farm, infrastructure vs. content database, web applications, application pools, feature activation failures, pushing applications to front end, security context, feature scope, feature dependencies
Analyze memory utilization

This objective may include but is not limited to: Memory profiling, Disposal of SharePoint objects, Load testing, Identifying memory bottlenecks (hierarchy), Analyze ULS logs, Monitoring memory counters, ensure implemention of IDisposable on custom artifacts containing IDisposable members

Designing SharePoint Composite Applications (13%)

Design external application integration

This objective may include but is not limited to: Selecting appropriate BCS connection from Web Service, .NET Type, and SQL Connection, Defining authentication requirements, Defining solutions that include Office client applications
Determine data capture approach

This objective may include but is not limited to: Evaluate when to use different forms technologies (InfoPath vs. ASP.NET), Office client, Silverlight, BCS, Infopath Forms Services
Design SharePoint information architecture

This objective may include but is not limited to: Content types (local, global), Site columns, Site structure, Taxonomy (managed metadata)
Design a workflow solution

This objective may include but is not limited to: workflow tool (Visio, SharePoint Designer, Visual Studio), Sequential vs. State Machine, Item vs. Site, Declarative vs. Code, custom actions

Designing SharePoint Solutions and Features (18%)

Plan SharePoint Features

This objective may include but is not limited to: Feature Sets, Feature Stapling, determine feature scope, Create a new Feature (vs. extending), activation dependencies, feature receivers
Plan SharePoint solution packaging

This objective may include but is not limited to: Create a new Solution (vs. extending), Manage reference assemblies in a SharePoint WSP solution, solution sets, solution dependencies, solution targeting
Establishing application modification and version upgrade strategy

This objective may include but is not limited to: Designing an artifact upgrade strategy, Feature and solution upgrade, Site upgrade, Versioning custom assemblies, Versioning workflows (new feature, new assembly version, new code), Resolving incompatible changes between dev and production
Develop a strategy for delivery of application modifications and existing data transformation

This objective may include but is not limited to: Formulating a new version of custom code, Updating Web parts while retaining properties, connections and other user entered settings, Content maintenance, Developing a content upgrade strategy, Deployment configurations, Deploying modified code safely (data safe), Preparing scripts (PowerShell, EXE), packages (WSP, MSI), or installers

Just a reminder about Sharepoint Migration tools vendors

2011-06-08T12:30:00.000-07:00

AvePoint(http://www.avepoint.com/sharepoint-migration-tools/)

Axeler(http://www.axceler.com/SharePointMigration.aspx)

MetaVis(http://www.metavistech.com/)

Metalogix(http://www.metalogix.com/)

Quest Software (www.quest.com/sharepoint/migration.aspx)

IT Showcase On: Microsoft® SharePoint® - Microsoft IT Usa Servicios de Infraestructura y Politicas de Governance para lidiar con 29.9 TB de datos en SharePoint

2011-05-18T09:35:00.001-07:00

RESUMEN EJECUTIVO

Situación:

Microsoft IT (MSIT) desplegó por primera vez Microsoft SharePoint en el año 2000 antes de que Microsoft lanzar este producto. MSIT no hizo mucho con el governance en ese momento. En pocos años, había aproximadamente 250.000 sitios de SharePoint de Microsoft con 200 a 500 sitios nuevos por día. Para frenar este crecimiento tremendo, MSIT creó una servicio de infraestructura y aplicar estrictas políticas de gobierno.

Por qué debería importarme esto a mí:

1. MSIT administra un asombroso número de sitios de SharePoint, incluyendo aproximadamente 224 mil sitios de nivel superior y 545 mil subsitios . Monto total de los datos: 29,9 TB.
2. MSIT cuenta con dos servicios principales: un servicio estándar (utilizado por la mayoría de los empleados) y un servicio personalizado para los usuarios y grupos que requieren más que el servicio estándar.
3. En sus implementaciones de SharePoint, MSIT experimentó issues de crecimiento igual que otras organizaciones de TI. Otras empresas pueden hacer uso de las lecciones aprendidas de MSIT para evitar los mismos issues o para hacerle frente a la demanda.
4. Con cada nueva versión de SharePoint, MSIT ha sido capaz de utilizar menos código personalizado desde que el producto fuera de la caja ofrece una cobertura para las áreas que antes requerían el código personalizado.

Mas info IT Showcase On: Microsoft SharePoint

Sharepoint + communicator presence bubble Problem

2011-04-12T14:09:00.001-07:00

This could be the solution for this thread

http://social.technet.microsoft.com/Forums/en-US/sharepointgeneral/thread/2ae69f05-c6fc-4f2f-ae6e-080056baf4cc/

Try placing this .js file in your page

http://www.divshare.com/download/14554218-6ce

¿Qué está impulsando el aumento masivo de puestos de trabajo de SharePoint sobre todo en los EE.UU. y Canadá.?

2011-04-12T10:11:00.001-07:00

Ha habido un notable incremento en el número de roles con experiencia en SharePoint. ¿Por qué ha habido tal carrera ascendente?

SharePoint 2010 ha ganando una mayor aceptación entre los clientes nuevos o antiguos de MOSS 2007 convertidos a 2010?

Por lo visto empresas de mediano a gran tamaño están aprovechando los acuerdos Enterprise para implementar 2007 y 2010, como el software assurance. Como muchas empresas migran a las últimas versiones posteriores de Exchange, muchos también implementan SharePoint como una alternativa mucho más atractiva que las carpetas públicas.

Se está empezando a ver, por fin, a las organizaciones reemplazar sus anticuados file system server por soluciones de colaboración en línea como SharePoint.

Se puede lograr valor de negocio real mediante el uso de SharePoint. No aplica a todos los requisitos de negocio, sino como una solución global que puede tener un ajuste perfecto. La razón por la que hay muchos puestos de trabajo también es porque las empresas están luchando para lograr los beneficios y está buscando personal calificado. Un verdadero reto es hacer que las organizaciones entiendan que se debe maximizar las funcionalidades OOB antes que la "personalización".

La mayoría de las empresas tienen una intranet y también usan Microsoft Office y al usar las nuevas versiones, la progresión a SharePoint es casi natural. También parece que SharePoint 2010 es cada vez más rápido porque la mayoría lo acepta como "nueva y mejorada" la integración entre Office 2010 y SharePoint 2010 siendo mucho mejor.

Hay una verdadera BI y una plataforma de colaboración completamente funcional combinada e integrada con Project 2010. También proporciona una plataforma para Identity Management. Si sabes cómo usar FIM 2010, es muy amigable.

El crecimiento también viene dado por se ha incrementado la adopción en sectores como el sector financiero, petroleras , educación, gobierno y salud.

Obviamente también está el gran trabajo de los vendedores Microsoft haciendo que los clientes se actualicen. Y también la venta de 20 000 nuevos usuarios por dia durante los últimos 5 años. Las empresas empiezan a darse cuenta que el producto ha llegado para quedarse y no demasiada gente sabe realmente cómo manejar o manipular este producto enorme, así que ahora están necesitando gente.

Lo que Sharepoint ha puesto sobre la mesa es más flexibilidad en relación con sus versiones anteriores, que eran difíciles de personalizar y, junto con las licencias de bajo costo se está asegurando la popularidad de Sharepoint.

La sensibilidad y criticidad de los datos de negocio en SharePoint se ha incrementado exponencialmente en los últimos años, en lo que se refiere a seguridad y escalabilidad. A su vez, está obligando a las empresas a establecer governance y equipos de apoyo en torno a su configuración de SharePoint. La nueva inversión es también un reconocimiento del incremento de valor de negocio que SharePoint proporciona a una organización hoy en día en comparación con los años pasados.

Nintex Workflows 2010 para Sharepoint

2010-12-01T19:35:00.000-08:00

Características:

Grafique, no programe
▪ Manejo intuitivo y fácil, función Drag & Drop para diseñar el workflow
▪ Automatiza los procesos de usuarios en cuestión de minutos

Mida y gestione
▪ Vea el workflow en tiempo real
▪ Mida y mejore el rendimiento de la empresa

Diseñe una vez, utilícelo varias
▪ Plantillas y módulos reutilizables
▪ Permite compartir y adaptar las prácticas comerciales entre los equipos de trabajo

Construido sobre SharePoint, para SharePoint
▪ Instalación y administración sencilla, no requiere software cliente
▪ No tiene costos adicionales de Infraestructura

Rápido retorno de la inversión

Quark ahora trae publicación dinámica para más de 100 millones de usuarios SharePoint

2010-10-14T13:18:00.000-07:00

Quark ahora trae publicación dinámica para más de 100 millones de usuarios SharePoint
Quark Publishing System se integra con Microsoft SharePoint 2010 para conectar a los usuarios con departamentos creativos para una más rápida e inteligente comunicación de Marketing

HAMBURGO - 04/10/2010 - Quark anunció hoy que Quark Publishing System ® puede ser integrado con Microsoft SharePoint 2010 para ofrecer a los mas de 100 millones de usuarios de SharePoint en todo el mundo un sistema simple para flujos de trabajo, colaboración y publicación dinámica que se extiende sobre todos los departamentos. Mediante la unión de SharePoint y Quark Publishing System, los usuarios y los departamentos creativos pueden colaborar dentro de un sistema para crear, editar, revisar y publicar comunicaciones compatibles con la marca. Esto permite a las organizaciones en todos los sectores, impulsar el retorno de su inversión de SharePoint mediante la reducción del costo de la publicación de material de marketing, mientras que llegan a públicos con mayor frecuencia, con información precisa y oportuna.
“Mediante la integración de Microsoft SharePoint y Quark Publishing System, Quark busca crear mayor valor para nuestros clientes, permitiéndoles acelerar el desarrollo de contenidos y el ciclo de vida de entrega", dijo Jenni Flinders, vicepresidente de Partner Business Development and Sales group de Microsoft. "La inversión de Quark es indicativo de la innovación fomentado en el ecosistema de Partners de Microsoft y su compromiso de servir a nuestra comunidad de clientes.”
A través de la integración de Quark Publishing System - el motor que permite la publicación dinámica de colaboración - con SharePoint - ampliamente utilizada en Microsoft por la clase empresarial para la coordinación, la comunicación y el intercambio de información en toda la organización - los usuarios pueden reducir los costos de publicación, aumentar la precisión y la puntualidad, eliminar la redundancia, y publicar a través de impresión, Web y multimedia sin problemas. Esta integración se basa en la integración de Quark existente entre Microsoft Word ® y QuarkXPress ®, que permite a los usuarios de Word contribuir y controlar el contenido en los diseños de QuarkXPress.

Publicar directamente desde Word a múltiples medios: prensa, Internet, Digital

"En la mayoría de las organizaciones, los trabajadores del conocimiento y los equipos de publicación desperdician un tiempo valioso y recursos tratando de colaborar con herramientas y procesos ineficaces. Las actividades críticas, tales como la gestión de proyectos, creación de contenidos, y revisión de publicaciones comprenden enorme esfuerzo manual y coordinación. El dolor es compartido por todos - estas deficiencias afectan tanto a los trabajadores del conocimiento como a los equipos de edición, "dijo PG Bartletta, Vicepresidente Senior de Gestión de Producto de Quark. "La solución que hemos desarrollado con Microsoft ofrece a las organizaciones una plataforma de publicación que permite la colaboración completa, dándole lo que expertos en la materia una forma de auto-publicación – trabajando con Word y produciendo impresiones, Web y contenidos digitales - y ofrece a los equipos creativos una solución automatizada para la gestión de activos de marca."

Beneficios para los Knowledge Workers y los Departamentos Creativos

Ahora pueden trabajar juntos mediante el aprovechamiento de SharePoint como un único repositorio para la gestión de contenido y colaboración durante el uso de Quark Publishing System para participar directamente en el proceso de publicación.

La solucion integrada lo hace facil para los knowledge workers, como:

· Crear, editar y copiar el contenido directamente en diseños de QuarkXPress
· Agregar imágenes al diseño a través de un editor Web dentro de la interfaz de usuario de SharePoint
· Crear y actualizar el contenido en Microsoft Word que se refleja automáticamente en los diseños de QuarkXPress
· Inicie la generación de impresión, Web, interactivo, y salida digital
· Búsqueda de documentos en miniaturas y vistas previas de los diseños

Los equipos creativos y usuarios asociados más cerca del proceso de publicacion, pudiendo:

El uso de SharePoint como repositorio de todos los activos utilizados en el proceso de producción, independientemente del formato de salida
Asignar recursos, asignar tareas, y comunicarse usando la funcionalidad de SharePoint
Continuar trabajando en las herramientas de escritorio familiares que son productivas utilizando, QuarkXPress, Adobe ® Creative Suite y Microsoft Office

Para obtener más información acerca de la integración de Quark Publishing System con SharePoint, visita http://dynamicpublishing.quark.com/qps/sharepoint.html. Quark y Microsoft ya están disponibles para discutir cómo esta solución integrada puede ayudar a las empresas a mejorar la creación y producción de materiales de marketing.

Quark es un Microsoft Gold Certified Partner, ganador del Premio Office Solution Builder, y miembro del Consejo Asesor de Desarrolladores de Microsoft Office 14. Además de la integración de Quark Publishing System con SharePoint, Quark y Microsoft colaboran también para integrar Quark ® XML Author con SharePoint para permitir la creación y gestión de contenido estructurado.

Para acceder a un paper de PG Bartlett llamado "Reducción de la brecha entre trabajadores del conocimiento y la publicación de Equipos", vista http://dynamicpublishing.quark.com/qps/sharepoint_information.html

Visual Sandbox Web Parts

2010-08-09T04:55:00.000-07:00

Una de las quejas sobre las soluciones Sandbox es que no se puede crear una web part como solución Sandbox. La razón de esto es la manera en que Visual Studio implementa la web part y que utiliza el método de Page.LoadControl para cargar el control del usuario que representa la web part. Requiere acceso al file system para conseguir el archivo ASCX, después compila el ASCX y la devuelve como un nuevo tipo. Hay una cantidad de maneras de resolver el problema de crear una web part, incluyendo la compilación del ASCX y referrenciarlo en la solución Sandbox. Sin embargo, hay una manera más fácil que haciendo todo este trabajo. Hay un esfuerzo de la comunidad de construir las herramientas para SharePoint en Codeplex. Las herramientas disponibles en Codeplex incluyen una plantilla para las web parts dentro de una solución Sandbox. Se pueden descargar estas herramientas de las siguiente URLs: http://sharepointdevtools.codeplex.com/ y http://cksdev.codeplex.com/.

( SharePoint 2010 + OCR + Tiff + iFilters ) o Busquedas de textos en imágenes

2010-08-06T19:57:00.000-07:00

( SharePoint 2010 + OCR + Tiff + iFilters ) o Busquedas de textos en imágenes

Una buena noticia es que el TIFF iFilter disponible en Windows Server 2008 y 2008 R2 permite buscar textos en documentos .tiff escaneados, esto es porque hace OCR on the fly
Como configurarlo:
Agregar la feature TIFF feature al server que indexa.
Agregar el rol de Windows 2003 indexing al servidor que indexa.
Comenzar el servicio de indexing en el servidor que indexa.
Habilitar TIFF OCR scanning a traves de la group policy en el servidor que indexa:
gpedit.msc
Local Computer Policy –> Computer Configuration –> Administrative Templates –> OCR
Y muy importante: Hacer REBOOT del server o Restart del service de SharePoint 2010

A partir de ahora van a poder tener reconocimiento OCR de los archivos .tiff.

Sharepoint Certified x 4

2010-07-06T07:27:00.000-07:00

I got my fourth Sharepoint Microsoft Certified Technology Specialist (MCTS).

Now I am certified in:

Sharepoint 2010 - Upgrades -Supported Paths In-Place

2010-06-23T06:15:00.000-07:00

When you plan your upgrade process, make sure that you verify that the upgrade path you want to pursue is supported.

Although Upgrade in place could not be the most common scenario, here are the steps you need to do for an upgrade to Sharepoint 2010.

For more info visit Review supported and unsupported upgrade paths (SharePoint Server 2010)

Sharepoint 2010 Enterprise Edition Features

2010-06-08T11:06:00.000-07:00

Sharepoint 2010 Enterprise Edition

These are the Enterprise Edition features.

• Access Services
o Publish Access databases in SharePoint.
• Advanced Content Processing
o Extract and create metadata from documents to improve search results, sorting capabilities, and refinement.
• Advanced Sorting
o Sort results based on Managed Properties or Rank Profiles.
• Business Data Integration with the Office Client
o Interact with external business data directly within the familiar user environment of Microsoft Outlook, Microsoft Word, and Microsoft SharePoint Workspace
• Business Data Web Parts
o Create unique business applications and display information from line-of-business systems using Business Data Web Parts.
• Business Intelligence Center
o Use the examples in this dedicated SharePoint site template to help you get started with your Business Intelligence projects
• Business Intelligence Indexing Connector
o Browse Excel workbooks and Reporting Services Reports with improved results, descriptions, thumbnails, and refiners. Discover your Business Intelligence assets quickly and easily, browse the document and its behind-the-scenes data, and access the information you need quickly and easily
• Calculated KPIs
o Create powerful key performance indicators (KPIs) derived from multiple data sources. Sample templates enable the creation of KPIs quickly and easily using a powerful new expression editor.
• Chart Web Parts
o Choose from a wide range of chart types to create advanced visualizations using the data in SharePoint, including SharePoint Lists, Business Connectivity Services, or Excel Services. A simple wizard guides you through the creation of charts empowering you to create your own dashboards quickly and easily.
• Contextual Search
o Tailor different results and refinement options based on the profile of the user or audience
• Dashboards
o Create rich dashboards that convey the right information the first time, aggregating content from multiple sources and displaying it in a Web browser in an understandable and collaborate environment. Rich interactivity lets you to analyze up-to-the-minute information and work with the data quickly and easily to identify key opportunities and trends.
• Data Connection Library
o Easily share, manage, and discover data connections by centralizing Office Data Connections (ODCs) in Data Connection Libraries. Access data you need while IT centrally manages the connections and underlying data sources.'
• Decomposition Tree
o Perform root cause analyses using powerful analytics to examine core data. View only the most pertinent information using the new Decomposition Tree
• Deep Refinement
o See the exact number of documents that match each refinement option in a result set.
• Excel Services
o Publish Excel workbooks as interactive reports or dashboards. Create rich business experiences with the new JavaScript Object Model, and use the new REST API to easily embed workbooks in other applications. Reuse content in SharePoint dashboards with the new features of Excel 2010 (including Sparklines and Visual Slicers).
• Excel Services and PowerPivot for SharePoint
o Publish Excel workbooks with PowerPivot as interactive reports and dashboards within SharePoint. Schedule and refresh your PowerPivot-enabled Excel workbooks and use a rich management dashboard to monitor and manage the workbooks across your SharePoint farm.
• Extensible Search Platform
o Meet your company^s complex search needs with an extensible search platform. Build search-driven applications, including 360° Customer Insight applications, Research and Development portals, and Product Support dashboards.
• Extreme Scale Search
o Search billions of documents while maintaining sub-second query times.
• InfoPath Forms Services
o Create rich electronic forms to quickly gather information. Use Microsoft InfoPath to build form-based SharePoint applications and advanced forms that connect to line-of-business systems.
• PerformancePoint Services
o Access the information you need when you need it with interactive dashboards and scorecards. Easily analyze root causes and make effective decisions by using new features like the Decomposition Tree, visualizations, and improved filtering.
• Rich Web Indexing
o Index dynamic Web content and JavaScript with a highly customizable indexing connector.
• Similar Results
o Find results that are similar to your search query.
• Thumbnails and Previews
o Recognize the right content quickly with thumbnail and preview images in your search results.
• Tunable Relevance with Multiple Rank Profiles
o Build rank profiles to define customized ranking algorithms. Blend multiple rank ingredients--including content freshness, authority, and quality--to return the right results.
• Visio Services
o Publish Visio 2010 diagrams to SharePoint 2010 to let your people view and refresh diagrams in a browser without opening Visio. Integrate diagrams into other SharePoint applications and develop rich mash-ups.
• Visual Best Bets
o Return rich, editorialized results for specific search keywords using Visual Best Bets. Target content to specific groups of users by associating Visual Best Bets with User Context.

Includes Foundation and Standard Features

Take a look at this comparison.

Massive Copy from file system to Sharepoint 2010 Library

2010-06-04T12:55:00.000-07:00

Use copy command on a command prompt or PowerShell.

For example you can use:

copy \\host\share\folder\*.* \\SharePointHost\Site\Doclib

Your \\SharePointHost value can be \\ComputerName or \\ComputerName.com, etc., just convert the URL to a UNC address; you have to watch out for special characters where you'll have to use escape codes. i.e. %2F, instead of blank spaces and special characters.

PowerShell might be useful in changing your file names to eliminate illegal characters in SharePoint file names; for example, on the web you can't upload a file with an ampersand or a question mark in its name

Announcing Facebook as 2010 TopCoder Open Sponsor (and they're hiring)!‏

2010-04-19T14:54:00.001-07:00

Facebook is excited to be a part of the 2010 TopCoder(R) Open!
Facebook is also looking to hire the best TopCoder members for both full time and internship positions.
Let us know if you're interested. We'd love to meet you to talk more about some of the awesome engineering opportunities we have.
http://www.topcoder.com/tc?module=Static&d1=tournaments&d2=tco10&d3=overview&d4=sponsor2
Facebook is built by a relatively small group of the smartest engineers, hackers and entrepreneurs who each have a huge impact on the 400+ million people that use Facebook around the world. We work in small teams, so every Facebook engineer is responsible for more than one million users, a ratio that is 10-30 times greater than other technology companies.
We are constantly challenged to scale quickly and efficiently, and have some of the best engineers working together to solve today's toughest technical problems.
Help develop the second most-trafficked site and one of the largest MySQL installations in the world.
Build with PHP, C++, Python, Java, Erlang, and even a little bit of ML.
Hack on open source infrastructure technologies to support the site's growth including HipHop for PHP, Cassandra, Hive, Scribe, and Thrift.
Enhance our custom-built search engine that serves millions of queries a day.
Grow Facebook Platform, one of the world's most advanced social platforms.
At Facebook, we move fast. Our rapid development cycle is supported by tools that always keep us operating ahead of the curve. Our engineers are able to write code and have it running live on the site that same night - see the impact you're making in real-time.
Best of luck in competitions leading up to the 2010 TopCoder Open Finals and we hope to see you there!
http://www.topcoder.com/tc?module=Static&d1=tournaments&d2=tco10&d3=overview&d4=sponsor2
Learn more about the TCO10 here: http://www.topcoder.com/tco10
- Facebook and the TopCoder Competitions Team

Office Talk Sharepoint 2010 Awards

2010-04-16T14:11:00.001-07:00

It's SharePoint Awards Winners 2010

So here are the Winner and Runner-up in each SharePoint category. These companies will all be receiving a special ‘Seal of Approval’ in the next ten days.

1. BEST SHAREPOINT INFORMATION SITE
Winner - EndUserSharePoint.com
Expert Comment – A great site written not for developers but for real SharePoint Administrators. It really feels as if they care.
Runner Up - SharePoint Magazine

2. BEST SHAREPOINT WEBPART PROVIDER
Winner - Amrein Engineering
Expert Comment - Very easy to navigate round site. Like the variety of web parts on offer and how they are explained, lots of crowd pleasers in there.
Runner Up - Kwizcom
3. BEST SHAREPOINT ADMINISTRATION TOOL 2010
Winner - ControlPoint (scored a perfect 10)
Expert Comment - Hands down the best in the industry. Very user friendly. Extremely strong permissions reporting capability – the top requirement for managing large farms as 80% of all support calls come from permissions management.

Runner Up - DocAve Administrator
4. BEST WEBSITE BUILT ON SHAREPOINT 2010

Winner - Chilis
Expert Comment - The most fun site I have seen in years! That chalk work is amazing! Great branding.
Runner Up - Swatch

5. BEST SHAREPOINT TRAINING PACKAGES 2010

Winner - Combined Knowledge CBT
Expert Comment – Combined Knowledge continues to lead the way with SharePoint Training. You can tell they understand SharePoint.
Runner Up - CBT Clips
6. BEST SHAREPOINT OFFLINE SOLUTION 2010
Winner - Colligo Contributor (perfect 10 again)
Expert Comment - An all great round solution which is easy to use. They offer more than just Outlook integration.
Runner Up - MyDocs

7. MOST USEFUL SHAREPOINT WEBPART 2010

Winner - Column\View Permissions
Expert Comment - By far the most business benefit – one of the top requests I get on a daily basis. This tool is perfect to resolve that!

Runner Up - Bamboo sharePoint video Library
8. FAVOURITE FREE SHAREPOINT WEBPART/ADD-ONS 2010
Winner - Google Charts
Expert Comment – Making life simple is what we all want and this is what Google Charts does.
Runner Up - Visualizer (Digital Assets)
Expert Comment - Phwooaar, coooool. Very slick. Great way to wow your audience. End users love stuff like this.
9. MOST FUN FREE WEBPART 2010
Winner - Daily Dilbert
Expert Comment – Start your SharePoint with a smile every day.
Runner Up - Hello User
10. BEST SHAREPOINT APPLICATION 2010
Winner - ShareKnowledge – E-Learning Solution
Expert Comment – Brilliant ! Now businesses can really use SharePoint to train their workforce. Great for Health & Safety courses. So easy to design courses as well. Ideal for any size organisation who have SharePoint.
Runner Up - MediaRich Digital Asset Management

So those are the winners but all the finalists offer terrific SharePoint products and I recommend you trial a few yourself.

Open XML SDK 2.0 weird issues

2010-04-16T13:57:00.001-07:00

I was creating and modifying .docx Word files with the Open XML SDK and have got some strange behaviors.

One if them was that I wrote some code to open a blank document and added some Paragraphs with Bold fonts.

Then I opened it with Word and all was ok. I saw my created Paragraph on bold.

The problem was when I tried to open it on another computer. Word told me that the file was corrupted.

So I decided to open it with the Productivity Tool and validate the corrupted file and I got some info like this.

Error description:The element has unexpected child element 'http://schemas.openxmlformats.org/wordprocessingml/2006/main:rFonts'.

Content type of part with error: application/vnd.openxmlformats-officedocument.wordprocessingml.document.main+xml

Location Path.xpath:/w:document[1]/w:body[1]/w:p[6]/w:r[1]/w:rPr[1]

The code I used was something like this:

// Creates an RunProperties instance and adds its children.
public RunProperties GenerateRunProperties()
{
    RunProperties runProperties1 = new RunProperties();
    Bold bold1 = new Bold();
    RunFonts runFonts1 = new RunFonts(){ Ascii = "Trebuchet MS" };
    Color color1 = new Color(){ Val = "000000" };

    runProperties1.Append(bold1);
    runProperties1.Append(runFonts1);
    runProperties1.Append(color1);
    return runProperties1;
}

And when I deleted the Bold , all worked fine.

Someday I’d like to know why this happens…

Perhaps it happens in this CTP version…

Adding a Sharepoint footer (globally)

2010-04-12T08:02:00.001-07:00

GOAL

I recently wanted a portal/sites wide footer for my SharePoint installation. I wanted this to affect the SPS portal and every WSS site without my needing to modify any of the .aspx pages that come with SharePoint.

RESEARCH

I found a great blog article on creating a footer with various means.

danielmcpherson - How To Create A Footer

Read the article and you may come to the same conclusion that the "3. DHTML and Stylesheet" solution is the most compelling, requiring no changes other than style sheet. Unfortunately this technique only works on IE due to HTC.

This effort underway which may help, but I was unable to graft into my scenario:

Scott Galloway - Use HTC within Mozilla!

I was convinced that the DOM script within the HTC was going to ultimately cause an incompatibility, so I scrapped the stylesheet-only idea.

SOLUTION

I ultimately created an HttpModule that I plugged into the site to put a footer on every dynamic page in the virtual directory. This "filter" would look for a </body> tag within any HTML content before it sent it to the user, and inserts my footer code. To make it more "style-sheet like," I decided to insert a javascript reference so that the content of the footer could be maintained by a separate file.

The trick is to create an IHttpModule implementation that installs a customized Stream filter to capture, watch and manipulate the text. Unfortunately stream needs to implement Stream and all it's methods so that you can override the Stream.Write(byte[] data, int offset, int count) as well as optionally Stream.Close(), Stream.Flush() or anything else you want.

I chose to capture all data pushed into Stream.Write(), and modify/output it only on Stream.Close(), with special attention on the destructor to make sure Stream.Close() was actually called.

Interesting excerpts:

public class MyFooterModule : IHttpModule
{
 public MyFooterModule() {}
 public string ModuleName { get { return "MyFooterModule"; } }
 public void Init(HttpApplication context)
 {
  context.BeginRequest += new EventHandler(context_BeginRequest);
 }
 private void context_BeginRequest(object sender, EventArgs e)
 {
  HttpContext context = ((HttpApplication)sender).Context;
  context.Response.Filter = new MyFooterFilter(context.Response.Filter, context);
 }
 public void Dispose() {}
}
public class FooterFilter : Stream {
 public const string FOOTER_HTML = "<script src=\"/Elements/Footer.js\"></script>";
 public const string BEFORE_REGEX = @"</body>\s*</html>";
 protected byte[] mycache = null;
 public override void Close() {
  if (mycache != null) 
  {
   string buffer = System.Text.UTF8Encoding.UTF8.GetString(mycache, 0, mycache.Length);
   Regex regex = new Regex(BEFORE_REGEX, RegexOptions.IgnoreCase);
   Match match = regex.Match(buffer);
   if ((match != null) && match.Success)
   {
    StringBuilder newBuffer = new StringBuilder(buffer.Length + FOOTER_HTML.Length);
    newBuffer.Append(buffer.Substring(0, match.Index;));
    newBuffer.Append(FOOTER_HTML);
    newBuffer.Append(buffer.Substring(match.Index;));
    mycache = MakeByteArrayFromString(newBuffer.ToString());
   }
   BaseStream.Write(mycache, 0, mycache.Length);
  }  
  base.Close();
 }
}

When you get to the installation, consider signing the assembly, and NOT putting it into the GAC, or resorting to setting web.config to Full trust. In the meantime, do whatever it takes to make the following line work in your web.config file:

    <add name="FooterModule" type="MyNameSpace,myassembly"/>
</httpModules>

You will have to put the assembly in the site's bin directory. Also put it into the layouts bin directory if you want to have the footer appear in the _layouts/1033/*.aspx pages.

By installing this footer module into the default web site's web.config file, every portal and site .aspx page will be affected. Making the same modification to the layouts virtual directory will add the footer to the _layouts/1033/*.aspx pages, but some will look undesirable such as the rich text editor. As far as I've found, no pages actually break using this technique the the provided regular expression during content manipulation.

I heard that this type of filtering does not properly adjust the Content-Length header, which should be a problem, but I have not seen any ill effects yet.

This was an old post on MindsharpBlogs that unfortunately is not more online.

Changing fonts with Open XML SDK 2.0

2010-04-07T13:40:00.001-07:00

Take a look at the next code if you need to change or replace the font name or size on paragraphs of a Word Document.

using System.Xml.Linq ;
using DocumentFormat.OpenXml.Packaging;
using DocumentFormat.OpenXml;
using DocumentFormat.OpenXml.Wordprocessing;

private void changeFonts()
{
string myFile = @"\\MySharedFolder\myDoc.docx";

WordprocessingDocument doc = WordprocessingDocument.Open(myFile, true);

//iterate through paragraphs
IList<Paragraph> paragraphs = doc.MainDocumentPart.Document.Body.Elements<Paragraph>().ToList<Paragraph>();

foreach (Paragraph para in paragraphs)
{

                foreach (Run r in para.Elements<Run>())
                {
                        foreach (RunProperties rp in r.Elements<RunProperties>())
                        {
                            try
                            {
                                //t rp is our current RunProperty
                                rp.RunFonts.Ascii = "Arial";
                                FontSize myFontSize = new FontSize();
                                myFontSize.Val = new StringValue("50");
                                rp.FontSize = myFontSize;

                            }
                            catch (Exception ex) { }
                        }
                }
            }
            doc.MainDocumentPart.Document.Save();

}

Que hay de nuevo en las Data View Web Parts de Sharepoint 2010

2010-02-22T10:00:00.000-08:00

Que hay de nuevo en las Data View Web Parts de Sharepoint 2010

La data view web part viene con nuevas funcionalidades dignas de ser revisadas.

Data View Web Parts
SharePoint Designer es la herramienta usada para crear data view web parts.
En este post, se mostraran las nuevas funcionalidades de la data view web part.

La data view web part salva a mas de uno a la hora de mostrar datos de diferentes origenes. Las companias tienen datos dispersos en multiples plataformas aparte de Sharepoint.
Primero sepamos que estas web parts van a ser construidas desde Sharepoint Designer 2010 y que esta version de Sharepoint Designer no es compatible con versions anteriores de Sharepoint.

Paso a Paso

Mas alla que haya nuevos tipos de conexiones como REST Service Connections, vamos a ver mas en detalle funcionalidades que hacen al funcionammiento de la web part.

Demas esta decir que ahora al hacer click en las data view web part , el ribbon contextual muestra una seccion List View Tools. El Panel Data Source Details se muestra hacienda click en Data Source Details en el tab Options. Este panel muestra campos que existen en el data source.

El Ribbon
El Nuevo ribbon va a estar presente en todos los productos Microsoft ahora, y SharePoint Designer 2010 no es la excepcion. “Ribbon” es la terminologia que describe el panel de arriba de todo de la ventana, que contiene barras contextuales.

Fig. 1: Ribbon.

En la Figura 1, las List View Tools se muestrab en la ribbon, que incluye 4 tabs. Estos tabs son Options, Design, Web Part, y Table. Toda la funcionalidad que teniamos en SharePoint 2007 sigue alli. Una de las principales diferencias, es que los seteos son mas faciles de encontrar.

El Tab Options

Este es el tab que vamos a usar para filtrar, ordenar, agrupar, etc. Lo que tenemos de nuevo es que podemos agregar columnas formula como para calcular la suma de dos columnas,etc.

Edicion Inline
Cuando se presiona el boton “Inline Editing”, aparecera una nueva columna a la izquierda de la data view web part. En modo diseño no tendr’a impacto, pero cuando la pagina sea grabada y vista en el explorador, se mostrara el boton “inline editing”. Cuando se hace click en este boton nuevo, los campos de la fila se vuelven editables directamente en la lista. Noten que esta capacidad tambien esta disponible cuando se crea cualquier vista en SharePoint 2010, y no solo esta limitado a la data view web part.
Mostrar List Item Menu
Antes cada menu de opciones de cada item estaba asiociado al campo Title de cada lista. En SharePoint Designer 2010, ahora tenemos la posibilidad de elegir el campo que querramos. Las opciones de esta configuracion se muestra en la figura 2.

Fig. 2:
.

Update Asincronico
Este es un nuevo checkbox llamado update asincronico. Con esta opcion habilitada, los datos se vuelven dinamicos, y los botones Refresh y Refresh Interval estan disponibles. Si el boton Refresh es elegido, un icono se mostrara a la derecha arriba de la web part, para los usuarios que eligen refrescar los datos. El interval de Refresh permite refrescar automaticamente ver la Figura 3.

Fig. 3: Opciones de Update Asincronico.

Folder Scope
Si hay folders en la fuente de datos, podes elegir mostrar los items de los forlders o no

.
El Tab Design
Este tab contiene opciones relacionadas al diseño y format de la data view web part.

Preview
La seccion preview contiene opciones para determiner como se van a mostrar los datos bajo varias circunstancias, como determinar cuantos items de ejemplo se van a mostrar en SharePoint Designer. Algunos items nuevos se pueden ver an la Figura 4

Fig.4: Opciones de Data View Preview
.

‘No Matching Items’ Template
Por default, cuando no hay items en la lista, el siguiente texto se muestra: “There are no items to show in this view of the “ListName” list. To create a new item, click “New” above.”
En una document library, el texto es: There are no items to show in this view of the “LibraryName” document library. To create a new item, click “New” or “Upload” above.
Este template llamado ‘No Matching Items’ nos permite la customizacion cuando no hay items que mostrar. No solo se podra editar el texto, sino la pagina misma, incluyendo imagenes, links, o cualquier customizacion.
Edit Template
Esta opcion solo esta disponible cuando se habilita “inline editing”.
Insert Template
Esta opcion solo esta disponible cuando se habilita “inline editing”.

El Tab Web Part
El Tab web part tab consiste de las propiedades de la web part como se muestra en la Figure 5.

Fig.5: El Tab Web Part.

Save Web Part
La habilidad de grabar una web part es nueva. Cuando se graba una web part “To File”, hay una ventana de dialogo simple para indicar donde grabar el archive .WEBPART. Cuando se graba en la web part gallery, hay una ventana de dialogo para configurar el nombre y descripcion de la web part.
.
Una vez que se hace click en el boton OK para grabarla, hay otra ventana de dialogo preguntando si vamos a mostrar siempre datos del sitio actual o del sitio donde se instale la web part.
Esta opcion nos evita modificar codigo de la web una vez instalada para que funcione.

Otras nuevas funcionalidades

Field Level
Cuando se hace click derecho sobre un campoen la data view web part, hay varias opciones. Las opciones como crear hyperlinks pueden ser hechas mas rapido en SharePoint Designer 2010, lo que significa menos clicks. Como se muestra en la Figura 6, cuando esta opcion es usada se puede crear links a las paginas de New Item, Edit Form, o Display Form.

Fig.6: Formato a nivel Field.

Quick Tag Editor
El Quick Tag Editor es una nueva opcion para rapidamente editar el codigo de un elemento. Seleccionar un item en la pagina, y en el Tab Home de Sharepoint Designer, hacer click en Quick Tag Editor, como se muestra en la Figura 7. Se muestra la porcion de codigo relacionado a la seleccion, con las opciones Edit Tag, Wrap Tag, o Insert HTML.

Fig.7: Quick Tag Editor.

Conclusion

Este es un resumen a alto nivel de algunas nuevas funcionalidades en el momento de usar las data view web parts en SharePoint 2010, usando SharePoint Designer 2010.
En algunos casos usar las data view web parts es muy util. Cuando llegan las limitaciones de esta, el proximo paso es desarrollar una web part custom.

Free SharePoint eMagazine

2010-01-21T11:33:00.001-08:00

Mirjam van Olst (SharePoint MCM and MVP) and myself took the challenge to find authors who are well known in the SharePoint Community, Sponsors who are willing to advertise in this magazine so we could cover the costs and the time to read, review and edit articles next to our busy jobs. Well... the results is this magazine! Over 100 pages with information for SharePoint professionals.
Playing with SharePoint 2010 you can’t help but to get excited about all the new possibilities. Have you looked at Visio Services or the Business Intelligence possibilities with the Chart Web Part? It looks very promising! Or have you been working with data using the SharePoint Designer. Talking about data, what about the enhancements of the Business Connectivity Services (previously known as the BDC). Very awesome! Personally I like the integration of Visual Studio Tools for SharePoint. It’s so easy now to develop, debug and deploy your solutions. But there are so many new things for a developer to look at; the Client Object Model, SandBoxed Solutions, UI Customizations and the Ribbon.
"Out of the Box" is a column on how you can create business solutions in SharePoint by configuring functionality (No Code Solutions). In this issue we look at Project Management with SharePoint.
Special in this magazine is the SharePoint Comic by Dan Lewis... make sure you don't miss it!

SharePoint 2010 Visual Studio 2010 Extensions

2009-12-29T06:16:00.000-08:00

Available for Download (free) at http://spvsx.codeplex.com/
The SharePoint 2010 Visual Studio 2010 Extensions project (SPVSX) is a collection of Visual Studio templates, Server Explorer extensions and tools providing accelerated SharePoint 2010 development based on Microsoft's new SharePoint 2010 development tools.

Sharepoint 2010 Business Connectivity Services (BCS) Primer

2009-11-10T19:50:00.000-08:00

Business Connectivity Services (BCS) Primer

The BCS is actually a platform that provides a SharePoint-based framework for creating composite applications, which are built by combining services and functionality from other enterprise applications to address the collaborative needs of users. These composite applications use the Office client user interface in addition to the functionality of the application. This helps people perform their tasks within the familiar user interface of the Office and SharePoint Server systems, and allows people to take actions and make decisions within the context of the problem at hand.

BCS at Channel 9

Double Certified!

2009-11-05T05:15:00.000-08:00

I got my second Sharepoint Microsoft Certified Technology Specialist (MCTS).

Now I am certified in:

Technology Specialist: Microsoft Office SharePoint Server 2007 – Configuration
Technology Specialist: Microsoft Office SharePoint Server 2007 – Application Development

New contribution to the community on Codeplex - The Sharepoint SPMultifilter web part

2009-08-18T12:13:00.000-07:00

The Sharepoint SPMultifilter web part

http://spmultifilter.codeplex.com/

Overview

The Sharepoint SPMultifilter Web Part is a web part that shows items from a Sharepoint List and such items can be filtered and ordered from a View of the list.
Items are shown on a grid with 5 Columns. Those columns can be filtered on the Sharepoint page without rendering again the whole page, just like an Ajax behavior.
So you can write the letter or word with wildcards and search the item you want on the grid.

Installation

Here you can see the steps so as to install the SPMultifilter web part;

• Firstly you must download the SPMultifilter.zip file to a local folder on your Sharepoint Server
• Expand it.
• Goto the deploy\SPMultiFilter Folder
• Run the deploywithwspbuilder.bat file
• Add the spMultifilter Web Part to your Web Part Gallery
• Edit your page and add the spMultifilter Web Part.

Web Part Attributes

The Sharepoint SPMultifilter Web Part has some attributes so as to render the needed Columns on the grid.
The attributes are:
• List
• View
• Field1
• Field2
• Field3
• Filed4
• Field5
• RowAColor
• RowBColor
The “List” Attribute is used to set the Sharepoint List to be shown on the grid. The items of this list will be filtered and ordered using the “View” attribute. So you can create a new View so be used by this web part and where you can choose your order and filter as you want.
The “Fieldx” attributes are the columns to be shown on the grid and will be the attributes to be filtered on the textboxes placed on the head of the grid, so that you can type letters and filter on-the-fly.
It is very important that Fields chosen on the attribute, exists on the View you have set on the “View” attribute. Otherwise the column won’t be shon on the grid.
The RowAColor and RowBColor attributes are the colors to be shown on the grid rows.

Tips

Filtering

In the next image, you can see 6 items, and if you write the ‘m’ letter on the Title textbox , you ‘ll see only 2 items. The ‘Microsoft and Yahoo’ title and the ‘Michael Phelps’ Title.

Filtering with wildcards

While you are writing letters to filter the grid you can use 2 wildcards, * and !, * makes ignore part of the word to filter. For example if you write *p , you will see 2 items filtered on the grid; you ‘ll see the ´Michael Phelps´ Title and ´Google’s Big Plan for Books´, because those titles contains the ´p´ letter and some another letters before ´p´.

Another wildcard you can use is ! . With this wildcard you will search all items except the ones you are writing. For example if you write !m, you will see 4 items, You ´ll see all items except the ones that starts with ´m´.

Special Columns
Also there are 2 special columns that doesn’t use the filtering functionalities. They are just to have a more user friendly grid.
URL Columns
You can choose a URL type column so that will be rendered on the grid as a Link to the content you have on the item.
This link can be opened on the same browser window or in a new broser window or in a frame. You just need to have a column named target on your “View” and set its value as “_window” or “_blank”.

Edit Columns
Another special column on the grid is the “Edit” Column. This type of column can be used so that you can edit an item from the grid as usual Sharepoint Webparts. Just set one of the “Fieldx” attributes with the word “Edit” and you will see an icon so as to edit the item.If you use this option, you must add the ID field in your View.

Comments
This web part can solve you access to links easily filtering by any column.
Note that it will render items depending of a view, so it is recommended to show all items of a list on the view without paging it, but taking care of performance of the page that will contain the web part.
Contact
If you need new functionalities you think are useful on this web part please contact to Fernando Hunth ( fhunth@hotmail.com ) or post it on the Codeplex project http://spmultifilter.codeplex.com/

SE SUBE LA CORTINA (UN POCO) DE SHAREPOINT 2010

2009-07-13T16:48:00.000-07:00

Hoy en la Worldwide Partner Conference (WPC) en Nueva Orleáns, Microsoft subió la cortina de SharePoint 2010, revelando por primera vez, oficial y públicamente, algunas de las features y direcciones de la próxima versión de SharePoint, que se publicará en el primer semestre de 2010. Con enorme cautela, el equipo del producto SharePoint deja asomar el sol e invitó al mundo a unirse a Conferencia de SharePoint en octubre para ver el resto de lo que hay detrás la cortina.

Dicen que: Vas a querer actualizarte a SharePoint 2010. Esto no va a ser como la debacle de la percepción de Windows Vista o el "gran salto de formación" de Microsoft Office 2007. Esto va a ser una enorme cantidad de nuevas funcionalidades, capacidad, y valor que absolutamente mejorara casi todas las implementaciones SharePoint, por no hablar de la vida de los usuarios de SharePoint, los administradores y desarrolladores.

Dicho esto, lamentablemente, no vas a aprender todo lo que hay que saber acerca de SharePoint 2010 todavía. La Punta que reveló hoy Microsoft pone de relieve sólo unas docenas de importantes mejoras, hay más por venir…
Algunas de las características que más entusiasman:

• Toda la experiencia del usuario final es mejor. La tecnología carece de valor si no es adoptada, y la nueva interfaz de usuario de SharePoint es acelerara la adopción. Va a estar basada en Ribbons (aunque se puede ocultar), la interfaz asíncrona que le permite hacer en uno o dos clics, en una sola página, lo que muchos clics a través de muchas páginas para lograr v3/2007 en SharePoint. La nueva interfaz de usuario de SharePoint es simplemente mucho más productiva e intuitiva. Y los usuarios no se limitarán a Microsoft Internet Explorer (IE) . Firefox, Safari de Apple, y "otros navegadores" serán soportados también. El "look and feel" y el contenido de un sitio puede ser fácilmente modificado a través de características tales como Rich Theming y Web Edit, el cual le permite editar cualquier parte de cualquier página, en su lugar y WYSIWYG como un Wiki sobrecargado.

• Los datos van a estar en interacción con nuevas formas. Tanto si se trata de datos de SharePoint o datos en el back-end de las aplicaciones y bases de datos, todo se muestra como una lista de SharePoint, gracias al Business Connectivity Services (BCS), la evolución de los Business Data Catalog.. Y, muy importante, ya no es una calle de sentido único. BCS lecturas y escrituras! Pero no termina ahí. Los datos pueden ir a través de SharePoint directamente en las aplicaciones de Office como Microsoft Word, que pueden consumir e interactuar con la lista de datos que-es-realmente-back-end de datos. Y puede tomar todo fuera de línea para lectura y escritura mediante la sincronización de trabajo de SharePoint usando SharePoint Workspace, la versión recargada de Groove 2010. Hablando de SharePoint Workspace y fuera de línea, todo lo que se necesita fuera de línea: listas, bibliotecas, BCS datos ... es increíble!
•
SharePoint 2010 ofrece el apoyo de medios enriquecidos. Ahora puede hostear vídeos con eficacia, puede incorporar Microsoft Silverlight con un built-in web part Silverlight, y puede proporcionar la interacción con clientes Office!
•
También llega Visio Services. Al igual que Excel Services permite a los usuarios visualizar e interactuar con datos de Excel en un navegador sin una instalación local de Excel, Visio Services hace lo mismo para los diagramas de Visio. Pero, por supuesto, Visio es una aplicación que los usuarios tienen mucho menos instalado localmente en el primer lugar, por lo que el impacto será mucho mayor. El ejemplo de Visio Services aprovechando back-end de las fuentes de datos y la creación de diagramas dinámicos fue súper impresionante.
Todas esas cosas proporcionará valor del negocio y conducira la adopción. Pero ¿qué ocurre con aquellos que tienen que administrar y soportar SharePoint 2010? Para un administrador de SharePoint, lo siguiente va a ser emocionante:

-Administración Central, se ha revisado y tiene un mucho más limpio, más productivo, y más intuitiva interfaz con muchas nuevas funciones . Varios nuevos informes, también!
-Con una tecnología tan compleja como SharePoint, cada administrador apreciara el Best Practices Analyzer, que ayudará a identificar problemas potenciales antes de que se conviertan en verdaderos dolores de cabeza.
-Una limitación importante en SharePoint v3/2007 es la escalabilidad de las listas y las bibliotecas, que a causa de la performance tuvo algún ajuste de rendimiento en más de 2.000 items. Las grandes listas (con millones de items) y bibliotecas volveran, y SharePoint proporciona muchas maneras para la gestión de listas y su impacto de rendimiento en la base de datos.
-Las Ribbons mencionadas anteriormente son nuevas. Si bien puede estar oculta. SharePoint 2010 tiene una función de actualización visual que permite mantener el antiguo aspecto y tener un preview hasta que esté bien y listo. Puedes previsualizar el efecto de la actualización para asegurarse de que nada se rompa!
•
Y, por último, para los desarrolladores, todo se trata de Visual Studio 2010 SharePoint Tools, que sin duda hara tareas necesarias para desarrollar de manera eficaz para SharePoint. También habrá un lenguaje de Queries integrado (LINQ - un modelo de objetos de cliente), el anteriormente mencionado BCS y Silverlight Web parts, y, el developer dashboard, que puede exponer información de depuración en cualquier página de SharePoint. 

Estas mejoras son, como reiteradamente se hace hincapié Microsoft, sólo la punta del iceberg! Hay mucho más escondido fuera de la vista, y Microsoft quiere que el mundo asista a la Conferencia de SharePoint para verla.

Visio Human resource solutions

2009-07-10T13:05:00.000-07:00

You strive to improve the overall efficiency of your organization while adding to the bottom-line value. You are seeking solutions that will enable you to...

.Quickly identify, respond-to and manage change
.Improve recruiting, training and retaining employees
.Deliver high value programs and tools to employees
.Provide cost effective and efficient communication
.Automate and simplify processes and workflows

Take a look at Microsoft Visio Toolbox

Social Sharepoint at Electronic Arts

2009-06-25T11:34:00.000-07:00

Electronic Arts (EA) is a leader in entertainment software, producing some of the world’s best-known games including The Sims and Medal of Honor. To stay on top in a highly competitive industry, EA must drive a rapid and increasing pace of product development. At the same time, the company works hard to maintain a creative, people-focused culture. As EA grew to thousands of employees and offices around the world, it became challenging to share ideas and expertise across the organization. It also grew more difficult to integrate new employees into the company’s distinctive culture. EA developed a solution called EA People based on Microsoft® Office SharePoint® Server 2007. Starting with the core functionality of the platform, EA heavily customized the user interface to make the most of the distinctive culture and skills of EA.

Employees can quickly find colleagues with needed expertise or experience, reducing the need to duplicate work.
Communities for new hires help them find connections and information they need to become productive more quickly.
Features like the ability to post personal information and images on My Sites and see where colleagues are in the organization lend to social cohesion, enhancing employees’ ability to work closely together even when they are physically remote.

Sharepoint Social Computing

MOSS 2007. The smallest server farm for a company (In my opinion)

2009-06-22T07:39:00.000-07:00

The smallest server farm that builds in redundancy consists of four servers:
• Servers 1 and 2: Web servers and query role installed on both computers. Additional application server roles, such as Excel Calculation Services, can be installed on one or both servers.
• Servers 3 and 4: clustered or mirrored database server.

With a four-server farm, you must carefully choose where to deploy the index server role. The query role cannot be deployed to both the index server and another server in the farm to achieve redundancy. This is because, when the index role is installed on the same server computer as the query role, the index role no longer propagates content indexes to other query servers. Consequently, if you install the index server role to one of the Web servers, you lose the ability to host the query role on both Web servers. You can install the index role on the database server, achieving redundancy of the query role on the Web servers. However, the performance of the database server will be affected, particularly when content is being crawled.
Additional application server roles, such as Excel Calculation Services, can be installed on one or both Web servers, depending on performance and availability requirements. In the previous diagram, additional application roles are deployed to only one of the servers in both Option A and Option B.
In Option A, performance is optimized if the Web server that is not hosting the combined index and query roles hosts the other application roles.
In Option B, the topology is optimized for user requests and queries. Performance of the other Web server

Sharepoint birthdays List on Codeplex

2009-05-27T12:33:00.000-07:00

Today i have posted my first Codeplex project.
It 's a simple but useful feature.
It about showing birthdays on a Sharepoint (WSS & MOSS) Site

I based this list on a post

Here below there is the post I based my Sharepoint birthday List

As It didn't work as is, I decided to post it working on Codeplex.

_____________________________________________________________________________________

This web part is a very simple but handy part to show coming birthdays of people. You only use standard controls from SharePoint and you do not have to program anything. It also shows how to use some functions which are not directly available in calculated fields but can be used with a simple trick. so far as I know this trick be used for any other function which is not available for calculated fields. The following describes the steps to create this web part.

Choose "Manage Content" from the "Actions" menu. Choose "Create" and create a custom list. Choose "Modify settings and columns" and add the following columns:

Name, single line of text
Birthday, Date and Time

The Trick: You can not use the Today function directly from the calculated field. So we create a dummy column representing the Today function. The credits for this trick are going to Pete Blair.

Today, single line of text

Next we have to create two calculated fields. The first calculated field tranforms the day of birth to a date in the current year. This means that may 19th, 1971 will be may 19th, 2005.

BirthDayThisYear, Calculated, =TEXT(BirthDay,"M/D/")&TEXT(Today,"YYYY")

the second calculated field will calculate the number of days till that date.

BirthDayIsSoon, Calculated, =DATEDIF(Today,BirthDayThisYear,"d")

Now remove the Today column. The calculated fields will use the actual Today function in stead of the Today column. Make sure that whenever you want to change the calculated fields the Today column is created

Create a new view which will only show the columns Name and Birthday. In this view use the following filter settings showing only the birthdays in the next 14 days.

Commerce Server Marketing Manager while approving

2009-05-13T12:30:00.000-07:00

I had created a new Direct Mail and when I tried to Approve it I got the next error message.

Commerce Server Marketing Manager while scheduling this direct mail (id = 1)

It happened that the Commerce Server Direct Mailer Service was off.

I trie to Start it but

I receive an error message when Commerce Server 2009 is installed on a computer that is running Windows Server 2008 64 bit

Windows could not start the Commerce Server Direct Mailer service on Local Computer.
Error 1075: The dependency service does not exist or has been marked for deletion

I tried this

http://support.microsoft.com/kb/949745

But It does not work

Commerce Server Authorization Manager

2009-05-13T06:39:00.000-07:00

To add users to the authorization roles
Click Start, click Run, type azman.msc, and then click OK.

In the Authorization Manager screen, right-click Authorization Manager, and then click Open Authorization Store.

In the Open Authorization Store dialog box, verify that the XML file option is selected, and then click Browse to locate the authorization policy for the Web service. For example, the catalog authorization policy XML file is located at \Inetpub\Wwwroot\ssCatalogWebService.

Select .xml, and then click Open.

In the Open Authorization Store dialog box, click OK.

Expand the authorization policy to \.xml\\Role Assignments\. For example, \CatalogAuthorizationStore.xml\CatalogandInventorySystem\Role Assignments\CatalogAdministrator.

Right-click , and then click Assign Windows Users and Groups.

In the Select Users, Computers, or Groups dialog box, in the Enter the object names to select box, type the name of the catalog administrator Windows group that you defined in the previous procedure, for example, ssCatalogAdminGroup. Alternatively, you can also type the name of an individual business user account. Click OK.

Repeat steps 2 through 8 for each authorization role in each Web service authorization store. When complete, you will have defined the following:

Daemon Tools Lite

2009-01-08T11:10:00.000-08:00

I use to use Daemon Tools Lite to get image files like .iso files

Sharepoint web parts for Commerce Server

2008-12-01T11:45:00.001-08:00

The following table lists the Web Parts in the CTP release.

Catalog System

Site Map Provider
Product Provider
Property Picker
Product Details
Product Filter
Product Query
Image Viewer

Profiles System

Address List
Address Detail
Credit Card List
Credit Card Detail
My Profile
Registration Wizard
Change Password
Live ID

Orders System

Add to Cart
Cart
Checkout
Minicart
Order History
Order Details
My Shopper Lists
Shopper List Detail

Marketing System

Advertisement List
Channel Configuration Feature

Search Box
Search Results
Search Paging
Store Locator (Virtual Earth)

Mojave available

2008-11-12T10:00:00.000-08:00

The Commerce Server team is pleased to announce the availability of the Microsoft Commerce Server 2007 code name "Mojave" October CTP. This is the first public release of our next Commerce Server offering.

This CTP includes the first of two key additions to Commerce Server: the new multi-channel commerce foundation. This new run-time API adds new out-of-box functionality, adds pervasive multi-channel awareness, and unifies the run-time calling model across all subsystems.

The next CTP will provide the second key addition: a contemporary, default production-ready out-of-the-box site using Web Parts running in SharePoint, and other SharePoint commerce services.

The October CTP currently includes the web parts only as SharePoint Solution Services files (.WSP), requiring site assembly.

To receive the October CTP, click this link, to review and accept the EULA. You will receive an email with the link to the download package. Note that this CTP is a pre-beta release that is not feature complete and requires some manual setup. This CTP currently includes the API and Web Parts for review and assembly of sites. It is strongly recommended that you consult the readme file associated with the download for information about installing and setting up the October CTP.

Please use the Connect feedback system to provide feedback about the October CTP. Thank you.

The final Commerce Server 2007 code name “Mojave” Community Technology Preview (CTP) will be available in the November 2008 time frame. It will be feature complete, and will have the full multi-channel commerce foundation in it, as well as the default out-of-the-box site using the ASP.NET web parts in SharePoint, along with other SharePoint commerce services.

Commerce Server 2007 targeting ads

2008-11-04T05:30:00.000-08:00

I was researching about targeting ads on Commerce Server 2007.

I spent some days trying to generate new ads so as to target for example a registered user and a public user, just to make a basic proof concept, so I generated a targeted ad for a registered user creating a new expression and then used the "Refresh Cache" Link button, but I never got my desired result on the Starter Site Pages.
It happens that there are some cache configurations that helped me so as to solve this problem during the proof concept, so if you modify this king of configuration to refresh cache in 1 second you 'll see your desired ad

Sample Configuration
cache name="Advertising" type="Advertising" refreshInterval="1" retryInterval="1"

I really dont know if the Refresh Link on the Marketing Manager is not working ok, or I am not understanding something on Commerce Server 2007, but this change on the configuration could help you.

Sharepoint 2003 timeouts

2008-07-24T10:35:00.001-07:00

This is just a memory note for me.

On an old project, building a web part, it had many process time, and i got timeout problems.

They were solved with some configurations:

on web.config

WebPartWorkItem with a value set to 7000

on machine.config

httpRuntime executionTimeout = 90

The Risks of Rolling Out MOSS without Extranet Capability

2008-07-01T13:38:00.001-07:00

That's an interesting white paper from Epok

Microsoft Office SharePoint Server 2007 (MOSS) is
on its way to becoming as important in enterprise
computing as Microsoft Windows and Office. Kyle
McNabb of Forrester Research describes the results
of his extensive surveys as "current MOSS adoption
is pervasive." Many businesses (more than 60%
according to McNabb) are using MOSS to provide
basic content management services to their users.
This is just the beginning. According to Bill Gates,
"The spectacular growth of SharePoint is the result of
the great combination of collaboration and information
management capabilities it delivers. I believe that the
success we've seen so far is just the beginning for
SharePoint."
Indeed, SharePoint use continues to expand within
organizations driven by business users, IT staff, and
information security officers who are all looking for
better ways to collaborate and control information
access and use. Business users striving to create
more agile and cost effective operations are quick to
realize the value of SharePoint for communicating
and collaborating with other divisions, partners and
extranet users. As a result, most MOSS 2007
deployment plans must include some form of extranet
support to meet the demands of business users.
Unfortunately, MOSS is optimized as a workgroup,
single directory collaboration suite, which limits the
utility and value in cross-organizational collaboration.
IT developers charged with deploying MOSS
extranets have struggled to design and implement
such projects. Those responsible often end up using
toolkit technologies like the External Collaboration
Toolkit for SharePoint (ECTS) built on Active
Directory Application Mode (ADAM) to roll their own
“one off” solutions from piece-parts. Faced with
limited product options and complex do-it-yourself
approaches many organizations defer addressing
extranet exposure of SharePoint until “later”. This can
be a costly mistake.
Delayed extranet planning and deployment can be
a serious mistake that leads to excessive license
fees, costly redesign and disruption of your
network, degraded security and compliance, and
more costly management of internal and external
users.
As a result, MOSS 2007 deployment plans need to
include an architecture that can quickly and
seamlessly support extranet needs. When the time
comes to activate extranet use, it should simply be a
matter of turning it on, not redesigning your MOSS
infrastructure.

MOSS and Extranets: Planning for the Inevitable

In rolling our MOSS, some best practices to
consider are:
- Segregate extranet users from corporate AD
users to make management of the external
users easier.
- Tie external user access to the business
agreements and regulations that govern access
rights (such as Non-Disclosure Agreements and
other legal documents that outline obligations,
terms and conditions for extranet users).
- Provide a unified view of all your MOSS sites
and how they are exposed to extranet users.
- Foster business manager ownership and
administration of extranet access: MOSS has
business users administering corporate users,
extend that same approach to external users to
optimize agility and to let stretched IT resources
focus on system and security administration, not
business relationships.
- Support your compliance and information
assurance processes by tracking system access
and information use across all external users
In summary, organizations should roll out MOSS
2007 with extranet capabilities ready to go to from
the beginning to avoid the pitfalls of a delayed
implementation. Companies like Epok provide
powerful MOSS solutions for extranet management
with linkage to compliance and security demands
and, provide a ‘walk before you run’ solution that
scales to meet enterprise requirements.
.
-Author: Kristofer Younger, Chief Technology Officer of Epok, Inc.

Some useful references about Sharepoint 2007 Scalability and Performance

2008-06-24T11:53:00.001-07:00

References

Scaling SharePoint 2007: Storage Architecture

The purpose of this white paper is three-fold. First, this document is intended to provide prescriptive guidance targeted at the storage subsystem for a highly scalable Office SharePoint Server 2007 implementation in order to facilitate architectural planning. Second, it is intended to provide techniques for monitoring scalability metrics for existing SharePoint implementations. Finally, it provides techniques for modifying the storage architecture of Office SharePoint Server 2007 systems that are suffering from poor performance due to the fact that the I/O burden on the storage subsystem has exceeded its capability.

(http://go.microsoft.com/fwlink/?LinkId=119399&clcid=0x409)

Evaluation Guide for Office SharePoint Server 2007

This evaluation guide is designed to give you a solid understanding of the design goals and feature set for Office SharePoint Server 2007 and a familiarity with the product implementation. It provides an overview of the solutions and benefits provided by Office SharePoint Server 2007, along with descriptions of new and improved features in the areas of portal, search, content management, business forms and integration, and business intelligence. It also provides a hands-on tour of the product's main feature areas and concludes with useful information for administrators and developers.

(http://go.microsoft.com/fwlink/?LinkId=119400&clcid=0x409)

Determine Hardware and Software Requirements

An installation of Office SharePoint Server 2007 can range from a single computer (stand-alone installation) to many computers (server farm). The requirements for your installation will depend on the availability and scaling requirements for your solution. This article describes the minimum and recommended hardware requirements based on whether you are deploying a stand-alone installation or a server farm. This article also lists the software prerequisites for installing Office SharePoint Server 2007.

(http://go.microsoft.com/fwlink/?LinkId=119403&clcid=0x409)

Planning Recommendations for Web Servers

Plan your Web servers by using the recommendations in this article to enhance system performance.

(http://go.microsoft.com/fwlink/?LinkId=119411&clcid=0x409)

Configure a Dedicated Front-End Web Server

Configure a dedicated front-end Web server for crawling (Office SharePoint Server 2007). Front-end Web servers are used by Office SharePoint Server 2007 to crawl content in SharePoint sites within your server farm. They are not used to crawl content that is external to your server farm, such as SharePoint sites in other server farms, Exchange Public folders, or file shares. Content that is external to the farm is accessed directly by the index server, without the need for the front-end Web server.

(http://go.microsoft.com/fwlink/?LinkId=92660&clcid=0x409)

Physical Topology Recommendations

The topology of your system's database tier, and your network, physical storage, and caching can significantly affect system performance. When you plan your hardware, remember that Office SharePoint Server 2007 is the last version of Office SharePoint Server 2007 that will run on 32-bit operating systems and databases.

(http://go.microsoft.com/fwlink/?LinkId=119415&clcid=0x409)

Physical Storage Recommendations

The disks and arrays you choose — and how you place data on those disks and arrays — can significantly affect system performance. If you are unfamiliar with Redundant Array of Independent Disks (RAID), see the following resources:

(http://go.microsoft.com/fwlink/?LinkId=119416&clcid=0x409)

Planning and Monitoring SQL Server Storage for Office SharePoint Server 2007: Performance Recommendations and Best Practices

This paper provides key recommendations and best practices to help administrators of SharePoint Products and Technologies to plan and monitor their SQL Server storage requirements to support optimal performance and operation of their server farms.

(http://go.microsoft.com/fwlink/?LinkId=119398&clcid=0x409)

Database Maintenance for SharePoint Products and Technologies

This white paper provides information and guidelines for maintaining the databases that host Microsoft SharePoint Products and Technologies data and configurations. It describes and provides examples of the database maintenance tasks that we recommend when using SharePoint Products and Technologies.

(http://go.microsoft.com/fwlink/?LinkId=117910&clcid=0x409)

Stsadm Operations

The articles in this section list and explain the operations you can perform by using the Stsadm command-line tool. Each article includes a description of the operation, syntax, required and optional parameters, values, and examples (when available).

(http://go.microsoft.com/fwlink/?LinkId=119417&clcid=0x409)

Managing Enterprise Metadata with Content Types

By managing enterprise metadata, an organization can make it easier for its members to find the content they are looking for when they need it—without overburdening them during the creation process.

(http://go.microsoft.com/fwlink/?LinkId=119418&clcid=0x409)

End-to-End Deployment Scenarios – Office SharePoint Server 2007 for Search

This chapter provides information and directions for deploying Microsoft Office SharePoint Server 2007 for Search as an end-to-end solution, whether on a single computer or in a simple server farm.

(http://go.microsoft.com/fwlink/?LinkId=119420&clcid=0x409)

Search Deployment

This white paper provides an overview of the rationale for an enterprise search solution, describes the features available in the various Microsoft products, and outlines solutions to several common search scenarios.

(http://go.microsoft.com/fwlink/?LinkId=119425&clcid=0x409)

Plan to Crawl Content

The purpose of this article is to help Shared Services Providers (SSP) administrators understand how Office SharePoint Server 2007 for Search crawls and indexes content and to help them plan to crawl content.

(http://go.microsoft.com/fwlink/?LinkId=80120&clcid=0x409)

Limit or Increase the Quantity of Content Crawled

For each content source, you can select how extensively to crawl the start addresses in that content source. You also specify the behavior of the crawl, sometimes called the crawl settings. The options you can choose for a particular content source vary somewhat based on the content source type that you select. However, most options determine how many levels deep in the hierarchy from each start address listed in the content source are crawled. Note that this behavior is applied to all start addresses in a particular content source. During operations, you might need to crawl some sites at deeper or fewer levels.

(http://go.microsoft.com/fwlink/?LinkId=119437&clcid=0x409)

One of the properties of the Web Part has an incorrect format

2008-06-10T12:38:00.001-07:00

Web Part Error:

One of the properties of the Web Part has an incorrect format.
Windows SharePoint Services cannot deserialize the Web Part.
Check the format of the properties and try again

I have got this error while modifying a Custom Web Part when i added to it the properties Width and/or Height. Simply I renamed it and that's all.

Here there is the same error on other situation.

Lack of permissions for application pool account can cause Web Parts to not display on home page

If the account used for authenticating the application pool for Windows SharePoint Services does not have read and write permissions to the directory that Windows uses for temporary files, Web Parts may not display properly. When this occurs, the following error message appears:

Web Part Error: One of the properties of the Web Part has an incorrect format. Windows SharePoint Services cannot deserialize the Web Part. Check the format of the properties and try again.

Locate the system temporary directory.
1. Right-click My Computer, and then click Properties.
2. On the Advanced tab, click Environment Variables.
3. In the System variables list, note the directories for TEMP and TMP.
Go to the directories listed for TEMP and TMP.
1. Click Start, and then click Run.
2. Type the path to folder that contains the folder associated with TEMP and/or TMP, and then click OK.
Right-click on the folder for the temporary directory, and then click Sharing and Security.
On the Security tab, verify that the application pool account for the content virtual server has Read and Write permissions in each of the directories.

For information about configuring the application pool account, see the Windows SharePoint Services Administrator's Guide.

javascript syntax error

2008-06-04T05:06:00.000-07:00

This is just a memory on my blog about the "descriptive" message syntax error with a javascript code.
Just to fastly remember that sometimes it comes from this kind of line where i forgot the = character on an "if" sentence.

if (a=1)

where the correct sentence is

if (a==1)

Sometimes i got the "syntax error" message and sometimes "Object expected"

More charts for Sharepoint

2008-05-28T14:02:00.000-07:00

This is a customized page using a flash component and taking data from a Sharepoint List and showing a pie and bars chart.

http://www.sharepointmall.com/Demos/Projects/Contents/ChartsFromAList.aspx

Google Maps on Sharepoint

2008-05-27T10:56:00.000-07:00

This is a sample of a customized Sharepoint page so as to get data from a Sharepoint Contact List and show it on Google Maps.

Google Maps on Sharepoint

Customized Sharepoint task list

2008-05-24T12:38:00.000-07:00

This is a Sharepoint page where you can see a customization to the Task list.

Here you can see a column showing the status in a different way.

It is showing different color lights, as indicators or semaphores, depending on status field content.

http://www.sharepointmall.com/Demos/Projects/CustomPages/default.aspx

Adding a drop down list (combo) to the custom property pane on a Sharepoint Web Part.

2008-04-21T10:19:00.001-07:00

How to add a drop down list to the property pane

Secondly, let's make use of an enum structure which contains company names (as displayed below).

///<summary>

/// Holds the company names

///</summary>

publicenum CompanyName : int

{

TaxOffice = 0, //This will display customers as Tax Office Customers

PostOffice = 1, //This will display customers as Post Office Customers

Bank = 2, //This will display customers as Bank Customers

Telephone = 3 //This will display customers as Telephone Customers

}

Figure 10: Enum class that hold the company names

I expose this enum class as a Web Part custom property as display below,

///<summary>

/// This property will determine the name of the company.

/// The names of the companies are stored in an enum collection.

/// This will be available in a drop down list.

///</summary>

[Browsable(true),//Display the property in property pane

Category("Customer Details"),//Create a Customer Details category in

property pane

DefaultValue(CompanyName.Bank),//Assign a default value

WebPartStorage(Storage.Personal),//Make available in both personal and

shared mode

FriendlyName("Company name"),//The caption display in property pane

Description("Select the office")]//The tool tip

public CompanyName DisplayCompanyName

{

get

{

return m_enmSelectedCompany;

}

set

{

m_enmSelectedCompany = value;

}

Figure 11: Custom property with an enum class

This custom property will display in property pane as below

Incompatible Web Part markup detected. Use ".dwp web part XML instead of *.webpart web part xml

2008-02-29T06:25:00.001-08:00

I'm on MOSS 2007 and just developed this web part deriving from Microsoft.SharePoint.WebParPages.WebPart. It works fine if I manually deploy it to MOSS, that is, manually copy the DLL and add the SafeControl entry into web.cnofig, and then add it in the web part gallery.

If I package it up in a solution .wsp file, adding the solution, deploying it, and activating it all work fine. However, when I go to the home page and try to add it, I get this popup js alert message:

Unable to add selected web part(s).

<web part name>: Incompatible Web Part markup detected. Use ".dwp web part XML instead of *.webpart web part xml.

_________________________________________________

How i solved it?

I fixed it by inheriting from

System.Web.UI.WebControls.WebParts.WebPart and deployed it successfully.

Creating a SpFieldUser Field in Sharepoint

2008-02-22T09:58:00.001-08:00

I was trying to use the list.Fields.Add method to add a SpFieldUser field but i didn't found information on how to do it.

But the below boxed info helped me to create it in another way.

How to add a User Information lookup field with code

One of our developers asked me a question about adding a lookup field to the "User information" list with code. The "Add" method of SPFieldCollection wants a Guid for the destination list, but the "User information" list is not a SharePoint list. The solution is to use the "AddFieldAsXML" and submit a field XML instead.
SPWeb web = GetContextWeb(Current) 'Or whatever method used to acquire this object
SPList list = web.Lists[<listname>];
list.Fields.AddFieldAsXml("<Field Type="User" List="UserInfo" ShowField="Title" DisplayName="<FIELDNAME>" Name="<FIELDNAME>" />");

Adding a button on a Sharepoint web part

2008-02-12T05:47:00.001-08:00

private string MessageButtonTreeClick="";

// Declare variables for HtmlControls user interface elements.
public void mybtnSearch_click (object sender, EventArgs e)
{
MessageButtonTreeClick += "ButtonClicked";
}

_______________________________________________

// Override the ASP.NET Web.UI.Controls.CreateChildControls

// method to create the objects for the Web Part's controls.

protected override void CreateChildControls ()

{

//Create a Search Button

mybtnSearch = new HtmlButton();

mybtnSearch.InnerText = "Search...";

mybtnSearch.Attributes.Add("width","75px");

mybtnSearch.ServerClick += new EventHandler ( mybtnSearch_click );

myTableCellControls_btnSearch.Controls.Add(mybtnSearch);

}

_______________________________________________

public class Tree : Microsoft.SharePoint.WebPartPages.WebPart

{

HtmlButton mybtnSearch ;

}

Microsoft Filter Pack Released to Web

2008-01-29T06:51:00.001-08:00

a filter pack was released to the download center that add's support for new Microsoft Office and ZIP file types for several applications that include Microsoft search functionality.

The pack includes IFilters for the following formats: .docx, .docm, .pptx, .pptm, .xlsx, .xlsm, .xlsb, .zip, .one, .vdx, .vsd, .vss, .vst, .vdx, .vsx, and .vtx.

The download is available here; http://www.microsoft.com/downloads/details.aspx?FamilyId=60C92A37-719C-4077-B5C6-CAC34F4227CC&displaylang=en

Links to the installation instructions for each product are here;

Office SharePoint Server 2007 - Office SharePoint Server 2007 registration steps

Search Server 2008 - Search Server 2008 registration steps

SharePoint Portal Server 2003 - SharePoint Portal Server 2003 registration steps

Windows SharePoint Services v3.0 - Windows SharePoint Services v3.0 registration steps

Exchange Server 2007 - Exchange Server 2007 registration steps

SQL Server 2005 - SQL Server 2005 registration steps

SQL Server 2008 - SQL Server 2008 registration steps

There's a slight mistype in the instructions for SharePoint Server 2007 and Search Server 2008 - Details are here http://blogs.msdn.com/ifilter/archive/2008/01/04/errata-for-filter-pack-kb.aspx

The "Add Link to Site" page stops responding, and the link is not added when you try to add a new link to the Site Directory in a SharePoint Portal Server 2003 site

2007-11-27T06:50:00.001-08:00

That saved me, because a day i wanted to change an attribute of an item on the Sites Directory at Sharepoint Portal 2003.

But when i clicked on the OK Button nothing happened.

It only became disabled and attributes were not changed.

Consider the following scenario. In a Microsoft Office SharePoint Portal Server 2003 portal site, you click Add Link to Site on the Sites page to add a new link to the Site Directory. On the "Add Link to Site" page, you specify the information that you want for the new link. Then, you click either OK or Cancel. In this scenario, the "Add Link to Site" page stops responding. Additionally, the link is not added to the Site Directory.

CAUSE

This issue occurs if Microsoft Windows Server 2003 Service Pack 2 (SP2) is installed on the server. A compatibility issue exists with the "Add Link to Site" page in SharePoint Portal Server 2003.
This issue also occurs if Microsoft Windows 2003 Service Pack 1 (SP1) is installed together with security update 933854 or together with security update 928365. A compatibility issue exists with the "Add Link to Site" page in SharePoint Portal Server 2003.
For more information about security update 933854, click the following article number to view the article in the Microsoft Knowledge Base:

933854 (http://support.microsoft.com/kb/933854/) Description of the security update for the .NET Framework 1.1 Service Pack 1 for Windows Server 2003: July 10, 2007

For more information about security update 928365, click the following article number to view the article in the Microsoft Knowledge Base:

928365 (http://support.microsoft.com/kb/928365/) Description of the security update for the .NET Framework 2.0 for Windows Server 2003, Windows XP, and Windows 2000: July 10, 2007

RESOLUTION

The following file is available for download from the Microsoft Download Center:
Download the SharePoint Portal Server 2003 Service Pack 3 (SP3) package now.

Making Document Libraries More Accessible: Scripting Network Places and Network Locations

2007-10-31T09:41:00.001-07:00

That is a very interesting and useful article i found. Enjoy it

Focused on the integration between Microsoft Office applications and SharePoint, I discussed options for making it easier for users to get to their document libraries. Expecting them to type a long URL in the File Open or File Save dialog boxes isn't realistic. I mentioned that by putting network places (Windows XP) and network locations (Windows Vista) in strategic locations, you can give users a much easier way to navigate to their libraries.

To make a long story short, network places and network locations are the same thing (Vista just had to rename them). They're the beautiful love child of a shortcut and a mapped drive. They're born in the My Network Places folder (XP) or in the Computer folder (Vista), but they can be moved anywhere, like a shortcut. Also like a shortcut, they can have descriptive, friendly names. Like a mapped drive, they appear as a folder in the Windows Explorer folder tree, allowing users to expand their contents.
Network places/locations are, in my opinion, one of the most useful UI elements in existence--and one of the most underutilized. Create network places/locations not just to SharePoint document libraries, but also to regular shared folders needed by users. I suggest putting network places/locations to commonly used targets on the desktop, and then putting other network places/locations in the My Network Places or Computer folder. But you can put them anywhere--even in users' (My) Documents folder or in the root of their user profile (which is great for Vista).
Here's what I recommend:
1. Determine which network folders (SharePoint document libraries and shared folders) are accessed by a user.
2. Create network places/locations that target those folders.

Create network places on XP in the My Network Places folder.
Create network locations in Vista by opening Computer, right-clicking in an empty area, and choosing Add A Network Location.
For SharePoint document libraries, the "target" should be the UNC to the document library, in the form \\ server \ site \[ subsite \]library, or the URL, in the form http:// server / site /[ subsite /] library . Experiment to determine what works best for your clients--there are differences between Vista and XP in how they respond to library addresses. The actual location where the network places/locations are created is the Nethood folder: %userprofile%\Nethood in XP, or in Vista %userprofile%\AppData\Roaming\Microsoft\Windows\Network Shortcuts.
Network places/locations in the Nethood folder are shown in the My Network Places folder in XP. In Vista, the network locations appear in two places: in the Network Locations group in the Computer folder and in the Network Shortcuts folder.

3. Organize the network places/locations to make them easily accessible.

You might choose to put the most commonly used network places/locations on the desktop, in the [My] Documents folder or (on Vista) in the root of the user's profile, which can be accessed by clicking the user name in the Start menu.
Less commonly used network places can be left in the Nethood folder.
When a user chooses the Open or Save command, Office 2003 & Office 2007 start a user in the last folder they were accessing, or in the (My) Documents folder. A user can click My Network Places if they're running XP or Desktop (or Computer) if they're running Vista and, from there, it's one more click to the document library if you've placed their network places/locations there. Interestingly, Network Shortcuts is not in the "links" by default on a Vista client. You can resolve this by adding a shortcut to the Nethood folder into the user's Links folder.
When an Office 2007 user chooses the Publish to Document Management Server command, the dialog box that appears is focused on the My Network Places (XP) or Network Shortcuts folder (Vista). The "Desktop" folder is one click away in the dialog box. That would suggest that the Nethood folder or the Desktop would be good places for network places/locations.

4. Disable XP's default behavior to automatically create network places. XP had an annoying habit of adding network places automatically, which fills up the Network Places folder with junk, and (I think) was one of the reasons why a lot of enterprises never took advantage of this great feature. To disable the automatic creation of network places, use Group Policy settings: User Configuration \ Administrative Templates \ Desktop \ Do not add shares of recently opened documents to My Network Places.
Finally, a number of users asked if it's possible to script the creation of network places/locations to speed deployment and management of network places. The answer is, "Yes!" The script follows at the end of this newsletter.
Until next time, happy SharePointing!
Dan Holme
dan h [at] (intelliem dot toplevel commercial domain)

' Create a network place (XP) or network location (Vista)

Option Explicit

' Generic objects - can be moved to global part of script

Dim WSHShell, FSO

Set WSHShell = WScript.CreateObject("WScript.Shell")

Set FSO = CreateObject("Scripting.FileSystemObject")

Dim sFolderPath, sTargetPath

' Create the network places - THIS IS THE ONLY BLOCK OF THE SCRIPT THAT YOU SHOULD NEED TO CHANGE

' Example A: a document library network place/location created in the Nethood folder

sFolderPath = WSHShell.SpecialFolders("NetHood") & "\" & "Expense Reports Document Library"

sTargetPath = "\\sharepoint.contoso.com\finance\expensereports"

CreateNetworkPlace sFolderPath, sTargetPath

sFolderPath = WSHShell.SpecialFolders("Desktop") & "\" & "Departmental Shared Folder"

sTargetPath = "\\server01\data$\departments\finance"

CreateNetworkPlace sFolderPath, sTargetPath

' This routine will create a network place

' which is actually a read only folder

' containing a regular shortcut named target.lnk and

' a desktop.ini file with specific contents

Sub CreateNetworkPlace(sFolderPath, sTargetPath)

Dim oTextFile, oFolder, oShortcut

' Create the folder and make it read only (required for Network Place)

If FSO.FolderExists(sFolderPath) Then

FSO.DeleteFolder sFolderPath, True

End If

' Create the folder

Set oFolder = FSO.CreateFolder(sFolderPath)

' Read-only attribute

oFolder.Attributes = 1

' Create the shortcut to the target inside the folder

Set oShortcut = WSHShell.CreateShortcut(oFolder.Path & "\target.lnk")

oShortcut.TargetPath = sTargetPath

oShortcut.Save

' Create the Desktop.ini file which makes it a Network Place and assigns the icon

Set oTextFile = oFolder.CreateTextFile("Desktop.ini", True)

oTextFile.WriteLine "[.ShellClassInfo]"

oTextFile.WriteLine "CLSID2={0AFACED1-E828-11D1-9187-B532F1E9575D}"

oTextFile.WriteLine "Flags=2"

oTextFile.WriteLine "ConfirmFileOp=0"

' 1 displays a warning that this is a system folder when moving, deleting, renaming a system folder

' 0 avoids the warnings

oTextFile.Close

End Sub

Microsoft Office Word Macros on a shortcut key

2007-10-11T09:44:00.001-07:00

Macros are very powerful and better if you can make them handy if you assign a shortcut key to your macros. This tip works with Microsoft Word 97, Word 2000, Word 2002, and Word 2003.

Select Customize from the Tools menu. You will see the Customize dialog box.

Click on the Keyboard button. Word displays the Customize Keyboard dialog box

Scroll through the Categories list and select the Macros category. The list at the right side of the dialog box changes to show the currently available macros.

In the Macros list, select the macro you want assigned to the shortcut key.

With the insertion pointer in the Press New Shortcut Key box, press the shortcut key you want to use. For instance, if you want to use Ctrl+Alt+J, press that.

Just below the Press New Shortcut Key box you can see whether the shortcut key is already assigned to a different function.

Click on Assign.

Repeat steps 4 through 7 for each change you want to make.

Click on Close.

Sharepoint 2003 and 2007 not valid characters on files

2007-10-02T07:33:00.001-07:00

Files uploaded to SharePoint cannot contain the following characters:

: # % & * : < > ? \ { | } ~

That happens on 2003 & 2007 versions.

Registering a client script on a Sharepoint Custom Page

2007-09-27T06:31:00.001-07:00

This a is a self memory post, because i know i ll need it again.

In this case i am creating a function to load a Flash Movie

Of course it is part of a ASP.Net Page developed with Visual Studio 2003

private void Page_PreRender(object sender, System.EventArgs e)
{

scriptString += "function changeMovie(){";

scriptString += "var d=document;";

        if (Page.IsPostBack)
        {
            scriptString += "myflash='" + lblFlashnameValue.Value + "&Hoja="+ lblIdHojaValue.Value +"';" ;
        }
        else
        {
            //First Time
            scriptString += "mypath='" + Request.QueryString["TMCOrigen"] + "/_layouts/pages/';";
            scriptString += "mypathXML='" + Request.QueryString["TMCOrigen"] + "/_layouts/pages/';";
            scriptString += "myflash=mypath+'tree20070921R.swf?SharepointTree='+ mypathXML + " + "'"+"tree99.xml"+"'" +";";

}

        scriptString += "d.all('tree20070921R').LoadMovie(0, myflash);";
        scriptString += "d.all.lblFlashnameValue.value =   myflash ;";
        scriptString += "}";
        scriptString += "</script>";
        Page.RegisterClientScriptBlock("clientScript", scriptString);
}

Creating or adding an attribute (xmlAttribute) on a node in c# and Visual Studio 2003

2007-09-19T07:25:00.001-07:00

//Add attribute id2
XmlDocument xDocId2 = new XmlDocument();
xDocId2.Load (tmpFilename);
foreach (XmlNode unNodo in xDocId2.DocumentElement.GetElementsByTagName("nodo") )
{
    XmlAttribute nAttr;
    nAttr = xDocId2.CreateAttribute ("id2");
    nAttr.Value= unNodo.Attributes["id"].Value     ;
    unNodo.Attributes.Append( nAttr);
}
xDocId2.Save(tmpFilename);

Enabling Wildcard Search in Sharepoint 2003

2007-09-04T08:07:00.001-07:00

This walkthrough will guide you how to enable wild search using SPS, you need to do the following:

Export the search result web part.
Customize the DWP file, add query to enable the wild search criteria
Import the web part back to SPS and drop it within search page area.

Here are the details:

Go to your search page. By default, you won’t be able to modify it, go to this link to enable the shared mode
http://your_server/search.aspx?mode=edit&view=shared
Modify the Shared Page, and export the search result Web Part (just save it in your desktop, by default it has *.dwp extension)
The Webpart file (DWP) is basically XML File, so you can open it using Notepad. Go find this section : “QueryTemplateWherePart”
Add the following code in the END of the section to enable the wide search : OR CONTAINS("urn:schemas-microsoft-com:sharepoint:portal:profile:PreferredName", '"%__keywordinput__%"') RANK BY COERCION(multiply, 0.01)
OR CONTAINS(#WeightedProps, '"%__keywordinput__%"')
Save the file, go back to your sharepoint modify page – Add Web Parts – Import
Drop your modified search result web part to your search page. And that’s all, hope this help…

Pros:

You ll be able to use the asterisc at the end of a word so as to make a search like Pro*, where you ll get results for word as project, prototype,etc

Cons:

User will not be allowed to save their search alerts and ll get this error, "An error has occurred on the server" . You can find info here http://support.microsoft.com/kb/920823/en-us

New SharePoint Server 2007 SDK - Free Download

2007-08-27T13:23:00.000-07:00

Overview

The Microsoft Office SharePoint Server (MOSS) 2007 SDK is designed for solution providers, independent software vendors, value-added resellers, and other developers to learn about the new Office SharePoint Server 2007 enterprise application and platform. It features conceptual and "How to" articles, sample code, and programming references.What’s New in this Release for the MOSS SDK

Installation enhancements: You now have a choice of installation location when you’re installing the SDK. Browse to your preferred folder during setup. The default installation path for MOSS is C:\Program Files\2007 Office System Developer Resources\.

Start menu navigation: This release features a new Start menu shortcut for quick access to documentation (compiled HTML Help, or CHM for short) files and the Welcome Guide (Readme.htm), which is a landing page with links to all the tools and samples. In Windows Server 2003, click Start, Programs, 2007 Microsoft Office System Developer Resources, Office SharePoint Server 2007 SDK to open: MOSS 2007 Technical Articles and Visual How-To's, Office Forms Server SDK Documentation, Office SharePoint Server SDK Documentation, Welcome Guide, Windows SharePoint Services SDK Documentation. In Windows Vista, click the Windows Vista Start button, All Programs, 2007 Microsoft Office System Developer Resources, Office SharePoint Server 2007 SDK to open: MOSS 2007 Technical Articles and Visual How-To's, Office Forms Server SDK Documentation, Office SharePoint Server SDK Documentation, Welcome Guide, Windows SharePoint Services SDK Documentation.

Offline experience improvements: All of the technical articles, visual how-to articles, and book excerpts are now packaged—plus the Excel Services and Excel 2007 Windows Compute Cluster Server 2003 Job Submission Developer Guide—into one searchable CHM file. Browse offline for content published on MSDN out-of-band with the SDK. (Known issue: Several links in the MOSSSDK_TechArticles.chm and WSSSDK_TechArticles.chm do not work in a strictly offline scenario. Also, WMV file screencasts or downloads associated with articles are not packaged in the CHM, to keep the download size manageable. Workaround: Browse to the content on MSDN online; for ease-of-use, the CHM file TOC is the same as the MSDN Library TOC.

New tools included with the MOSS SDK:Developer tools and samples for the following areas of MOSS development (new tools in red):

Business Data Catalog Samples and Utilities

-Microsoft Business Data Catalog Definition Editor
-Sample Pluggable SSO Provider
-WSHelloWorld Web Service
-WSOrders Web Service
-Excel Services User Defined Function Sample
-WSOrders Custom Proxy Sample
-Amazon Web Service Sample
-AdventureWorks Metadata Samples
-SAP Sample

Document Management and Content Processing Samples

-Comment Scrub Document Converter
-Term Replacement Document Inspector

Search Samples

-Sample Protocol Handler
-Custom Content Source

Records Management and Policy Samples

-De-Duplication Router
-Document Integrity Verifier
-Records Center Web Service Console Application
-Search, Collect, and Hold Tool
-Sample Custom Barcode Generator
-IRM Document Protector

Workflow Samples

-Custom Workflow Report Query Generator
-Custom Workflow Report XLSX Injector
-Visual Studio Workflow Templates
-Enterprise Content Management Workflow Activities
-List Item Activities
-Hello World Sequential Workflow
-State Based Approval Workflow
-Modification Workflow
-Replication and Contact Selector Workflow
-Intersystem Purchase Order
-Confidential Approval Workflow
-Group Approval Workflow
-Approval Workflow Sample
-Multi-Stage Workflow
-Server-side Collect Signatures Workflow

Full details can be found in the Welcome Guide of the SDK, accessible through the Start menu.

http://www.microsoft.com/downloads/details.aspx?FamilyId=6D94E307-67D9-41AC-B2D6-0074D6286FA9&displaylang=en

Why you need your very own Areas at Sharepoint Portal Server 2003.

2007-08-27T07:26:00.000-07:00

Why you need your very own Areas at Sharepoint Portal Server 2003.
How to understand this functionality

The search engine, on Sharepoint, makes use of innovative algorithms and dazzling mathematics. But judging whether these results are any good or not is completely in the eye of the beholder. It's subjective.

The Search engine sometimes don't provide valuable results. This is can often be because when you know little about what you're looking for, you have little idea as to what to search for. For example, someone interested in learning about crabs may never have heard of the term crustacean (or know how to spell it).

It's often easy to forget that better maths, artificial intelligence, natural language processing, fuzzy logic, and neural nets, may never work out that "Bubble & Squeak" has nothing to do with bubbles or squeaking. But people can make these connections and structures easily. One way to help your search engine to locate "better" matches is to add a little common-sense humanity and create Areas.

Areas are simply a classification or an organization of related keywords or concepts. A better search engine is essential in a world where more and more people now understand what "information overload" and "being lost in hyperspace" feels like.

The challenge

Making Areas is an act of communication. They basically capture an essence of the knowledge that resides in your organization. A conceptual short-hand overview that describes what's important and how things you are interested in relate to each other. Creating Areas, like anything that worthwhile can be hard work, time-consuming and require considerable domain expertise and creativity.

Imagine a "Creatures of the World" site. It may have an areas structure like this...

Animals

Vertebrates
Warm blooded
- Mammals
- Birds
Cold blooded
- Fish
- Reptiles
Invertebrates
Arthropoda
Crustaceans (Crabs, Lobsters, barnacles, etc)[li]Insects

Already you may be thinking, I wouldn't have organized the Creatures like that, my users need to access them like this...

World

Seas
Atlantic
Pacific
- Barrier Reef
Land
Africa
Europe
North Pole

Now imagine looking for information of the Red Rock Crab (Plagusia chabrus)

In the first example, I might not know what a Arthropoda was (I didn't when I started this article). In the second example, would a crab be in the Land or Seas section.

Making Areas for your company can be very political. The way information is organized helps define the information. Both the examples above don't mention the rarity of the animals, something I would want to make a primary node if I wanted to raise environmental issues.

Often we don't question Areas structure when we see them. Many off-licences I visit have wines arranged by price (with the expensive wines normally higher than the cheap plonk) or by region (France, Spain, The Americas etc). But one online company, has chosen to arrange their wine by taste, with categories of "fizzy", "fresh", "juicy", "big" and sweet. I'm not a wine buff, but using this Areas structure, I know that I'd probably like anything between "juicy" and "smooth" wines and I'd be more prepared to be adventurous within this category than a category like "Australia" or even a price range. It took the people at Best Cellars time and effort to categorize the wines on offer, but doing so has made me more likely to find what I want and (incidentally) spend money!

Facetted classification to the rescue

One of the problems with Areas and classification is that the world and the things in it, tend not to like a hierarchical arrangement of folders. In the past, many classification systems were too exclusive and restrictive, becoming hugely complex, cumbersome and political. A facetted classification system is a more fluid approach to creating areas structure.

Facets allow for a more complex structure, where the categories are applied to the information like keywords. For example, the "Red Rock Crab" would be able to be found in numerous ways, for example...

Red Rock Crab

Animals / Invertebrates / Crustaceans /
World / Seas / Pacific
World / Land / Australasia
A new search engine, Teoma, reveals these categories (or facets) in a way I find very helpful. Contrast the way these search results work.

"Red Rock Crab" at Teoma

"Red Rock Crab" at Google

Small steps
Making Areas is a collaborative and iterative process. You shouldn't expect get it right first time. This means that working with the areas structure needs to be readily available to all involved and stunningly easy to use, otherwise it will stagnate and not be used. It needs to evolve so that you can imagine your intranet making sentient suggestions, "people who made use of these corporate logos also read these branding guidelines".

Interestingly, you end up with something that closely resembles a thesaurus, but one that is geared to your subject area. The thesauri themselves are enjoyable to browse and can easily be integrated into search queries to find conceptually related material.

As we are all discovering, it isn't enough to simply to have information available because the way you choose to organize your information may, ironically, be preventing people from finding and using it. Facetted Areas structure allow a for a multitude of information structures to coexist.

Looking on the horizon are technologies like RDF and XML topic maps and concepts like the Semantic Web and Knowledge Management all of which are attempting to make pieces of information more meaningful by understanding the relationships that exist between them. These technologies may make the web a "smarter" place to be, but in the meantime, integrating your search engines with your areas structure will make your sites more meaningful, useful and humane.

This is an adaptation for SharePoint 2003 Topics Areas found at http://www.othermedia.com/go/Article_28.html

Scripting With Flash

2007-08-01T11:25:00.000-07:00

http://www.adobe.com/support/flash/publishexport/scriptingwithflash/scriptingwithflash_03.html

This is a just a memory reminder when i needed to write javascript to as to change the movie on a flash Object. The flash i was using was a tree, because i could not use any treeview on a Sharepoint 2003 Project.

Extending Microsoft Office Sharepoint Server 2007

2007-07-12T08:22:00.000-07:00

Extending Microsoft Office Sharepoint Server
2007

This is an overview of feature.xml attributes.

Feature.xml Attributes

Feature attribute	Description
Id	The globally unique identifier (GUID) for the Feature, in Registry format.
Title	The name of the Feature. It 's important because it makes the purpose of the feature easily identifiable. It can be up to 255 characters in length
Description	(Optional) Describes what the Feature does
Version	Specifies the version of the feature
Scope	Specifies where the Feature will be deployed and made available -- that is, server farm, Web application, site collection, or Web (site).
Hidden	Determines whether the Feature will be visible in the Feature administrative user interface. This option toggles between False and True. False is the default. Set this option to True to hide the Feature from administrative user interface.
AlwaysForceInstall	(Optional) If True, any updates to the Feature are installed within the given scope without manual intervention during updating. Removes the need to add the - force parameter to the stsadm.exe command line when redeploying a Feature.
DefaultResourceFile	(Optional) The resource file the Feature uses for additional configuration details
ImageUrl	(Optional) The URL to an image you want to have associated with the Feature in the Feature administrative user interface.
ReceiverAssembly	(Optional) The strong name of the assembly that handles events for the Feature. (*)
ReceiverClass	(Optional) The fully qualified, case-sensitive name of the class that handles events for the Feature.
ActivationDependencies	(Optional) The Feature IDs of any dependent Features -- that is, Features that depend on the Feature being activated before they can be activated.
ElementManifests	The relative path to associated element files for the Feature. This can include more than one element file.

(*) The ReceiverAssembly attribute in the Feature.xml file
should not be confused with the Receiver element in the supporting element
files. The ReceiverAssembly attribute names the assembly from
which to load Feature events-- that is, different events specified throughout
a Feature life cycle, such as when a Feature is activated or deactivated,
using special Feature classes through the Sharepoint object model. The
Receiver element in the element files associated with the Feature receives the
assembly for a specific event handle assembly.

Understanding the Event Model

2007-04-24T07:59:00.000-07:00

This article is candidate for my WebMemoryBlog but i posted it here.

This info is from http://msdn.microsoft.com/library/default.asp?url=/workshop/author/om/event_model.asp but as sometimes ms deletes some of the contents i decided to publish it here.

Understanding the Event Model

An event is a notification that occurs in response to an action, such as a change in state, or as a result of the user clicking the mouse or pressing a key while viewing the document. An event handler is code, typically a function or routine written in a scripting language, that receives control when the corresponding event occurs. The following topics describe events and event handlers and explain how to use them in your documents.
The Life Cycle of an Event
Attaching an Event Handler
More About Event Bubbling
Returning Values and Canceling Default Actions
Event Handler Scoping
Event Object
Keyboard Events
Mouse Events
Focus and Selection Events
Load and Readystate Events
Other Events
The Life Cycle of an Event
An event has a life cycle that begins with the action or condition that initiates the event and ends with the final response by the event handler or Microsoft Internet Explorer. The life cycle of a typical event consists of the following steps.
The user action or condition associated with the event occurs.
The event object is instantly updated to reflect the conditions of the event.
The event fires. This is the actual notification in response to the event.
The event handler associated with the source element is called, carries out its actions, and returns.
The event bubbles up to the next element in the hierarchy, and the event handler for that element is called. This step repeats until the event bubbles up to the window object or a handler cancels bubbling.
The final default action, if any, is taken, but only if this action has not been canceled by a handler.
For events that bubble, if there is no event handler bound to the source element, the event handler for the next element up the hierarchy is called.
When an event handler carries out its actions, it uses the event object to retrieve information about the event, such as the position of the mouse pointer, the state of the keyboard keys, the element in which the event occurred, and so on.
The following example defines an event handler, wasClicked, for the onclick event and associates it with the BODY element. When the user clicks the mouse button anywhere in this document, the event fires and the event handler displays the message "I was clicked," followed by the tag name of the element in which the event occurred.
<-html>
<-body onclick="wasClicked()">

Welcome!

This is a very short document.

<-/body>
<-/html>
Show Me
The srcElement property of the event object specifies the element object in which the event occurred. This is useful for deciding what action the event handler should take in response to the event.
Attaching another event handler, wasAlsoClicked, to the p element demonstrates the parent-child relationship of document elements.
Show Example<-html>
<-body onclick="wasClicked()">

Welcome!

This is a very short document.

<-/body>
<-/html>
Show Me
As in the preceding example, if the user clicks the heading "Welcome!", the message "I was clicked H1" appears. But if the user clicks the word "short," two messages appear: "You clicked me B," followed by "I was clicked B." In the first instance, clicking "Welcome!" fires the onclick event, setting the H1 element as the source element of the event. There is no event handler for this element, so the event bubbles up to its parent element in the hierarchy, BODY, and its event handler, wasClicked, is called.
In the second case, when the user clicks the word "short," the onclick event fires again. This time the b element is set as the source element. Because there is no event handler for b, the event bubbles up to the p element and its event handler, wasAlsoClicked, is called. But that's not the end of the event. After wasAlsoClicked returns, the event continues to bubble up the hierarchy to the next parent element, BODY, causing wasClicked to be called.
In some cases, you might not want the event to bubble up in the hierarchy. You can stop the bubbling by setting the cancelBubble property of the event object to true in any event handler. After the handler returns, the event stops bubbling and comes to an immediate end. Notice that this cancellation affects only the current event, not subsequent events. Subsequent events will bubble unless you explicitly cancel them.
Consider the following example. It defines two event handlers, setBodyStyle and setParaStyle, that are called when the user clicks in the document or in the paragraph, respectively. To ensure that only the style for the paragraph changes when the user clicks in the paragraph, the setParaStyle handler uses cancelBubble to prevent the event from bubbling up to BODY.
Show Example<-html>
<-body onclick="setBodyStyle()">

Welcome!

This is a very short document.

<-/body>
<-/html>
Show Me
The preceding example does not automatically assume that the source element is p. Because the user might have clicked in the b element, the event handler must check the element before applying the style. In this case, the handler uses the parentElement property to move up the element hierarchy until the p element is found.
Attaching an Event Handler
You must associate an event handler with a specific event and specific element or object in order for the handler to be called when the event fires. You can associate an event handler by using any one of the following, essentially equivalent, methods.
Declare an event handler function and assign a call to that function in the appropriate inline event attribute of an HTML tag. The following example defines a Microsoft JScript function, named flip, and associates it with the img element as the event handler for the onmouseover event.
.
.
.

The preceding example shows an event handler function being bound; however, any expression can be used here to be evaluated each time the event fires. Notice that because this is an expression, the parentheses following the function name are required.
Declare event handling code and use the FOR and event attributes of the script tag to associate the code with the event. The following example also defines JScript code and associates it as the onmouseover event handler for the img element that has the identifier MyImage.
.
.
.

Declare an event handler function in VBScript and associate it with an event by giving it a name that has this form: id_event. The following example defines a Microsoft Visual Basic Scripting Edition (VBScript) function that handles the img element as its onmouseover event handler.
.
.
.

As a general rule, you should always define and associate your event handlers as early in the document as possible. Depending on the method you use, the handler can begin handling events either while the document is loading or immediately after loading, as shown in the following table.
JScript event handler
When set using an inline event attribute, associates when the element is created.
FOR and EVENT event handling code
Associates when the document is fully loaded.
VBScript event handler
Associates when the document and all contained objects and applications are loaded.
Some events can occur while the document is loading. If you need to handle events at this time, you can use JScript and an inline event attribute to associate the handler when the element is created.
You can associate the same event handler with more than one element in the document. This is useful if you want the same action to occur whenever the given event occurs in any of the elements. Typically, event handlers are written to handle only one type of event, but it is possible to create event handlers that can handle more than one.
You don't have to limit yourself to one event handler for each type of event. If the action you want to occur for a given event in one element is different than for the same event in another element, you can define two event handlers and associate each to its appropriate element. In general, you can define any number of event handlers for the same type of event and associate each with one or more elements in the document.
If you use a combination of handling methods in a document, you can also define more than one event handler for the same event in the same element. For example, you can declare both a JScript and a VBScript event handler and associate them with the same event and element. If you associate more than one event handler in this way and the handlers are in different languages, all handlers receive the event, but the order in which they receive the event is not specified.
If you associate two event handlers of the same language to the same event and element, only the last handler receives the event. But any handler associated using the FOR and EVENT attributes always takes precedence over a handler associated using an inline event attribute.
When you associate with an inline attribute, you typically assign to the attribute a call to the event handler function, causing that function to be called when the event fires. But assigning a call to an event handler is not a requirement. Instead, you can assign any valid script code; this code is executed when the event fires. For example, the following button element displays the message "Hello World!" when you click it.
This method is convenient as long as the code is relatively short and uncomplicated. If you use an inline attribute in this way, you also should use the LANGUAGE attribute to specify the scripting language for the code. If you don't specify the language, either the default language or the most recent language specified is assumed.
Attaching with Event Properties
The inline event attributes of an element are also available as properties. This means you can use the properties to dynamically change the event handling for an element at any time. For example, you can associate a handler to an element that didn't previously have one, or change the existing handler for an element to some other handler. Adding or changing event handlers is a useful way to make sure that the actions taken on an event reflect the current content of the element.
The following JScript example uses the event property to associate an event handler, setHeadStyle, to the H1 element. A pointer to the setHeadStyle function is assigned to the onclick property of the element.

Welcome!

.
.
.

Handling Custom Events or Events with Parameters
Using the FOR and EVENT attributes to associate events gives you access to custom events fired by embedded objects and to any parameters that an event generates. Unlike standard events that can be bound using attributes or properties, in the case of custom objects these are not available.
Use the FOR attribute to specify which element or object to handle, assigning it an identifier or the name of an object, application, or control. If you don't specify this attribute, the handler is bound to the window by default. Notice that JScript is case-sensitive, so you must type the identifier or name exactly as it appears in the corresponding element or object.
Use the EVENT attribute to specify which event to associate to, assigning it an event name. If the event generates parameters (few predefined events do), you can also specify a list of comma-separated parameter names enclosed in parentheses immediately after the event name. The parameters are untyped. Because JScript is case-sensitive, make sure you always spell event names in lowercase letters. Also, if you give a parameter list, VBScript requires that all parameters defined for the event be listed, even if they are not used.
The following JScript example associates the event handling code with the onerror event for the window. This event fires if an error is detected while loading the document. The event generates parameters, so a parameter list is given, and the lineno parameter is used in the code.
The following JScript example associates the event handling code with a custom event, ondatechange, that the embedded object fires.

An alternate way to handle custom events and to receive event parameters is to associate VBScript handlers. In this case, you use the VBScriptid_event format for the event handler name and provide a parameter list if appropriate. The following VBScript example handles the onerror event and receives its parameters.
Similarly, the following VBScript example handles a custom event, ondatechange, fired by the embedded object.

More About Event Bubbling
Event bubbling ensures that the event handlers for all elements in which an event occurs have an opportunity to respond to the event. Consider the following example.

Jump to a sample document.

The user might reasonably expect that clicking the word "sample" will cause the same actiona call to the event handler named doParaas clicking any other word in the p element. If events did not bubble up from the source element, clicking "sample" would not cause any action, because there is no event handler bound to the b element. Because events do bubble up through the element hierarchy, every event handler on the element's parent hierarchy has a chance to respond, and in this case doPara is called when the user clicks "sample."
Unless you keep event bubbling in mind, you might initially be baffled by some results. For example, consider a document that uses onmouseover and onmouseout events to show and hide a collection of paragraphs, but also uses the events inside the list to highlight paragraphs in the collection.

My Menu

In the preceding example, suppose the user moves the mouse pointer over the words "My Menu," then over the words "Item 1," and finally over the words "Item 2." Here's what happens:
The mouse pointer moves over "My Menu."
The onmouseover event fires for the div element, and showPara is called.
The mouse pointer moves from "My Menu."
The onmouseout event fires for the div element, and hidePara is called.
The mouse pointer moves over "Item 1."
The onmouseover event fires for the p element, and highlight is called.
The onmouseover event bubbles up to the div element, and showPara is called with p as the source element.
The mouse pointer moves from "Item 1."
The onmouseout event fires for the p element, and unhighlight is called.
The onmouseout event bubbles up to the div element, and hidePara is called with p as the source element.
The mouse pointer moves over "Item 2."
The onmouseover event fires for the p element, and unhighlight is called.
The onmouseover event bubbles up to the div element, and showPara is called with the second p as the source element.
Whenever the user moves the mouse over and away from a paragraph in the collection, the event handlers for div are called. If the handlers are written without taking this into account, the paragraphs might be hidden when they should not be.
In general, whenever you use nested event handlers in this way, you need to consider carefully whether the event handler should carry out an action each time it is called. One way to control the action is to use the cancelBubble property. In the preceding example, the highlight and unhighlight event handlers could set cancelBubble to true to prevent the event from bubbling up to the div element. Another way is to check the source element for the event, the srcElement property of the event object, and pick an action that is appropriate to that element.
It is possible to trap events on an element even though the element does not natively support the event. For example, the onkeydown event is supported by the input type=text object. However, because of event bubbling you can define an event handler for the onkeydown event on a div. Any onkeydown events fired by elements contained in the div will bubble up to the div and be handled by its event handler.

In the preceding example, when the user presses a key in either text box, the onkeydown event fires. The event bubbles up through the element hierarchy until it is trapped by the div's event handler.
Returning Values and Canceling Default Actions
Event handlers can return values to the event either by using the return value mechanism defined for the language, such as the return statement for JScript, or by using the returnValue property of the event object.
Return values are useful for controlling the default actions associated with events. For example, clicking the a element causes the browser to load the document specified by the HREF attribute. You can cancel default actions such as these by returning false from your event handlers.
Not all scripting languages support return values. For these languages, you must use the returnValue property to set a return value. If a language supports return values, you can use either the language-defined method of returning a value or returnValue. If you use both methods, the property always takes precedence.
After all event bubbling is complete, any default action associated with the event is canceled if returnValue is false or, if this property is not set, the return value of the last function is false. Some events do not have default actions associated with them and might use the returnValue (or function return value) in other ways.
Canceling a default action is not the same as canceling event bubbling. You can cancel the default action and still allow the event to bubble up through the hierarchy.
Event Handler Scoping
Depending on whether a script is written inside a form container or elsewhere in the document, different scoping rules are applied for executing event handlers and the elements that are available on the window object. Four different scenarios are listed below.
When events are fired, a special object referencethe me pointer in VBScript and this in JScriptis set to the current element firing the event.
1) Event handler for a button outside a form.
This is the basic case. You can use any of the handling mechanisms described earlier. The only rule is that you cannot access elements within a form block directly on the window object. Instead, you can access them from the document object or the particular form's elements collection.
2) Event handler not inside the form block for a button inside a form.
If the button has a unique identifier to the entire document, the event handler can be written anywhere within the document. If the event handler is written outside the form block, the same rules apply for accessing elements on the window object as described in scenario 1 above.
3) Event handler inside the form block for a button inside the form.
If the button's identifier is not unique to the document, the event handler must be written within the form. When writing event handlers inside a form, using either inline attributes or the FOR and EVENT attributes (but not the VBScriptid_event method) changes the scoping rules of the window object. Events defined this way can access elements behind the form directly from the window object. They can also access elements that are outside the form directly as long as they do not conflict with any of the form's element names.
When using the VBScriptid_event method of handling, only elements that are not within the form's scope can be accessed as properties of the window.
If there is no unique identifier within the form, the first element with the matching identifier is bound to the event handler when using the FOR and EVENT attributes of the script element or the VBScriptid_event mechanism of defining events.
4) Event handler inside the form block for a button outside the form.
The event handler executes only if the VBScriptid_event method of handling is used; otherwise, this code does not execute.
You can write an event handler for multiple elements. This can be done only when the elements are not within the same scope, where scope is defined as being inside the form or not inside the form. For example, if writing an event handler for id=genericButton in the document's scope, and adding a genericButton to the document and another within a form, the same click event is fired in both cases. The me pointer will point to the actual source of the event. These elements do not have to be of the same type for this to work.
If multiple elements have the same identifier and are within the same scope, only the first one fires the event.
Event Object
The event object, on the window object, is accessible to all event handlers and is the language-independent, preferred way for handlers to get and modify information about the event. For example, the following VBScript and JScript examples both use the object to display the tag name of the element in which the event occurred.

Note In VBScript, you must use the window keyword with event to avoid a conflict with the VBScriptevent keyword.
The srcElement property is one of the most important properties on event. Many event handlers use this property to determine an action to take, based on the source of the event. For example, the following JScript event handler carries out an action whenever the user clicks any of the H1 elements in the document.
Another important property is cancelBubble, which controls event bubbling for the given event and, if set to true, prevents the event from bubbling up the element hierarchy.
The returnValue property gives an event handler a language-independent way to return a value to the event. For many events, setting the return value to false cancels the default action for that event.
Some properties of the event object have meaning only for certain events. For example, the keyCode property is an integer that specifies a standard numeric Unicode keycode for keyboard key events. For other events, this property is set to zero. Other examples are the toElement and fromElement properties, which represent the element that the mouse is going to and coming from for the onmouseover and onmouseout events. For other events, these properties are null.
When a mouse event occurs, such as onclick, the x and y properties specify the horizontal and vertical position of the mouse. If none of the elements containing the source element are positioned, the position of the mouse is relative to the BODY element. If a positioned element contains the source element, the position of the mouse is relative to that element. In addition to mouse position, the button property indicates which mouse buttons are pressed at the time of the event. It is 0 if no buttons are pressed, 1 for the left button, 2 for the right, and 3 for both.
The altKey, ctrlKey, and shiftKey properties are useful for all events. These properties specify whether the ALT, CTRL, and SHIFT keys are pressed or released at the time of the event. The property is true if the key was pressed. The following VBScript example cancels the default action for the a element if the SHIFT key is pressed when the event occurs.
The clientX and clientY properties are integers that specify the coordinates relative to the size of the client area, not including window decorations. The offsetX and offsetY properties are integers specifying container-relative positions. These match the offsetTop and offsetLeft properties of the element. Use the offsetParent property to locate the container that defines this positioning. The screenX and screenY properties are integers that specify the coordinates relative to the physical screen.
Note Properties such as returnValue and keyCode are read/write properties. This means an event handler can assign a new value to the property, overwriting the original value. The property retains this new value as the event bubbles up the element hierarchy. This makes it easy for an event handler bound at a low level in the hierarchy to modify events that are also handled at a higher level.
The event object provides detailed information about where in the document an event occurs, so that it is easy to write an event handler that can adapt its action based on the source of the event. If you associate the event handler on an element or object that contains all the elements in which the event might occur, event bubbling will ensure that the handler is called whenever the event occurs. This means you don't need to associate the event handler to each element.
Keyboard Events
Keyboard events occur when the user presses or releases a keyboard key. The onkeydown and onkeyup events fire when a key changes state as it pressed or released, respectively. These events fire for all keys on the keyboard, including shift state keys such as SHIFT, CTRL, and ALT.
The onkeypress event fires when the user's keyboard input is translated to a character. These occur, for example, when the user presses letter or number keys, or a combination of shift keys and letters and numbers.
When a keyboard event occurs, the keyCode property of the event object contains the Unicode keycode of the corresponding key. The altKey, ctrlKey, and shiftKey properties specify the state of the ALT, CTRL, and SHIFT keys.
You can change which key is associated with the event by either changing the value of the keyCode property or returning an integer value. You can cancel the event by returning zero or false.
The onhelp event is a special keyboard event that occurs when the user presses the help key (F1).
Mouse Events
Mouse events occur when the user moves the mouse or clicks the left button. The onmousemove event fires when the user moves the mouse, and onmouseover and onmouseout fire when the mouse moves in and out of an element. The onmousedown and onmouseup events fire when the left mouse button changes state as it is pressed or released, respectively. The onclick and ondblclick events fire when the user single-clicks and double-clicks the button.
When a mouse event occurs, the button property of the event object identifies which mouse button, if any, is pressed. The x and y properties specify the location of the mouse pointer at the time of the event. For the onmouseover and onmouseout events, the toElement and fromElement properties specify the elements the mouse is moving to and from.
Mouse Clicks
The onclick event fires when the user presses and releases the button. The ondblclick event occurs when the elapsed time between two consecutive onclick events is within a system-defined range.
Mouse click events are interspersed with onmousedown and onmouseup events. For example, the onclick event follows an onmouseup event. The ondblclick event occurs at the end of the following sequence.
onmousedown
onmouseup
onclick
onmouseup
ondblclick
An onclick event can also occur when the user presses ENTER on a focusable element, such as a button element. In this case, the event fires without a preceding onmouseup event.
You can cancel a mouse click by returning false or setting the returnValue property to false.
Note For mouse devices that have one button, that button is considered to be the left mouse button.
Moving Between Elements
The onmouseover and onmouseout events fire whenever the mouse pointer moves from one element to another. Consider the following document fragment.

Move from here

To here

In the preceding example, as the mouse pointer moves from the H1 element to the words "To here," it crosses over the boundaries of the p, b, and i elements. However, the event sequence is simplified to the following: onmouseout on the H1, which bubbles up the hierarchy, and onmouseover on the i element, again bubbling up the hierarchy.
The fromElement and toElement properties on the event object return the element object the mouse pointer is coming from and going to. Through event bubbling, it is possible to determine each boundary that has been crossed by the mouse move.
When moving between elements, the onmouseout event fires first to indicate that the mouse pointer has left the original element. Next the onmousemove event fires, indicating that the mouse pointer has moved. Finally, onmouseover fires to indicate that the mouse pointer has entered the new element.
Focus and Selection Events
The focus and selection events provide detailed information about the actions the user is taking in the document.
The focus events occur on elements such as button and various types of INPUT objects that can receive the input focus. For these elements, the onfocus event fires when an element receives the focus, and the onblur event fires when an element loses the focus. An element receives the input focus when the user clicks it with the mouse or navigates to it using the keyboard. These events are useful for knowing when to prepare an element to receive input from the user.
Note The focus events fire whether moving the input focus between elements in the document or between frames in the window or even applications on the desktop. For example, if a control in the document has the focus and the user switches to another application, the onblur event fires for that control. When the user switches back to the document, the onfocus event fires. It is not possible to cancel the loss of focus.
The selection events occur when the user selects a portion of the document using the mouse or keyboard. The onselectstart event fires when a selection is first initiated. Such events fire, for example, when the user clicks a character or object in the document. The onselect event fires when the user changes the selection, for example, by moving the mouse pointer over a portion of the document while holding down the mouse button. The default action for the onselectstart event is to move the selection to the given character or object and highlight that selection. You can cancel this default action by returning false.
The ondragstart event fires when the user first begins to drag the selection. The user can drag a selection by holding down the mouse button on the current selection and moving the mouse. The default action for this event is to prepare the selection to be copied to another element. You can cancel this default action by returning false.
Load and Readystate Events
Three events signify the current state of the document: onreadystatechange , onload, and onunload.
The onreadystatechange event fires when the document changes from initializing to interactive, and from interactive to loaded. A document is interactive as soon as the user can interact with it by scrolling or clicking on anchors or elements. A document is loaded when all the content is downloaded.
The onload event fires after the document is loaded and all the elements on the page are completely downloaded. The onunload event fires immediately prior to the document being unloaded as when navigating to another document.
Specifying code for the onload and onunload events can be done on the BODY tag. However, these events actually occur on the window object. Therefore, when handling the onload event using the
This example handles "OnChange" events for the INPUT element with the the value "edit1" for the NAME attribute. The EVENT attribute defines the event name. This is either one of the intrinsic events, or an event specific to this object. The FOR attribute is used to bind the handler to appropriate HTML elements. It uses the URL fragment identifier to provide a flexible means of addressing within HTML documents. It has the following syntax:
FOR = " URL#expression "
Typically the SCRIPT element is in the same document as the HTML elements it binds to. As a result the URL part is typically void. The expression is a URL fragment identifier with its syntax matching one of the following:
id:id-value
This is used when the script binds to a single HTML element. The element must have an ID attribute with a matching value.
field:field-name
This is used when the handler is to be used for one or more form fields with the same NAME attribute
field:form-name/field-name
When there are several forms in an HTML document, there may be a possibility of the same NAME value being used by both forms. This syntax allows you to prefix the field NAME by the corresponding name for the enclosing FORM element.
tag:tag-name
This is used when a handler is to be used with all elements with the same tag name
tag:tag-name/class-name
Similar to the above, but this syntax allows you to restict the handler to be used with those elements that belong to a given subclass. That is have matching CLASS values.
... a bunch of motivating examples are needed, either here or in a separate document ...
Parameter Passing
Most events are associated with one or more parameters. For some languages, for example HyperTalk, the parameters are passed via global variables (e.g. the mouse location is accessible via "the clickLoc"). This is problematic if the global variables are overwritten by subsequent events of the same type. Other languages require explit parameter lists. The type of a parameter may be implicit, according to its position in the list, or given explicitly as with C++. Some languages use tagged data that include type info within each parameter (e.g. Poplog).
(a) Implicit Parameters
With this approach, the names and types of parameters are implied by the event name. In the example below, button and location are implicit for all OnClick events: (b) Named ParametersWith this approach, the EVENT attribute includes a bracketed list of parameter names after the event name. The types of the parameters are implicit depending on the event name and position in the list. This also works well for languages with tagged data types, as then, the parameters carry their own type information. The above example becomes: (c) Typed ParametersWith this approach, typing information is included with the parameter names. The types need to be mapped to the typing system in use for each scripting language. The example becomes: For this approach to work, it seems like a standard syntax will be needed for typing information. Would the following be okay? param-name as type-nameWhere type-name is one of: integer, string, real, point, or object for a self typed object.

Sharepoint 2007 Demos

2007-03-09T14:04:00.000-08:00

Sharepoint 2007 demos with deployed sample templates

http://www.wssdemo.com/application

Thanks wssdemo!!

Sharepoint 2007 - problem with default.aspx

2007-01-24T09:56:00.000-08:00

I created a site with a default.aspx page customized that works fine.
Then i created a template based on this site
Then i created a site base on the template.
Sp created it but when i navigate the defualt.aspx page of the new site i get this message

The requested page cannot be viewed because it is not configured properly. It has been disconnected from its page layout. Click here to go to Page Settings and reconnect this page to a page layout.

Sharepoint 2007 problem adding a webpart on a Spanish site

2007-01-18T08:22:00.000-08:00

I got the next message after adding a Content Query Tool Part.

No se puede crear una dirección URL segura en caché para "PickerTreeDialog.js"; archivo no encontrado. Compruebe que el archivo existe en el directorio de diseños.

Now i am trying to see how to solve it...

Well, i solved it copying the file PickerTreeDialog.js from

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\1033

to

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\3082

Sharepoint 2007 problem adding a webpart on a Spanish site

2007-01-17T13:37:00.000-08:00

I got the next message after adding a Content Query Tool Part.

No se puede crear una dirección URL segura en caché para "styles/controls.css"; archivo no encontrado. Compruebe que el archivo existe en el directorio de diseños.

Now i am trying to see how to solve it...

Well, i solved it copying the file controls.css from

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\1033\STYLES

to

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\3082\STYLES

Sharepoint 2007 Content Query Tool Part Custom Fields

2007-01-16T14:02:00.000-08:00

How to: Display Custom Fields in a Content Query Web Part
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.

The Web Part has two major aspects: Query and Presentation. Query determines what content you want to show and Presentation determines how you want to style and present the content. You can also attach rules so that only items of a certain type that fit a certain set of rules are shown in the Web Part.

In the tool pane, you can do the following:

Select the scope of the query. You can configure the Web Part to query items across the entire site collection, from a specific site in the site collection, or a particular list.

Select the type of list to query items from.

Specify which content types the Web Part should display.

Select additional filters to control what content the Web Part displays. For example, one filter may be used to show only Article Pages that were authored by a particular user.

Select sorting and grouping options to determine the order in which items appear.

Select styling options to control how the Web Part presents items and group headers.

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.

This topic explains how to include additional columns in the Web Part's query and how to programmatically instruct the Web Part to rename columns to names the default XSLT transformation expects, and then render the columns using the default XSLT transformation styles.

To understand the steps involved in this customization, let’s consider a scenario. Let's say you have a Knowledge Base Articles content type with the following columns:

KB Title (Text)

Product (Text)

Version (Text)

Status (Choice)

You associate a document library titled Knowledge Base Articles with the content type that contains Knowledge Base articles. You want to display the Knowledge Base articles content in a Content Query Web Part on your home page, display the Title column as the Title field, and display the Product column as the Description field in the Web Part. To do this, perform the following steps.

To display custom fields in a Content Query Web Part
Add a Content Query Web Part to a page.

In the Query section, set the Source to show items from the Knowledge Base Articles document library (list). Set the list type and content type accordingly.

In the Presentation section, set the Item Style to Title and description.

Edit the properties in the Web Part file to display custom fields. To access the .webpart file for the Web Part, on the Web Part's edit menu, click Export.

Office SharePoint Server 2007 generates a .webpart file with the complete set of properties that are available for this Web Part. The .webpart file is an XML file that you can edit using a text editor.

In the .webpart file, locate the CommonViewFields property. Use this property to specify the additional fields you want to display in the Web Part. Add the internal names of the columns and the type.

Copy Code
KB_x0020_Title,Text;Product,Text;
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.

Map these internal column names to the columns' Title and Description present in the XSLT transformations. To do this, edit the DataColumnRenames property.

Copy Code
KB_x0020_Title,Title;Product,Description
Note:
The default XSLT transformations can render the following four fields: Title, Description, LinkUrl, and ImageUrl. In your DataColumnRenames property, verify that the names you specify match the names in the XSLT transformations; that is, Title, Description, LinkUrl, and ImageUrl.

Save the .webpart file locally.

In the Web page, delete the Content Query Web Part you added in step 1.

Import the .webpart file and add the Web Part to your page. To import the .webpart file, click Page, click Add Web Parts, and then click Import. Browse to the .webpart file, and then click Upload.

Drag the Web Part to the appropriate zone in the page. The Web Part should display the Knowledge Base Title and the product name.

If you want the Status or the Version column to appear in addition to the KB title and product, modify the XSLT transformation and add the rendering for the additional columns.

Note:
The previous example shows you how to edit an individual Web Part on one page to include custom fields in the rendered output. However, you can also make changes to Web Parts using an editor such as Microsoft Office SharePoint Designer 2007. Office SharePoint Designer 2007 is a good tool to use if you want to customize a Web Part that is used on a page layout, and automatically include that custom Web Part in pages that are created using that layout. You can also add customized Web Parts to the Web Part gallery, which makes them available for dragging and dropping into Web Part zones of new pages.

Sharepoint - An unexpected error has occurred.

2006-10-23T15:35:00.000-07:00

An unexpected error has occurred.

Web Parts Maintenance Page: If you have permission, you can use this page to temporarily disable Web Parts or remove personal settings. For more information, contact your site administrator.

This a a message sometimes appears me while i am developing a webpart.
So what i need to do to is to Open the page with FrontPage delete the webpart and add it again.
:)

Sharepoint 2007 missing "Save site as template"

2006-08-28T07:42:00.000-07:00

While i was experimenting with my first site, i wanted to save this as template and have not found this functionality on the Beta Version, but i found that you can navigate the page _layouts/savetmpl.aspx while you are on your site and you ll can generate a template.

Sharepoint 2007 experience

2006-08-23T08:40:00.000-07:00

I went on trying to build a worflow for a Document library but when i could not write a valid approver. I tried writing it, using the users dialog, but when i lost focus on the textbox, it always was blanked. So i canceled the process when to the document lirary and started again with the workflow build. Then it worked fine. (?)

Sharepoint 2007 workflows problem

2006-08-23T07:58:00.000-07:00

I tried to make my first workflow on Sharepoint 2007 but after some steps i got the next error:

"The form cannot be displayed because session state is not available."

but it can be solved modyfing the web.config file, uncommenting the line where you can read:

add name="Session" type="System.Web.SessionState.SessionStateModule"/

Packaging and Deploying Sharepoint Web Parts

2006-07-17T08:38:00.000-07:00

Just another webmemory

SharePoint Products and Technologies Tool: WPPackager for Packaging and Deploying Web Parts

http://www.microsoft.com/downloads/details.aspx?FamilyID=0fda5912-c136-4b44-911a-011adfcc66e3&DisplayLang=en

Generates an installer for Sharepoint Web Parts

Sharepoint - Object reference not set to an instance of an object

2006-04-17T06:34:00.000-07:00

I got the "Object reference not set to an instance of an object" error trying to know the field value of a spListItem.

It happens that that works ok if this ListItem comes from a spList but no if it comes from a spView.

For example i added field called target and an item without value to a list and at a list field i did not get the error but it happened on a view.

Sharepoint - The following file(s) have been blocked by the administrator

2006-03-31T05:23:00.000-08:00

Sometimes on different Servers i got the following error trying to upload an Access or another kind of file...

The following file(s) have been blocked by the administrator:
Administration.mdb

This can be solved doing the following:

- Go to Start/Programs/Administrative tools/Sharepoint Central Administration

-"Security Configuration" section
-"Manage Blocked File Types"

-Find the MDB extension at the list

-Remove it

-Click the "OK" button

Sharepoint Versions and service packs

2006-03-09T05:37:00.000-08:00

Versión Windows SharePoint Services or SharePoint Portal Server 2003 Windows SharePoint Services SharePoint Portal Server 2003

Original 6.0.2.5530 11.0.5704.0
SP1 6.0.2.6361 11.0.6715.0
SP1-Sec 6.0.2.6411 N/D
SP2 6.0.2.6568 11.0.8126.0

Sharepoint links customization

2005-12-16T12:00:00.000-08:00

Sometimes some sharepoint users need to click a link on certain Sharepoint pages and open the link on a different target than the current window, so they can not open the link on a new window.
This can be solved if we can add or modify the target Attribute on the A tag where the link is contained.

You can do it by opening the Sharepoint page on Microsoft Office Frontpage.

Search the A tag and edit it adding the target attribute with the _new value

Save it and it is done.

As always , if you need some help just email me.

webmemory inaugurated

2005-12-13T07:53:00.000-08:00

A new blog called webMemory was created.

Take a look at http://webmemory.blogspot.com/

Sharepoint stsadm commands

2005-10-28T12:50:00.000-07:00

Just a shortcut for me, when i do not remember the name of the Sharepoint command so as to add a template.

http://www.microsoft.com/resources/documentation/wss/2/all/adminguide/en-us/stsk01.mspx

Request timed out

2005-09-06T11:12:00.000-07:00

I was testing a webpart and got the next message error

Server Error in '/' Application.Request timed out.Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Web.HttpException: Request timed out.Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.Stack Trace: [HttpException (0x80004005): Request timed out.]

After try changes on many timeouts configuration files, it finally worked with the httpruntime executiontimeout located at the machine.config file.

Sharepoint, deploying aspx pages

2005-08-22T09:14:00.000-07:00

That is another memory help for me.

When i want to add asp.net pages to be used from a Sharepoint Site i must copy them to the ...\60\Template\Layouts\MyFolder Folder.
That must be done when i developed an asp.net aspx page and want to deploy them to the Sharepoint server.

And the way to call them 'd be http://server/site/_layouts/MyFolder/mypage.aspx

Unable to display this Web Part

2005-08-03T12:04:00.000-07:00

Today i tried to navigate a Sharepoint site where normally i used to navigate without problems, but i got the next error message.

Unable to display this Web Part. To troubleshoot the problem, open this Web page in a Windows SharePoint Services-compatible HTML editor such as FrontPage. If the problem persists, contact your Web server administrator.

Trying and trying this was solved when i restarted IIS.

Backup/Restore wss sites: using smigrate

2005-06-29T07:17:00.000-07:00

1. Use smigrate to backup a site .
Example syntax: smigrate -w http://sps/sites/example -f d:\bckp\backup.fwp

2. Use a Cabinet decompression utility such as EXTRACT to decompress all of the files out of the FWP file.
You can get the EXTRACT utility from the Microsoft CAB SDK at: http://msdn.microsoft.com/library/en-us/dncabsdk/html/cabdl.asp, althoughany utility that can decompress CAB files will suffice.

Example syntax: EXTRACT /A /E backup.fwp /L c:\files

3. Browse to the "files" folder and open the manifest.xml file.

4. Change location (LCID) and language settings and any custom list type entries to built-in list type entries.
For example, to turn location and language settings:
vti_defaultlanguage="SWde"tovti_defaultlanguage="SRen-us"
Same thing with keys "LCID" Value "1033" - is for US"1031" is for DE (search for string 1031\ and replace it with 1033\)

5. Save your changes.

6. Use a Cabinet compression utility such as CABARC to compress all of the files in the "files" folder into a FWP file.
You can get the CABARC utility from the Microsoft CAB SDK at: http://msdn.microsoft.com/library/en-us/dncabsdk/html/cabdl.asp, although any utility that can generate CAB files will suffice.

Example syntax: CABARC N backup.fwp c:\files\*.*

7. Use smigrate to restore the fixed FWP file to a new site but first you have to create a project site without using a template.

Example syntax: smigrate -r -w http://sps/sites/example -f backup.fwp

Note that each site has its own manifest file.
If you don't use the "-e" switch with smigrate during the backup, then smigrate will also backup allof the sites below the one you specify.
If that happens, you will need to alter the manifest file for each site in the FWP below the one you specified.
You can find the manifest files for a site's immediate child sites listed in the "" section in the manifest file.
Sometimes you see greater font size then excepted. Open site default.aspx in frontpage and edit it.
In html code search after /1031/ows.css and change it to /1033/ows.css.

Generally I publish things that i have not found easily, but always those things are published because are useful to me. In that case i found it easily on the Tarik Eker Blog, but i published it on my blog as a fast ShorCut to me.

OnSaveRequest Event tip

2005-06-15T09:15:00.000-07:00

OnSaveRequest Event

Occurs when the save operation is invoked from the Microsoft Office InfoPath 2003 user interface or by using the Save or SaveAs method of the XDocument object in the InfoPath object model.
Function XDocument::OnSaveRequest(ByRef pEvent As SaveEvent)
pEvent Required SaveEvent. A reference to the SaveEvent object.
Remarks
If the ReturnStatus property of the SaveEvent object is set to False, InfoPath cancels the save operation. If an error occurs in the code for the OnSaveRequest event handler, InfoPath ignores the error and relies on the ReturnStatus property of the SaveEvent object. If the ReturnStatus property is not explicitly set, the default value of False is used.
The ReturnStatus property works in conjunction with the IsCancelled property when the InfoPath form is closing. If the document has changes that have not been saved and the user cancels the save operation, the IsCancelled property can be set to True to allow InfoPath to close.
Note This object model member is not supported when the Disable Service Pack features option on the Advanced tab of the Options dialog box in InfoPath is selected or when Microsoft Office 2003 Service Pack 1 or later is not installed. Any form that implements this object model member in its code will generate an error message if it is opened in InfoPath when service pack features are disabled or unavailable.
Example
In the following example, the OnSaveRequest event handler is used to create an XMLHTTP object for transporting the form's underlying XML document:function XDocument::OnSaveRequest(eventObj)
{
// Write the code to be run before saving here.
XDocument.UI.Alert("Begin saving form.");
eventObj.IsCancelled = eventObj.PerformSaveOperation();
// Write the code to be run after saving here.
XDocument.UI.Alert("Form saved.");
eventObj.ReturnStatus = true;
}

I 'd like to add that it is needed a little configuration item so as to that event be fired, because you 'll have the problem that the event is not fired.

You must do some steps:

At Design Mode of your Infopath Form
Go to Tools/Form Options menu
On the Open & Save Tab, On the Save behavior section, check the "Save using custom code" option.

Sharepoint Events

2005-06-09T08:02:00.000-07:00

Today i needed to trap some events on a Sharepoint Document Library

And i found this sample that works fine.

Take a look at

http://msdn.microsoft.com/office/understanding/sharepoint/articles/default.aspx?pull=/library/en-us/odc_SP2003_ta/html/sharepoint_wsseventing.asp#odc_sharepoint_wsseventing_enablingeventsfordocumentlibraries

Reapplying a template to a Sharepoint Site

2005-05-18T07:58:00.000-07:00

I needed to reapply a template to a site previously created, but is seems that it is not possible.
At Sharepoint , i created a site applying a template, but then the template changed, and i needed to apply it to the site.

Unfortunately you cannot apply a template to a site once it is created, as far as I know. However what you can do is apply a theme to a site once it has been created. I would suggest using that route or dropping and recreating all of the sites with the new template. Sorry the answer isn't a nice friendly one.

You can find this info at

Reapplying a template

Translating DataViewWebPart Titles to another language

2005-05-16T11:59:00.000-07:00

Translating a DataView WebPart to another language.

Today i needed to modify a template i have.
It did not seem to be difficult because i must take a template and translate words to spanish.
But when i needed to modify the titles of a webpart called DataView with FronPage it did not give any possibility so as to do it.
The problem began when i modified , to spanish, the Fields Name but the fields titles on the grid remained on English.
So that i carefully found where was the fieldtitle attribute on the webpart and modified it to a spanish word.

I realized to do that , previously going to the Insert/Database/Data View Menu at FrontPage and inserting a new DataViewWebPart with the previous translated fields.

Sql database comparison tool

2005-05-09T07:28:00.000-07:00

That is just help to my memory, when i am trying to search a tool so as to compare two Microsoft® SQL Server© databases.

Apex SQL Diff is a server based, high speed database comparison tool that will analyze the differences in tables, procedures, views, users etc between two Microsoft® SQL Server© databases in seconds.

It can be found here:

Apex Sql Diff

Multiple filters on a SQL WHERE clause

2005-05-02T12:19:00.000-07:00

Sometimes I had to develop a report or a something to show data, but previously the user‘d have the possibility to apply multiple filters so as so view the info that wants to be found.

As ever I designed the User Interface with the filters then passed the filters through the different layers and finally, they came to a stored procedure that makes the query.

It returns the data and that’s all.

Several times I heard some colleagues telling that they must show data applying multiple filters and they finally at the stored procedure did not find another way to make the query than building a string and then executing it with the EXEC sql Command or making several SELECT sentences.

I published an article about applying several filters on on a SQL WHERE clause

You can find it at

http://www.codeproject.com/useritems/sql_WHERE_clause.asp

Exec Task in Nant 0.84

2005-04-27T13:09:00.000-07:00

Today i needed to add a line to the Nant file so as to execute a command line.

Browsing the Task List , i found that there is one called exex
(http://nant.sourceforge.net/release/latest/help/tasks/exec.html)

Then i wrote the command i needed to execute .
Something like this "rs -iblablabla -ublabla -pblabla"

But executing the command line, Nant intended to execute the next:

rs "-iblablabla -ublabla -pblabla" (Adding quotes)

So that it derived on an error .

Lamentably i can not install the 0.85 version that solves the problem, so thinking a little I solved it executing a .bat file and writing my command on it and finally executing what i needed.

So the configuration file keeps in that way:

exec program="mirs.bat"/

That solved my problem when Nant adds quotes while executing a command, but in some cases this can not solve your situation and you'll need to install the 0.85 version.

Reporting Services - Expanding a Chart Subreport

2005-04-13T11:54:00.000-07:00

I had a subreport with a chart, but i did not like how it was drawn because it was displayed with the chart and some legends at its right side, so that the chart width was decreased so as to the legends could be seen expanded.

I prefered to see all the chart on the same size so that i go to the report designer and on the chart properties , at the Legend tab i modified it to write the legends with row layout centered at bottom.