maandelikse Argiewe: Oktober 2009

In die lof van jQuery Verbeterde Soek-as-jy-tipe (deur Jan Tielens)

Laat 'n antwoord

Ek werk op 'n BPOS demo (binnekort beskikbaar wees op Microsoft se webwerf) and I wanted to add a little pizzazz. I’ve known about Jan Tielen pogings om vir 'n geruime tyd en ek het gedink dit sou 'n groot tegniek toe te voeg tot die demo, so I did. You can read about it here: http://weblogs.asp.net/jan/archive/2009/07/02/sharepoint-search-as-you-type-with-jquery.aspx. It’s so simple to use it should probably be a crime (en is miskien iewers).

Ek voeg net twee punte wat hy reeds geskep / geskryf oor:

  1. Dit beteken, in werklikheid, werk in 1 BPOS (SharePoint aanlyn) omgewing.
  2. Te maak dit werk sonder 'n popup boodskap prefix die verwysing na die jQuery biblioteek met https in plaas van http, soos in:
<script type ="Teks / javascript" src ="Https://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js"></script>

Jan points out that you should probably move the library itself to your site. Feeling a little lazy today, I decided to blog about it instead 🙂

</einde>

Dit is nog 'n post in my aan die gang reeks oor hoe om te gebruik jQuery met SharePoint.
As jy wil meer oor jQuery te leer, Ek raai: jQuery in Aksie deur die Bear Bibeault en Yehuda Katz.

Skryf in op my blog.

Volg my op Twitter http://www.twitter.com/pagalvin

Technorati Tags:

Die SharePoint Shop Besprekings Donderdag 10/29 op 12:30 PM EDT

Laat 'n antwoord

Die volgende SharePoint shop talk vind plaas Donderdag om 12:30PM EDT.

Ons het twee weke af geneem (as gevolg van die SharePoint konferensie verlede week) en as 'n gevolg, Ons het 'n aantal van vrae in die tou, not to mention all kinds of cool stuff to talk about regarding SharePoint 2010. All of the panel members attended SPC, so bring your SP 2010 questions to the call or email them to questions@sharepointshoptalk.com.

Aside from a good part of the call set aside to talk about some SP 2010 goodness, we’ll also discuss:

  • Why SharePoint shows different navigation options under site settings (this varies based on features and site configuration)
  • Modifying versions.aspx – problems, difficulties doing so (I”m not surprised 🙂 ).
  • Embedding RSS feeds into a site when the source is authenticated.
  • Using stsadm to manage logging.

Teken hier aan: https://www.livemeeting.com/lrs/8000043750/Registration.aspx?pageName=p663256djrrflfdw

As usual, stuur enige vrae of onderwerpe te questions@sharepointshoptalk.com, e-pos my direk of Twitter @ pagalvin.

Ons hoop om jou daar te sien!

</einde>

Skryf in op my blog.

Volg my op Twitter http://www.twitter.com/pagalvin

Technorati Tags:

Vinnige Hit: Lees Path XML direk vanaf 'n SPListItem in SharePoint

1 Antwoord

I’m been working on a project where I need to extract attachments from an InfoPath form. There are some good resources for parsing InfoPath forms (wat net XML-lêers, So dit is eintlik baie maklik).

Terwyl ek die opbou van die projek, I started by downloading an InfoPath form and saving it to my local hard drive. My c# code was reading directly from that instance. Egter, the InfoPath forms are really living inside a SharePoint forms library. I did a little half hearted searching to find out how to read it directly from the library and almost gave up, in which case I would have saved the form to a local temp directory and read it from there. Egter, there’s no need to go through those hoops as you can read it directly from the library. This little snippet shows how:

/// Klas definisie dinge hier, insluitende:
private SPFile mySharePointFile; /* Deel van 'n SPList */
// Meer kode gaan hier en binne 'n metode van die klas het ons 'n:
XmlTextReader textReader;
textReader = nuwe XmlTextReader(mySharePointFile.OpenBinaryStream());

textReader.WhitespaceHandling = WhitespaceHandling.Geen;

textReader.Read();

// Indien die knoop het waarde

terwyl (textReader.Read())
{

… and so on and so forth …

Hulle het die sleutel bietjie bogenoemde is dat ons kan die Path direk lees via die OpenBinaryStream() method call on the SPFile as a parameter to the constructor on XmlTextReader. It works great.

</einde>

Skryf in op my blog.

Volg my op Twitter http://www.twitter.com/pagalvin

Technorati Tags:

Vinnige en maklike: Stuur e-pos gebruik Gmail SMTP-bediener in. NET C #

2 antwoorde

Dit is nie juis 'n nuwe onderwerp, maar toe ek dit nodig gehad het om te doen, I found a lot of “why won’t this work for me” and not too many direct answers. I hope someone finds this useful.

Die volgende stukkie van die kode sal stuur 'n e-pos met my eie Gmail-rekening om dit te doen, insluitend aanhegsels:

die gebruik van System.Net.Mail;
die gebruik van System.Net;

NetworkCredential loginInfo = nuwe NetworkCredential("[My Gmail ID]", "[My Gmail Vergeet]");
Mailbericht msg = nuwe Mailbericht();
msg.From = nuwe Pos adres("[M Gmail-id]@ Gmail.com");
msg.To.Add(nuwe Pos adres("paul.galvin@arcovis.com"));
msg.Subject = "Test infopath dev subject";
msg.Body = "<html><liggaam><sterk>'N sterk boodskap.</sterk></liggaam></html>";
msg.IsBodyHtml = waar;

foreach (string AFile in NIPFD.GetAttachmentNamesAndLocations())
{
    msg.Attachments.Add(nuwe Beslaglegging(AFile));
} // Voeg aanhegsels.

SmtpClient kliënt = nuwe SmtpClient("smtp.gmail.com");
client.EnableSsl = waar;
client.UseDefaultCredentials = valse;
client.Credentials = loginInfo;
client.Port = 587;
client.EnableSsl = waar;
client.Send(msg);

A few key bits that slowed me down and other observations / notes:

  • The first line that creates the loginInfo object needs to use the gmail ID stripped of “@gmail.com". So, if my gmail email address is “sharepoint@gmail.com” and my password is “xyzzy” then the line would look like:

NetworkCredential loginInfo = nuwe NetworkCredential("sharepoint", "Xyzzy");

  • My gmail account is set up to use SSL and that wasn’t a problem.
  • There is some conflicting information out there on what port to use. I used port 587 and it worked fine for me.
  • In my geval, I also needed to send attachments. That NIPFD object has a method that knows where my attachments are. It’s returning a fully path (bijv. “c:\temp\attachment1.jpg”. In my test, Ek het twee aanhegsels en hulle albei werk goed.

Ek gebruik van Visual Studio 2008 hierdie kode te skryf.

</einde>

Skryf in op my blog.

Volg my op Twitter http://www.twitter.com/pagalvin

Technorati Tags: ,,,

SharePoint Konferensie 2009 - Kry jou regte tyd rou data Van Twitter

Laat 'n antwoord

Ek verwag dat byna almal weet dit in elk geval, but I thought I’d toss out a quick note that there’s a tremendous amount of very interesting information available via twitter. The hash tag #SPC09 seems to be the most popular. Like always, daar is 'n baie van silliness en "in" grappies, Maar as jy kan kry verlede wat, check dit uit. I do my best to respond to comments or questions directed to me and I know that a lot of others do as well, so dit is nie net 'n een-rigting vloei van inligting.

New sessions start in just under two hours and continue up until about 3pm EDT this Thursday. It will start to pick up then.

Check uit die Twitter voer hier: http://twitter.com/#search?q=%23spc09

</einde>

Skryf in op my blog.

Volg my op Twitter http://www.twitter.com/pagalvin

Programmaties Uittreksels aanhegsels van Path Vorms (Insluitend hul name!)

Laat 'n antwoord

I have an expense entry solution for a client that leverages InfoPath and workflow. At one point during the approval process, Ek het 'n e-pos wat al van daardie goeie Path data sowel as die aanhegsels hulself te genereer sodat (sug) iemand kan neem dat die data en die hand te re-sleutel dit in 'n Oracle databasis aansoek.

It’s not very difficult to get at or parse the InfoPath form. I didn’t know how to handle the attachments, egter. After an hour or two of poking around the Internets ('n ewigheid!) Ek het gevind dat hierdie artikel: http://support.microsoft.com/kb/892730

It provide some handy code to extract the attachment from a node in the form. (Jy moet nog steeds die knoop en al wat te vind, maar dit is net XML-ontleding).

Ek weet dat die beslaglegging is base64 geënkodeerde-en ek oorspronklik het die pad van net onttrek die die base64 data, decoding it and saving it. Egter, Ek het gou besef ek het nie geweet hoe om die lêer naam kry homself totdat ek het gevind dat die genoemde artikel.

Ek het eintlik het bevind dat baie vroeë, maar ek was sit af deur sy gesplete persoonlikheid. Aan die een kant, the article *says* it’s good for InfoPath 2007. Tog, die kode en instruksies is al oor die Visual Studio 2003 en verwysings na Path 2003.

Bottom line, die kode wat artikel wat verskaf is goed werk vir my (so ver). I can get my InfoPath form, Ek kan ontleed dit, I can find and decode the attachment and I know its name. What more can one ask of one’s life?

</einde>

Skryf in op my blog.

Volg my op Twitter http://www.twitter.com/pagalvin

Technorati Tags: ,,

As jy bekommerd is dat jou SharePoint omgewing kan 'n bietjie ongesond wees, Laat my toe om jou te los wat met 'n gesondheid tjek.

SharePoint Shop Talk herhaling vir 10-08-2009

6 antwoorde

Vandag se SharePoint shop talk sy gewone wye verskeidenheid van onderwerpe gedek:

  • We discussed the issues around opening up parts of a SharePoint site collection to your trading partners. It’s not the most complicated thing in the world, maar wanneer jy begin praat oor hardop, you realize there are a lot of small individual things that need to be done to do this correctly. You have to consider the firewall, lisensiëring (jou intranet SharePoint lisensie mag nie, en sal waarskynlik nie, voldoende), SharePoint opset (AAM, uitbreiding van web programme te sones wat waarskynlik HTTPS in staat gestel om), ens.. If anyone has a checklist of what to do and the sequence, I’d love to see it in comments. This question wins the “Most Discussed Question” aware of the year (so ver).
  • I got to ask a question about the image library functionality that generates those thumb nail images. I speculated that an event receiver on the image library is generating the thumb nail. I’m probably way off base, but it does seem like there’s an entirely separate image on the web server for the thumb nail itself. Vamshi, 'n SharePoint Shop Talk gereelde, punte uit hierdie blog entry: http://pathtosharepoint.wordpress.com/2009/08/23/picture-libraries-take-advantage-of-web-friendly-formats/. That’s a pretty interesting post about images in SharePoint if you’re interested in it.
  • Ons het gepraat oor persoonlike wysig vorms (wat jy skep via SPD) and the fact that you lose the attachment functionality when you do that. Laura Rogers has blogged on that subject here: http://sharepoint911.com/blogs/laura/archive/2009/09/10/fix-for-the-custom-form-attachments-issue.aspx

Hierdie week, Ons het 'n nuwe funksie waar ons het ongeveer 10 minutes demonstrating an interesting tip/trick in a SharePoint environment. Hierdie week, het ons gewys hoe om 'n inhoud redakteur web deel te bygevoeg (en eintlik enige web deel) to a newitem.aspx page. In hierdie geval, the objective was to show some extensive online help for that newitem.aspx page. This is also one of the usual starting points for integrating jQuery into your environment. Volgende week, we do plan to show a jQuery tip/trick. Ons hoop om jou daar te sien.

</einde>

Skryf in op my blog.

Volg my op Twitter http://www.twitter.com/pagalvin

Technorati Tags:

SharePoint shop talk 10/08/08 op 12:30 PM EDT

Laat 'n antwoord

Ons bied ons volgende week SharePoint Shop Talk sessie môre by 12:30 PM EDT.

Dit is 'n oop Q&A and general kibitzing session on all topics SharePoint related.

Jy kan lees verskeie herhalingen van vorige sessies hier 'n gevoel van wat ons doen op hierdie oproepe om hier te kom: http://paulgalvin.spaces.live.com/?_c11_BlogPart_BlogPart=blogview&_c=BlogPart&partqs=cat%3dPublic%2520Speaking

Registrasie is en gereed om reg hier: https://www.livemeeting.com/lrs/8000043750/Registration.aspx?pageName=0z40kg9nb0t0842f

Twitter jou vrae aan my, @ Pillow.

E-pos om hulle te questions@sharepointshoptalk.com or just show up on the line and ask them out loud.

Ons hoop om jou te sien dan!

</einde>

Skryf in op my blog.

Volg my op Twitter http://www.twitter.com/pagalvin

Technorati Tags:

Om te blog of nie te blog - dit is die vraag (om te blog oor)

1 Antwoord

Let daarop: Dit is oorspronklik gepos word aan www.endusersharepoint.com.

A few weeks ago I had the chance to speak at SharePoint Saturday in New York. Weer, a tremendous event. Hierdie keer, I spoke about “learning SharePoint” – a very broad topic. During the presentation (wat jy hier kan kry), Ek het gepraat oor 'n verskeidenheid van tegnieke vir die "leer" SharePoint, insluitend dinge soos boek leer, klaskamer opleiding, skep jou eie VM en die belangrikste (vir my), community participation. One way to participate in the SharePoint community is via blogging. Someone asked me about blogging in particular and asked my opinion on a few concerns he had that I’ve heard others mention before. It’s been itching at the back of my head for a few weeks so in my usual fashion, Ek krap wat jeuk deur blog oor dit.

Sommige mense dink dat daar so baie kwaliteit bloggers daar buite op die toneel vandag en dat so baie kwaliteit blog inskrywings is geskryf dat in 'n sekere sin, there’s nothing new to write about. Of, the “new” thing is so narrowly focused that it’s not going to be interesting to anyone. I don’t agree with those sentiments or the underlying assumption about them.

Om mee te begin, as jy blog, want dit is deel van jou persoonlike poging om te leer SharePoint goed, it’s really irrelevant if someone has written on your topic or not. One of the drivers behind community participation, of dit nou vir persoonlike leer of nie, is dat jy nodig het om te kry dit reg. No one wants to put up some weak blog entry and look silly in front of the world. In the course of getting it right, jy gaan die onderwerp te dink deur middel van meer versigtig, ens.. Thus, jy dink, studeer en die oorweging van hierdie onderwerp uit alle soorte hoeke, links na regs, tot af, binne en buite (of ten minste het jy moet wees). That’s a very valuable exercise. In werklikheid, it’s almost beside the point of pushing the “post” button by the time you finish writing it since you’ve already derived much of the benefit by now. Natuurlik, jy wil die post knoppie in elk geval te stoot vir 'n verskeidenheid van redes, but I digress. The bottom line is that blogging is a valuable learning exercise in and of itself, tydperk.

I also reject the “it’s already been done” argument. So what if it was? The terrible consequence is that people who are looking up your topic via bing will now find two or five or a dozen articles. Who cares? I always prefer to find several articles on the same topic when I go searching the tubes for stuff. Different points of view, verskillende skryfstyle, different approaches to the same problem – they all help me understand what I need. In my opinion, die gemeenskap is nie waar naby aan die bereiking van 'n versadigingspunt op goeie gehalte blog artikels oor enige onderwerp in die SharePoint wêreld.

So, blog weg! You won’t hear me complaining about it. I guarantee it 🙂

</einde>

Skryf in op my blog.

Volg my op Twitter http://www.twitter.com/pagalvin

Technorati Tags: ,

Moenie 'n Bull in die China Shop

Laat 'n antwoord

'N Kort geskiedenis van SharePoint (Uit 'n relatiewe nuweling se perspektief)

Let daarop: Hierdie artikel is oorspronklik gepos word aan www.endusersharepoint.com. I forgot to post it to my own blog 🙂

SharePoint ontwikkel het 'n groot deel sedert sy vroeë dae as 'n soort van 'n inkubasie tegnologie by Microsoft –dit ontwikkel het amper soos 'n horror movie, waar die mal wetenskaplike se skepping neem op 'n lewe van sy eie, breaking free of its creator’s expectations and rules. The technical evolution is obvious – the WSS 3.0 voorwerp model is ryker en meer kompleks as WSS 2.0, which was itself an improvement over earlier versions. The next version will no doubt show tremendous improvement over 3.0. From an End User’s perspective, egter, SharePoint se evolusie is selfs nog meer betekenisvol.

In die vroeë dae, SharePoint didn’t offer much to End Users. They would have their usual functionality requirements, work with IT to define them well and implement a solution. IT would use SharePoint to solve the problem. The product wasn’t very accessible to End Users. I’ve thought threw a few analogies, but I decided to stick Venn Diagrams to show what I mean. When Microsoft first released SharePoint to the world as a commercial offering, Dit volg op 'n betreklik tradisionele patroon van eindgebruiker <-> IT relationship. A lot of End Users, kommunikeer en werk met 'n baie klein aantal mense Dit oplossings vir probleme op te lewer:

image

Die algehele probleem domein waarvoor SharePoint is 'n geskikte aflewering platform is 'n klein (especially compared to today’s SharePoint. End Users and IT worked in a more classic arrangement with IT: definieer vereistes IT, wag vir dit doen nie hul werk agter die gordyn en neem lewering van die finale produk.

As SharePoint ontwikkel om die 2.0 wêreld (WSS 2.0 en SharePoint Portal Server), several things happened. Eerste, the “problem domain” increased in size. By problem domain, I mean the kinds of business problems for which SharePoint could be a viable solution. Byvoorbeeld, sou jy nie dink te hard oor die implementering van 'n ernstige soek oplossing in 'n SharePoint omgewing tot SPS (en selfs dan, dit was nie so goed soos dit nodig is om te wees). Op dieselfde tyd, Einde gebruikers het 'n ongekende vermoë om nie net te definieer, but also implement their own solutions with little or no IT support.

Die 3.0 platform (WSS en mos) maintained and increased that momentum. The problem domain is enormous as compared to the 2.0 platform. Virtually every department in a company, wat wissel van die vervaardiging van gesondheid en veiligheid departemente tot bemarking, uit verkope aan gehaltebeheer - hulle kan vind 'n goeie gebruik vir SharePoint (en dit is nie 'n geval van Mais Chen 'n ronde pen in 'n vierkantige gat). Op dieselfde tyd, the platform empowers even more End Users to implement their own business solutions. I try to capture that with this diagram:

image

This has proven to be both a potent and frustrating mixture. Die 3.0 platform turns previously stable roles on their heads. Suddenly, Einde gebruikers is effektief regter, jurie en laksman sake-ontleder, application architect and developer for their own business solutions. This gets to the heart of the problem I’m writing about. But before I dive into that, Kom ons kyk na die olifant in die kamer.

Loer na die Crystal Ball

Hoe sal SharePoint 2010 invloed op hierdie patroon? Will it be incremental or revolutionary? Will more, minder of ongeveer dieselfde aantal End gebruikers hulself bemagtig om oplossings te bou in SharePoint 2010? Will SharePoint 2010’s problem domain expand even further or will it just refine and streamline what it already offers in WSS 3.0 / MOSS?

Daar is genoeg inligting "daar buite" om veilig te sê dat die algemene antwoord is:

  • The problem domain is going to dramatically expand.
  • Einde gebruikers sal vind dat hulle selfs meer bemagtig as ooit tevore.

The Venn Diagram would be larger than this page and cause some IT Pros and CxO’s to reach for their Pepto.

I believe it’s going to be a tremendous opportunity for companies to do some truly transformational things.

Geen Bulls in China, My Shop!

Dit klink baie, maar uit my oogpunt as 'n SharePoint konsultant en om myself in die skoene van 'n IT-bestuurder, I see this vision. I own a China shop with beautiful plates, kristal, ens. (my SharePoint omgewing). I’ve rented a space, I’ve purchased my inventory and laid it all out the way I like it. I’m not quite ready to open, maar in afwagting, I look at the door to see if my customers are lining up and I notice an actual bull out there. I look more closely and I actually see twee bulls and even a wolf. Then I notice that there are some sheep. Sheep are so slegte, maar hulle is dalk verbloem wolwe? I don’t want bulls in my china shop!

Dit raak erger! When I rented the space, I couldn’t believe how nice it was. Wide and open, geweldige geriewe, very reasonable price. Egter, nou is ek besef dat die wye oop ruimtes en die groot deur is net perfek grootte vir 'n bul te kom dwaal in en afval te lê na my China.

Ek is besig om hierdie beeld te ver, natuurlik. End Users are not bulls (die meeste van hulle, in elk geval) en IT-afdelings nie (of sekerlik moet nie) view their user community with that kind of suspicion. Egter, daar is hierdie soort van volmaakte botsing plaasvind reeds in die die 3.0 platform that I expect will only get worse in SP 2010. SharePoint already empowers and encourages End Users to define and implement their own solutions.

Dit is groot en al, maar die feit is dat dit nog 'n baie tegniese produk en nog steeds oproepe vir die aard van die kragtige besigheid vereistes analise, design and general planning and management that technical projects require to be successful. These are not the kind of skills that a lot of End Users have in their bag of tricks, especially when the focus is on a technical product like SharePoint.

I’ve given this a lot of thought over the last year or so and I don’t see any easy answer. It really boils down to education and training. I think that SP 2010 gaan die spel verander 'n bietjie en dit gaan om te speel anders en in slow motion as maatskappye uitrol hul SP 2010 oplossings oor 2010 and beyond. In order to succeed, End Users will need to transform themselves and get a little IT religion. They’ll need to learn a little bit about proper requirements
analysis. They will need some design documentation that clearly identifies business process workflow, byvoorbeeld. They need to understand fundamental concepts like CRUD (skep, werk en te verwyder), dev / toets / QA / prod omgewings en hoe om daardie infrastruktuur te gebruik om behoorlik ontplooi oplossings wat leef 'n lekker lang tyd en draai (nie breek) in reaksie op veranderinge in 'n organisasie.

In die komende weke, Ek is van plan om te probeer en 'n paar van my eie nuwe idees, sowel as skakel na die groot werk wat gedoen word deur baie ander skrywers (op www.endusersharepoint.com en elders) so that interested End Users can learn that old time IT religion. Keep tuned.

</einde>

Skryf in op my blog.

Volg my op Twitter http://www.twitter.com/pagalvin

Technorati Tags: ,