Actualización: 04/25/08: Foi recuperar o atraso nalgúns artigos e atopei unha ligazón a este artigo: http://www.networkworld.com/news/2008/032608-microsoft-sharepoint.html?page=1. I make note of it because in addition to asking, "how do I learn sharepoint?", some people ask "why should I learn sharepoint?". That article partly answers the later.

Nos últimos meses, unha ducia ou máis persoas de todo o planeta foron me correo-e e facer a pregunta xeral, "How do I learn SharePoint?"

Estou case autoritaria, pero eu tiven algún éxito (e tratando de mellorar o tempo) so I thought I’d document my personal road map. Others may find it valuable.

Antes de facelo, Eu só quero observar que é evidente para min, con base neses correos electrónicos persoais e do número aínda maior de MSDN / SharePoint mensaxes Universidade da mesma natureza, that there is huge developer interest in getting up to speed with WSS/MOSS. I wonder what it’s going to be like a year from now … máis doado atopar bos talentos SharePoint? The same? Are folks committing themselves to the platform at a rate sufficient to keep up with demand for good resources? How could you even figure something like that out short of a WAG?

Guión de Paul

I was full time employed by the good folk at Conchango while I followed this road map. This means that from a learning perspective, I was actively engaged in projects as I followed the steps I outline below.

Algúns termos básicos

Para as persoas que entran neste mundo, existen dous acrónimos principais:

• WSS: Windows SharePoint Services
• Moss: Microsoft Office SharePoint Server

WSS is "free" na medida en que está xunto co Windows Server 2003 (ou, polo menos, se pode descargar de MS). I put quotes around free because you need a box, O válida a licenza / S e probablemente SQL (though there’s a "free" tipo de SQL ben).

MOSS is built on top of WSS and extends it. There is no MOSS without WSS. MOSS is not free.

Quizais non sexa un día, pero logo tes algunha familiaridade básica coa plataforma, it’s important to learn the differences. Por exemplo, unha poderosa parte web, a web Part de Consulta de Contido, is a MOSS feature and not available WSS. People often make the incorrect assumption that CQWP is available in WSS and then end up scrambling for a stop-gap measure when they realize their error.

Bater os libros

I started working with WSS/MOSS on about 01/02/2007. I had a little prior experience with SPS 2003 but very little. To get myself started, Eu compras o dous libros aquí (http://paulgalvin.spaces.live.com/lists/cns!1CC1EDB3DAA9B8AA!203/).

I started with the big blue administration book. Naturally, it covers administration. Á vez, Ofrece un levantamento de todas as características Moss (e as características do WSS ben).

Para min, non é tan importante lembrar de todos os varios detalles (ata que chegou o momento de obter a certificación) but it’s good to know the boundaries. (Eu sigo esa mesma visión en primeira persoa shooters que eu xogo na Xbox ou PC — I enter a room and tend to make a counter-clockwise loop until I get back where I started. I just feel better knowing the shape of the box I’m in.)

Despois de ler o libro azul grande, I would read the entire Inside WSS book. It dives deeply into issues that developers care most about.

Crea un ambiente virtual

Co fin de facer calquera desenvolvemento ou usar adecuadamente o medio ambiente, precisa dun sistema operativo completo soprado Windows Server co SharePoint Deseño, Visual Studio 2005 (2008 traballo, pero algunhas ferramentas teñen aínda que ser portado desde a escrita deste artigo), InfoPath 2007 and some other stuff. There are many good blog entries describing this process. I’d have a look at these two:

• Como crear un Moss 2007 VPC Imaxe: The Whole 9 Yards – SharePoint Blog Reporteiro
• Como construír un gran creador VPC para o Desenvolvemento do SharePoint – Blog

Ademais, Andrew Connell compartiu as súas experiencias con VMWare aquí:

• Produtos de virtualización de Microsoft vs. As ofertas de VMWare

Use your favorite search engine to see what other people do. It’s a useful learning exercise in and of itself.

Spend a few minutes angrily denouncing the fact that you need a server environment on which to do development. Pero … don’t bother blogging about it or posting it to MSDN forums. É xa se fixo 🙂. Pola, embrace it and move on. You’ll be better off for it.

Obter a certificación

Creo que o camiño MS SharePoint certificación, que consiste en catro exames, is exhaustive. I suggest that you follow their online preparation guide and do your best to understand each of the areas of the test.

Eu non suggest that you take the exam just to pass it. Eu non suggest that you use one of the "brain dump" style 3rd party "tools" for passing MS tests. If you can take the test, pasalo en base a unha combinación do seu propio estudo dirixido e hands-on experiencia, vai ser un desenvolvedor máis forte e demandante de emprego para el.

There are four tests in two "tracks":

Revelador:

• TS: Microsoft Windows SharePoint Services 3.0 – Desenvolvemento de Aplicacións
• TS: Microsoft Office SharePoint Server 2007 - Desenvolvemento de Aplicacións

Administrador:

• TS: Windows SharePoint Services 3.0, Configurar
• TS: Microsoft Office SharePoint Server 2007, Configurar

I recommend that developers study for all of these exams. You’ll be strong for them, aínda que eu creo que se saltou os exames de administrador, vostede obtería.

Eu atopei a versión WSS ser considerablemente máis reto do que as versións correspondentes Moss, much to my surprise. I was in a class recently and several others made the same point.

Mentres eu estaba estudando para o 70-542 exame (Desenvolvemento Moss) I tracked my study resources. These may be helpful to you as well: http://paulgalvin.spaces.live.com/Blog/cns!1CC1EDB3DAA9B8AA!192.entry

Póñase-se na Comunidade

A comunidade SharePoint é vibrante, forte e crecendo o tempo.

Quere ollar para o seguinte para comezar:

• Blogs
• Foros
• Codeplex
• Chilro

Blogs

Se non entender RSS, stop everything and learn it. It will take 10 minutos para aprendela la, quizais outro 10 minutos para atopar un sitio lector RSS (Eu gusto do lector Google, www.google.com / reader).

Comezar engadindo este blog para o seu lector de RSS 🙂

Seguinte, engadir www.sharepointblogs.com to your reader. They aggregate many blogs into a single feed.

Ao longo do tempo, you’ll find blogs that are not aggregated that way. Just add them individually.

I subscribe to a few dozen blogs which I’ve accumulate over the last year. Se quere, Podo exportar miña lista e correo electrónico.

Eventualmente, you may want to start your own blog. I personally think that a series of blog entries describing a "newbie’s" aprender WSS / Moss progreso sería unha interesante serie. Gustaríame ter feito isto só.

Foros

Eu participo activamente en dous grupos foro: MSDN ea Universidade de SharePoint.

Forums are excellent places to learn. People ask questions ranging from the very simple ("How do I create a site column") ao pánico ("My server is down!") para cuestións de deseño máis hipotéticos.

Despois de obter un sabor da contorna, venture out and start replying. Short of directly interacting with a customer, nada é mellor que este para as mans na experiencia.

Codeplex

Ir a www.codeplex.com.

Check it out e buscar proxectos SharePoint.

Asine o resumo diario Codeplex feed no seu lector de feeds.

Fai todos os novos proxectos do SharePoint para o seu lector de feeds.

Eventualmente, despois de ler os foros e mirando cara abaixo súas propias WSS / Moss demos, considerar a montar o seu propio proxecto CodePlex.

Chilro

Mentres escribo este blog, unha chea de xente SharePoint comezaron a usar Chilro.

It’s hard to characterize Twitter. You’ll just have to check it out yourself.

Conclusión

That wraps up my roadmap and makes me current. I just started using Twitter two weeks ago.

WSS/MOSS is a very cool platform and the community is growing all the time. Use community resources to improve your skills and enjoy the journey!

</final>

Rexístrate para o meu blog.

Actualización: An anonymous person in the comments posts this link: http://www.atidan.com/atidan-collaboration-kit.php

Os usuarios do foro moitas veces unha pregunta como esta:

"I would like to have a calendar at the site level that is populated by events from subsite calendars. Ideally, usuarios en subsites vai crear eventos de calendario, and will have the option of marking them as ‘public.’ Events marked as public will dynamically appear in the shared site calendar. Thus the shared site calendar is a roll-up of all public events from all subsite calendars."

É WSS 3.0 ou Moss 2007, non é posible configurar directamente un "roll-up" calendar. Calendars exist on their own, independente de calquera outro calendario.

Para crear un calendario de roll-up, seguir un destes camiños:

1. Use a Content Query Web Part. This is the easiest solution for MOSS users (WSS non ofrece CQWP). CQWP, por desgraza, does not provide a calendar view of data out of the box. It does provide enormous rendering flexibility (Aquí tes un exemplo) pero por defecto, shows its results in simple list format. In many cases, CQWP probablemente unha boa opción.
2. A more programming-oriented solution would be to use event receivers. Implement event receivers on the subsite calendars that keep their public events in sync with the master calendar. As a given subsite calendar is modified, reach out to the master calendar and update it as needed. This option is available in both WSS 3.0 e Moss.

There are probably other clever solutions to this problem. If you have one or know of one, por favor, deixe un comentario ou enviar correo-e me e eu vou actualizar este post.

</final>

Rexístrate para o meu blog.

Podemos, e non debe crear moitos puntos de vista en listas do SharePoint (bibliotecas de documentos, Contraer personalizadas, etc). SharePoint always lists available views in alphabetical order. We cannot change this using out of the box functionality. If it can be done via customization (e eu non estou seguro que pode), está lonxe de técnico para o usuario final típico.

Se quere controlar a orde en que as listas do SharePoint vistas dispoñibles, simplemente poñer un número ou unha letra para os nomes de vista, como no:

1 – Por tipo de material
2 – Todos os documentos
3 – Data de caducidade

-ou-

A – Por tipo de material
B – Todos os documentos
C – Data de caducidade

I have also created views whose purpose is strictly to feed a KPI. I have been following this naming convention:

Z_KPI_[descrición]

Isto fai que o meu "KPI" exhibicións de aparecer na parte inferior da lista.

</final>

Rexístrate para o meu blog.

Hoxe, I was working with a client and describing how to modify the content query web part and display additional bits of information from a content type.

"Primeiro, configurar o CQWP para conectarse a súas fontes de datos, a continuación, export-lo para a súa estación de traballo, modificar <CommonViewFields>, subir, remove the original and now it’s ‘primed’ to display those other columns. Seguinte, abrir o SharePoint Deseño, navigate to the site collection root and locate ItemStyle.xsl. Copy one of the templates as a useful starting point. Go back and modify the CQWP to make use of this new template. Finalmente, modificar o modelo para facer os seus novos campos! (Non esqueza comprobar-lo de volta para que outros usuarios poden ver os resultados)."

É todo moi claro para min (ea maioría de nós tipo creador do SharePoint) o que está pasando e como el é moi bo, realmente, that the data retrieval aspects of the CQWP are so well-separate from the data presentation aspects. Pero, non é tan fácil de explicar, é?

</ Comezo>

Para filtrar por unha consulta para o Si / Non caixa de verificación titulada "PG Milestone", configurar CQWP como esta:

Este é un dos obvios, xa que-se-sabe-lo, pero difícil de atopar-unha resposta ás preguntas-: Como filtrar nun Si / Non caixa de verificación mediante o Contido Query web Part.

O primeiro resultado da busca I find using the search term "filter yes/no content query web part" é algo totalmente incorrecto, entón eu penso que eu ía poñer isto alí enriba e ver se pode substituír o resultado incorrecto resultados de procura típicos.

É moi fácil: True values = "1" and false values do not equal "1" (moi retro, na realidade).

No exemplo anterior,, I created site column of type "Yes/No (checkbox)" named "PG Milestone". I added it to a doc library, cargado algúns documentos, establecer o valor para unha parella e proba.

</ Comezo>

Actualización 12/04/07: Ver este Microsoft KB (http://support.microsoft.com/kb/923589) Para obter información sobre.

En realidade, verifícase que é, pero intelixente Moss tivo que fan difícil.

My customer does some development work on his MOSS site over the weekend. It’s a bit of a jumble as to what he actually did, pero o resultado final é este:

• He tries to add a site column called "Quantity" e as respostas Moss: "The column name that you entered is already in use or reserved. Choose another name."
• He attempts to add it to another environment and that works. Polo tanto, "Quantity" non é un nome reservado.
• He tries to find an existing site column named "Quantity" in that site collection. He cannot find it.

Eu fixen algunhas investigación, and even some coding, encerado filosófica e, finalmente, descubriron que unha columna chamada Cantidade fixo, de feito, exist. It was in the "_Hidden" group. Hence, que non podería atopalo a través da interface de usuario do SharePoint.

Como foi parar alí? I do not know, pero eu teño unha teoría (ou como a miña muller ía chamalo, "blah blah blah"). Nalgún lugar ao longo da liña, un fabuloso modelo de corenta was added and probably activated at a site in the site collection. It was then deactivated (ou o lugar eliminado). The site column, con todo, remained but in the "_Hidden" group. If someone knows better, por favor me aviso vía e-mail ou engadir nos comentarios.

SharePoint was telling the truth. It’s hardly worth pointing out that that message is not as helpful as it could be. It would be nice to see that message fork into two different messages in the future: 1) Dicir que o nome da columna é reservada ou non é. 2) Se non está reservado, amosar o sitio web, ou, polo menos, o grupo, en que o nome da columna xa se utiliza.

</final>

Esta semana, finalmente reproducido un problema que fora informar por un usuario remoto: Cando tentou exportar o contido dunha lista de Excel, as cousas parecen comezar a traballar, pero entón Excel debería aparecer un erro: "Cannot get the list schema column property from the SharePoint list". She was running office 2003, windows XP and connecting to MOSS.

Eu procurei as Internets e vin algunhas especulacións pero nada 100% definitive. Hence, este post.

O problema: Exportando unha vista a Excel que contén unha data (data = o tipo de datos da columna).

O que funcionou para nós: Convert the date to a "single line of text". Entón, convertelo-lo para unha data.

That solved it. It was nice to see that the conversion worked, na realidade. It was quite nervous that converting things this way would fail, but it did not.

Este erro foi lanzada unha sombra enorme sobre o tipo de datos data en mente do cliente, entón nós imos estar buscando unha resposta definitiva de Microsoft e espera que eu vou publicar e actualizar aquí o próximo período curto de tempo coa súa resposta oficial e Información do hotfix.

Outras referencias:

http://www.kevincornwell.com/blog/index.php/cannot-get-the-list-schema-column-property-from-the-sharepoint-list/

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2383611&SiteID=1

<final>

Rexístrate para o meu blog.

Durante os últimos dous días, I have participated in two meetings during which we presented the results of a SharePoint project. The CIO and his team joined the first meeting. That’s standard and not especially notable. The IT department is obviously involved in an enterprise rollout of any technology project. The second meeting expanded to include a V.P. de marketing, varios directores que representan HR, Loxística, Fabricación, Proxectos de Capital, Calidade, Adquisitivo, Desenvolvemento corporativo e outros departamentos (algúns dos cales nin sequera foron directamente implicados na fase actual). That’s a mighty wide audience.

Na miña vida anterior, I primarily worked on ERP and CRM projects. They both have a fairly wide solution domain but not as wide as SharePoint. To be fully realized, SharePoint projects legitimately and necessarily reach into every nook and cranny of an organization. How many other enterprise solutions have that kind of reach? Not many.

SharePoint clearly represents an enormous opportunity for those of us fortunate enough to be in this space. It provides a great technical opportunity (que é dalgún xeito ligado a súa cabeza aquí under "Technologies You Must Master"). But even better, SharePoint exposes us to an extensive and wide range of business processes through these engagements. How many CRM specialists work with the manufacturing side of the company? How many ERP consultants work with human resources on talent acquisition? SharePoint exceeds them both.

Como calquera cousa, non é perfecto, pero é un lugar maldito bo para ser.

No SharePoint foros, someone occasionally asks about "changing the label of Title" or about "removing title from lists".

Bottom line: Non faga iso!

Desafortunadamente, a interfaz de usuario permite un cambio de sentido único de que etiqueta da columna, como se mostra:

Title is a column associated with the "Item" tipo de contido. Moitos, moitos, moitos CT empregar esta columna e se cambiar isto aquí, it ripples out everywhere. There’s a good chance that you didn’t intend for that to happen. You were probably thinking to yourself, "I have a custom lookup list and ‘Title’ simplemente non ten sentido como un nome de columna, so I’m going to change it to ‘Status Code’ and add a description column." But if you follow through on that thought and rename ‘Title’ to ‘Status Code’, todos os títulos da lista (incluíndo bibliotecas de documentos) changes to "Status Code" e probablemente non tiña a intención para que isto ocorre.

O problema real é que se trata dun cambio de sentido único. The UI "knows" that "title" is a reserved word. Así, if you try and change "Status Code" back to "Title", vai evitar que e agora se retratado nun canto usando tinta que nunca seca 🙂

Entón o que pasa se xa cambiou? I haven’t seen the answer we all want, which is a simple and easy method to change the label back to ‘Title’. Right now, the best advice is to change it to something like "Doc/Item Title". That’s a generic enough label that may not be too jarring for your users.

Eu teño algunhas outras ideas que están na miña lista de cousas a facer cousas para a investigación:

• Contacta Microsoft.
• Fai algo co modelo de obxecto, quizais xunto cunha característica.
• Descubrir o esquema da base de datos e actualizar manualmente SQL. (Ten que contactar coa Microsoft antes de facelo; el probabelmente vai anular o seu contrato de soporte).

Se alguén sabe como solucionar isto, por favor publicar un comentario.

Actualiza final da tarde, 11/15: Descubrín esta conexión que describe un método para crear un tipo de lista que non ten unha columna de título: http://www.venkat.org/index.php/2007/09/03/how-to-remove-title-column-from-a-custom-list/

Preto de unha semana, I started up a codeplex project that provides a simple and reasonably generic method for adding custom action functions to SharePoit Designer workflow. It’s described here: http://www.codeplex.com/spdwfextensions. Beyond simply providing a framework, it also aims to provide a set of useful functions that will make SPD more useful/flexible/powerful.

Aquí están os recursos planeados para a versión actual 1.0: https://www.codeplex.com/Release/ProjectReleases.aspx?ProjectName=spdwfextensions&ReleaseId=8280

Se alguén ten algún interese neste proxecto, por favor, deixe un comentario ou iniciar / engadir a un debate aquí: http://www.codeplex.com/spdwfextensions/Thread/List.aspx

Aquí están o actual conxunto de funcións que foron codificados (aínda que non sexa totalmente probado desde 11/08/07):

Función	Descrición (se non mesmo. función Net)
Nun-entradas()	Volta o número "entradas" in a string as per a specified delimiter. Por exemplo: Num-entries in a string "a,b,c" with delimiter "," = 3.
Entrada()	Returns the nth token in a string as per a specified delimiter.
Lonxitude	String.length
Substituír()	String.Replace()
Contén()	String.Contains() Returns the word "true" or the word "false".
Substring(comezar)	String.substring(comezar)
Substring(comezar,final)	String.substring(comezar,final)
ToUpper()	String.toupper()
ToLower()	String.ToLower()
StartsWith()	String.StartsWith() Returns the word "true" or the word "false".
EndsWith()	String.EndsWith() Returns the word "true" or the word "false".