Search results for 'app:weblogs' matching tag 'Sharepoint'

Posters descargables de SharePoint 2010

haaron — Mon, 26 Oct 2009 05:00:00 GMT

Mas información de SharePoint 2010. Aquí unos posters.

Poster and downloads	Description
Services Download: Visio, PDF, XPS	Services architecture, including and common ways to deploy services in your overall solution design.
Cross-farm Services Download: Visio, PDF, XPS	Illustrates how to deploy services across farms to provide centralized administration of services.
Topologies for SharePoint Server 2010 Download: Visio, PDF, XPS	Describes common ways to build and scale farm topologies, including planning which servers to start services on.
Hosting Environments in SharePoint Server 2010 Download: Visio, PDF, XPS	Summarizes the support for hosting environments and illustrates common hosting architectures.
Business Connectivity Services Model Download: Visio, PDF, XPS	This model poster describes the architecture of Microsoft Business Connectivity Services in SharePoint Server 2010 and provides information about how to create solutions that are based on the service. Use this model with the following article: Business Connectivity Services overview (SharePoint Server 2010)
SharePoint 2010 Upgrade Planning Download: Visio, PDF, XPS	This model covers planning for an upgrade from Microsoft Office SharePoint Server 2007 to SharePoint Server 2010. It includes information about the following: Upgrade requirements: Hardware, operating system, and database Upgrade process: specific steps to follow before, during, and after the upgrade Use this model with the following article: Upgrading to SharePoint Server 2010
SharePoint Server 2010 Upgrade Approaches Download: Visio, PDF, XPS	This model helps you understand the in-place, database attach, and hybrid approaches to upgrading from Office SharePoint Server 2007 to SharePoint Server 2010. See the farm topologies before, during, and after upgrade Compare the advantages of each type of upgrade approach Use this model with the following articles: Determine upgrade approach (SharePoint Server 2010) Upgrade process overview (SharePoint Server 2010)
SharePoint Server 2010 — Test Your Upgrade Process Download: Visio, PDF, XPS	This model explains the methodology for testing the upgrade process before upgrading from Office SharePoint Server 2007 to SharePoint Server 2010. Understand the goals for testing your upgrade process: customizations, hardware, timing, planning See specific steps to follow for testing your upgrade process Use this model with the following article: Use a trial upgrade to find potential issues (SharePoint Server 2010)
SharePoint Server 2010 — Services Upgrade Download: Visio, PDF, XPS	This model covers upgrading services from Office SharePoint Server 2007 to SharePoint Server 2010. Considerations for specific services: Personalization, Search, InfoPath Forms, Excel, Business Data Catalog, Single Sign-on In-place upgrade with services Database attach upgrade with services
Choose a tool for business intelligence in SharePoint Server 2010 Download: Visio, PDF, XPS	This model covers an overview of business intelligence in SharePoint Server 2010 and provides you with the following information. An overview of each business intelligence service and when you might use the service. Architecture for application of the business intelligence services and how they work together in a topology. A list of possible data sources for each business intelligence service.

Fuente: http://blogs.technet.com/tothesharepoint/archive/2009/10/23/3288841.aspx

A video on Access 2010

Anonymous — Wed, 21 Oct 2009 05:00:00 GMT

I recently posted on my experiences of Access 2010, well if you want to know more have a look at the video by Clint Covington and Ryan McMinn on Channel 9

Access Services in SharePoint 2010 or: How I Learned to Stop Worrying and Love Access 2010

Anonymous — Mon, 19 Oct 2009 05:00:00 GMT

So what I have I been doing of late? The blog has been a bit quiet. Well I have been having a good look at Access Services in SharePoint 2010. This has been an interesting experience, as I am not historically what you might call an avid Access developer.

Like most .NET developers I had looked as Access as more of a file format than an application, something from the past. Something that I might use for a small data store, maybe in a web application hosted on a cheaper ISP that does not provide ‘a real’ SQL DB, or where an XML data files don’t seem right, often because I just can’t be bothered to work out the XPATH. When using Access as a data format it seems easier to get at my data using basic hand crafted SQL commands or maybe at most via a OLEDB Data Adaptor/DataSet. All very old old school. Thinking about Access in this way just seems an easy way out, playing it safe with the knowledge I have. I don’t for a second propose that this a good idea, you should not be looking at using any technology just because it is there and you already know it. There are obvious downsides, using Access in this manner meant that from the ADO.NET developer side I could not:

make use of the newer lambda expression based syntax of LINQ
make use of newer ORM solutions such as Entity Framework or nHibernate.

But equally, by treating Access as just a data format I was not able to make use of it as the Rapid Development tool it is. I was too hung up in the unpleasant idea of an MDB sitting of a server being poor at locking and saturating the network with unwanted traffic. I was not even considering Access as a front end to a MS-SQL solution, and it is not as if that is new technology, it has been around for ages. I was just sitting happily with my prejudices.

I don’t think this position is that rare for .NET developers these days. Access seems just looked down upon as something old in the Office pack that is best ignored, no good would come of using it in a business environment.

So enters Office 2010 and SharePoint 2010 Access Services, for me this changes the game. For those who don’t know this technology, you can create an Access database locally on your PC then publish it to SharePoint. Tables become SharePoint lists, macros become workflows and forms well become forms. Access becomes a RAD tool to create data driven SharePoint sites.

So how has this new technology been working for me? Well I can’t say I have grown to love the Access client, but I think that is mostly down to that fact that I am still not thinking right for it. Access is all about data binding, you don’t have to think about what form fields need to be copied to which DB columns, the wizards make a really good attempt to design forms for you based on the relationship of the tables in your DB and this just all seem unnatural to me. I think this is because I am usually working with design patterns to reduces the linkage between forms and data to a minimum e.g. the MVC pattern, and so consider this good practice; automated data binding seems seems wrong. So in Access I keep wanting to build things from first principles, but this is just not sensible. Better to let the tool get you close and then you add the polish, put away any thoughts of implementing design patterns as you would in a language such as C# or VB.NET.

I think this is the key to the degree of irritation I feel with the product, if you have got used to architecting from the ground up, especially in a Test Driven Development style, you have to turn everything on it head. It feels like you are cheating, not doing the job properly.

But wait! look at the benefits. A while ago I was involved in a project to provide a resource management data driven web site that was hosted within SharePoint. It contained the usual things, data entry forms, links to SQL and reports. It took a couple of weeks to build. I think I could write the same system in Access with SharePoint 2010 in an afternoon, and would be happy to have a client’s business analyst sit next to me while I did it, in a pair programming style, to design the forms, report layouts and columns as I went along. For the smaller scale data driven site Access Services is a great tool, but obviously it is not perfect. I do keep hitting points where I think ‘if I were in C# I could just do that’ but then I remember ‘yes but it would take would have taken me three days to get here not an hour’. Most project don’t need that last 10-20% you can only reach on .NET custom code, the client with be far happier with 80% done quickly and flexibly rather than 95% done a lot later. Also we have to factor in my relative lack of experience with Access as a RAD tool, reducing the productivity that could potentially be achieved by a more experienced Access developer.

Actually the bulk of the time I have spent has been on looking at how you can extend Access Service to reach that last 20% of functionality, and it not that hard. The key to remember is that the Access Services are just built on standard SharePoint objects. Ok there is a new service running to render the pages, but underneath there are just SharePoint lists and workflow, and where these exist there are events that you can programmatically handle. I have found that by trapping events such as ItemAdd() for the Access created SharePoint lists there is no real limit to what you can achieve via the SharePoint Object Model. And this development process is made even easier by the new Visual Studio 2010 templates for SharePoint features. If nothing else the fact that all the templates create a WSP for deployment as standard makes for far more robust feature development.

There is one major difference between a standard SharePoint site and one created by Access, and it is that SharePoint Designer cannot open the Access site. I thought this would be an issue when I first heard about the limitation, but it turn out not to be. Anything you might have wanted to do in SharePoint Designer you can do quicker and easier in Access for this type of data driven site. Ok the range of things you can do is more limited, but again you get that 80% you need with much less pain.

So how has my experience with Access 2010 been? Exasperating, frustrating but undeniably productive. I am not sure it is the right product for an ISV style company who want to roll out single solution to many client sites (but it could be used for this if needed via the SharePoint site template gallery); but for a smaller data driven site (with or without custom extensions) written within an IT department it is a very strong contender. Taking Access in many ways back to it roots.

So if you need small data driven sites I would suggest you put aside your prejudices and have a look at the beta program for Office/SharePoint 2010, I think you will be surprised.

Da inicio el flujo de informacion sobre SharePoint 2010

haaron — Mon, 19 Oct 2009 05:00:00 GMT

A tan solo unas horas de dar inicio el SharePoint Conference, Microsoft libera un conjunto de posters sobre actualizacion a plataforma SharePoint 2010.

Estaremos al pendiente.

SharePoint 2007 on Windows Server 2008 R2

laflour — Sun, 11 Oct 2009 05:00:00 GMT

When you consider using Windows Server 2008 R2 for your SharePoint 2007 platform you need to put additional effort to configure and install SharePoint properly.

There are few actions you need to undertake for the successful deployment of SharePoint on R2.

1) You can only install SharePoint 2007 SP2 on R2 version. Unfortunately, MS doesn’t provide SharePoint 2007 SP2 slipstream package, so you need to create one by yourself (Take into account, that you need to delete everything from the “\Updates” folder in case of using SP1 slipstream)

2) After you complete installation you will find that whenever you are trying to open the Central Administration the login and password are requested, regardless of your efforts to add Central Administration to the Trust Zone and set the option to logon automatically with the user’s name/password. This is a new change in security of Vista and Windows 7. To remove the login prompt you need to add a key “AuthForwardServerList” to the windows registry. Read the following guidelines.

3) When you create a new site and try to open it you can find the situation when login dialog box is prompted, but you end up with the white screen after you entering credentials three times. Usually, you navigate to c:\Windows\System32\drivers\etc\ folder, open the “hosts” file and add an alias for your site to solve this problem. But, under some circumstances this wont help you in R2, and moreover, your can’t open the site via “localhost” name. The solution is to add the alias not only to host file, but in “lmhosts.sam” as well

SharePoint 2007 on Windows Server 2008 R2

laflour — Sun, 11 Oct 2009 05:00:00 GMT

When you consider using Windows Server 2008 R2 for your SharePoint 2007 platform you need to put additional effort to configure and install SharePoint properly.

There are a few actions you need to undertake for the successful deployment of SharePoint on R2.

SharePoint 2007 32bit->64bit migration Strategy

laflour — Wed, 07 Oct 2009 05:00:00 GMT

As you know, Microsoft will release SharePoint 2010 public version soon, and there is no space for 32bit versions anymore. All server stuff come in 64bits only – Windows Server 2008 R2, SharePoint 2010 and etc, so, we need to be ready for this.

I recommend to watch New Zealand TechEd session “Upgrade Planning and Guidance OFC306” that describes how to plan you 32bit –> 63 bit migration for SharePoint Farm

Hospedaje SharePoint una alternativa en estos tiempos

haaron — Thu, 24 Sep 2009 05:00:00 GMT

Soy una PyME que no tiene un departamento de TI, necesito compartir archivos y mejorara la comunicación de mis colaboradores pero desafortunadamente no está dentro de mi estrategia de negocio invertir en hardware y licenciamiento de software. ¿Qué puedo hacer?

Hay distintas alternativas disponibles en la industria de TI. Cada alternativa tiene sus pros y contras desde el punto de vista costo total de propiedad y retorno de inversión. Una tendencia que en los últimos años se ha venido incrementando es la del uso de software como servicio. Básicamente consiste en hacer uso de software o soluciones informáticas que proveedores nos pueden habilitar como un servicio disponible a cambio de una renta establecida. Al final del día no se termina haciendo una inversión en hardware ni en recursos especializados encargados de soportar dicha plataforma. Insisto que en ciertos escenarios es aplicable este enfoque.

Mis amigos de SolucionesSharePoint.com han puesto a disposición como servicio la plataforma Windows SharePoint Services 3.0 o WSS 3.0 por sus siglas, un ambiente de colaboración basado en sitios web que empleados de una organización pueden utilizar para compartir información y comunicarse de mejor manera a través de internet haciendo uso de las múltiples herramientas informáticas que vienen pre fabricadas en el producto.

Herramientas como:

Repositorio de:
- Documentos
- Imágenes
- Paginas
- Formularios
Listas de:
- Anuncios
- Contactos
- Panel de Discusiones
- Enlaces o direcciones de internet
- Calendario
- Tareas
- Tareas de proyecto
- Tareas de seguimiento de asuntos
- Encuestas
Sitios Web para:
- Colaboración Departamental
- Colaboración con Documentos
- Seguimiento de Reuniones
- Programación de ausencias y vacaciones
- Base de datos de errores
- Centro de llamadas
- Administración de contactos
- Sitio de soporte y proceso de cumplimiento
- Biblioteca y revisión de documentos
- Planificación de eventos
- Sitio de aprobación y rembolso de gastos
- Servicio de asistencia y retardos
- Seguimiento de inventario
- Área de trabajo de equipo de TI
- Administración de ofertas de empleo y entrevistas
- Base de conocimiento
- Seguimiento de prestamos
- Administración y seguimiento de active físico
- Administración de solicitudes de cambio
- Presupuesto y seguimiento a proyectos
- Área de trabajo y seguimiento a proyectos
- Reservación de salas y equipo
- Canalización de ventas potenciales

Acércate a de SolucionesSharePoint.com para que con una inversión bastante decente puedas contar con la posibilidad de ofrecer a tu empresa una solución rentable a las necesidades de tus empleados. Así mismo SolucionesSharePoint.com cuentan con una planta de consultores en colaboración que te apoyaran a definir la mejor estrategia para explorar al máximo las herramientas pre fabricadas de SharePoint para dar una solución concreta a tu necesidad en particular. Es aquí donde veo un valor adicional a esta empresa ademas de su servicio.

Suerte!

Panel de Edición de WebPart con Silverlight

haaron — Tue, 22 Sep 2009 05:00:00 GMT

Hoy quiero hacer referencia al trabajo que mi buen amigo Gerardo Reyes ha hecho en su último post sobre cómo crear paneles de edición de WebParts SharePoint utilizando Silverlight para ofrecer una experiencia de usuario mejorada cuando configuramos nuestros WebParts. Muy interesante ya que sobre este punto no se ha visto mucho y da una perspectiva util al respecto.

http://gerardo-reyes.blogspot.com/2009/09/creando-editor-parts-personalizados.html

Saludos!

SharePoint Saturday Melbourne! 14th November

BenWalters — Tue, 22 Sep 2009 05:00:00 GMT

It’s now officially official, SharePoint Saturday Melbourne is locked in and scheduled for November 14th the site is now live and we are accepting Speaker Submissions so head on over to http://www.sharepointsaturday.org/melbourne and start getting those presentation idea’s down, we will stop accepting session submissions on Oct 21st so make sure you get your ideas in, don’t forget to when making submissions this will be occurring after the SharePoint Conference in Vegas so we should have a lot more freedom to talk about some of the new features of 2010. We’ll also have event registration open in the coming days so watch this space.

“Join SharePoint architects, developers, and other professionals that work with Microsoft Office SharePoint Server 2007 for ‘SharePoint Saturday’ event. SharePoint Saturday is an educational, informative & lively day filled with sessions from respected SharePoint professionals & MVPs, covering a wide variety of SharePoint-orientated topics. SharePoint Saturday is FREE, open to the public and is your local chance to immerse yourself in SharePoint!”

Also be sure to follow http://www.twitter.com/spsmelbourne for all the latest info around the event. We are hoping we can top Sydney's attendance this time around and make this the biggest SPS event in Australia to date.