Arkivji ta 'Kull Xahar: Ottubru 2009

Fil-tifħir ta 'jQuery Msaħħa Fittex-As-You-Tip (minn Jan Tielens)

Ħalli Risposta

Jien jaħdmu fuq demo BPOs (dalwaqt tkun disponibbli fuq is-sit ta 'Microsoft) and I wanted to add a little pizzazz. I’ve known about Jan Tielen tal isforzi għal pjuttost filwaqt li u I had teknika kbira li żżid mal-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 (u forsi huwa x'imkien).

I żid biss żewġ punti li dak li diġà ħoloq / kiteb dwar:

  1. Dan ma, fil-fatt, jaħdmu fi BPOs (SharePoint online) ambjent.
  2. Biex jagħmluha taħdem mingħajr messaġġ popup annoying prefiss ir-referenza għall-librerija jquery ma https minflok http, kif fil-:
<tip b'kitba ="text/javascript" src ="https://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js"></iskrittura>

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 🙂

</aħħar>

Dan huwa post ieħor tiegħi serje għaddejjin dwar kif tuża jQuery ma SharePoint.
Jekk inti tixtieq titgħallem aktar dwar jQuery, I jirrakkomanda ħafna: jQuery fl-Azzjoni billi Bear Bibeault u Yehuda Katz.

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Tags:

SharePoint Shop Talk il-Ħamis 10/29 fil 12:30 PM EDT

Ħalli Risposta

Il SharePoint Talk Shop jmiss jieħu post dan nhar ta 'Ħamis 12:30PM EDT.

Imxejna meħuda ġimgħatejn off (minħabba SharePoint Konferenza aħħar ġimgħa) u bħala riżultat, għandna numru ta 'mistoqsijiet fil kju, not to mention all kinds of cool stuff to talk about regarding SharePoint 2010. All of the panel members attended SPC, sabiex iġibu SP tiegħek 2010 mistoqsijiet lill-sejħa jew email lill- questions@sharepointshoptalk.com.

Apparti minn parti tajba tas-sejħa imwarrba biex jitkellmu dwar xi wħud SP 2010 goodness, aħna ser jiddiskutu wkoll:

  • Għaliex SharePoint turi għażliet ta 'navigazzjoni taħt settings tas-sit (Din tvarja bbażati fuq karatteristiċi u l-konfigurazzjoni sit)
  • Timmodifika versions.aspx - problemi, diffikultajiet jagħmlu dan (I”m not surprised 🙂 ).
  • Embedding RSS feeds fis-sit meta s-sors ikun awtentikat.
  • Bl-użu stsadm biex jamministraw qtugħ.

Reġistru hawn: https://www.livemeeting.com/lrs/8000043750/Registration.aspx?pageName=p663256djrrflfdw

Bħas-soltu, jibagħtu xi mistoqsijiet jew suġġetti għal diskussjoni questions@sharepointshoptalk.com, email lili direttament jew twitter biex @ pagalvin.

Nittamaw li tara int hemm!

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Quick Hit: Qari InfoPath XML direttament minn SPListItem fl SharePoint

1 Irrispondi

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 (li huma biss fajls XML, dan huwa attwalment pjuttost faċli).

Filwaqt I kien bini l-proġett, I started by downloading an InfoPath form and saving it to my local hard drive. My c# code was reading directly from that instance. Madankollu, 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. Madankollu, there’s no need to go through those hoops as you can read it directly from the library. This little snippet shows how:

/// Jittieħed klassi definizzjoni hawn, inklużi:
privat SPFile mySharePointFile; /* Parti minn SPList */
// Aktar kodiċi tmur hawn u ġewwa metodu tal-klassi għandna:
XmlTextReader textReader;
textReader = ġdid XmlTextReader(mySharePointFile.OpenBinaryStream());

textReader.WhitespaceHandling = WhitespaceHandling.Xejn;

textReader.Read();

// Jekk il-node għandha valur

filwaqt li (textReader.Read())
{

… and so on and so forth …

Huma bit ewlieni hawn fuq hija li nistgħu taqra l-InfoPath direttament permezz tal-OpenBinaryStream() method call on the SPFile as a parameter to the constructor on XmlTextReader. It works great.

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Tags:

Quick u Easy: Send Email Bl-użu Gmail SMTP Server in. NET C #

2 tweġibiet

Dan mhux eżattament suġġett ġdid, iżda meta I meħtieġa biex jagħmlu dan, I found a lot of “why won’t this work for me” and not too many direct answers. I hope someone finds this useful.

Il-daqsxejn ta 'kodiċi li ġej se tibgħat email bl-użu kont gmail tiegħi stess biex jagħmlu dan, inkluż attachments:

użu System.Net.Mail;
użu System.Net;

NetworkCredential loginInfo = ġdid NetworkCredential("[ID Gmail tiegħi]", "[Password Gmail tiegħi]");
MailMessage MSG = ġdid MailMessage();
msg.From = ġdid MailAddress("[M Gmail Id]@ Gmail.com");
msg.To.Add(ġdid MailAddress("paul.galvin@arcovis.com"));
msg.Subject = "Test infopath dev subject";
msg.Body = "<html><korp><qawwija>A messaġġ qawwi.</qawwija></korp></html>";
msg.IsBodyHtml = vera;

foreach (string aFile fil NIPFD.GetAttachmentNamesAndLocations())
{
    msg.Attachments.Add(ġdid Attachment(aFile));
} // Żieda attachments.

SmtpClient klijent = ġdid SmtpClient("smtp.gmail.com");
client.EnableSsl = vera;
client.UseDefaultCredentials = falza;
client.Credentials = loginInfo;
client.Port = 587;
client.EnableSsl = vera;
client.Send(MSG);

A bits ewlenin ftit li naqas me isfel u osservazzjonijiet oħra / noti:

  • L-ewwel linja li toħloq l-oġġett loginInfo jeħtieġ li tuża l-ID gmail imqaxxar mill- "@ Gmail.com". Allura, jekk l-indirizz email tiegħi huwa gmail "Sharepoint@gmail.com"U password tiegħi huwa" xyzzy "imbagħad il-linja look like:

NetworkCredential loginInfo = ġdid NetworkCredential("sharepoint", "xyzzy");

  • Kont gmail tiegħi huwa stabbilit għall-użu SSL u li ma kienet problema.
  • There is some conflicting information out there on what port to use. I used port 587 u maħduma multa għalija.
  • Fil-każ tiegħi, I also needed to send attachments. That NIPFD object has a method that knows where my attachments are. It’s returning a fully path (e.g. "C:\temp\attachment1.jpg”. In my test, I kellu żewġ żjidiet u tnejn li huma maħduma multa.

I użati studio viżwali 2008 li tikteb dan il-kodiċi.

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

SharePoint Konferenza 2009 - Get Real Time Your Data Prima Mill Twitter

Ħalli Risposta

Nistenna li kważi kulħadd jaf dan xorta waħda, 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, hemm ħafna ta 'silliness u "in" ċajt, but if you can get past that, check out. 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 it’s not just a one-way flow of information.

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 out the twitter feed here: http://twitter.com/#search?q=%23spc09

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Programmatically Estrazzjoni Attachments minn forom InfoPath (InkluŜ l-ismijiet!)

Ħalli Risposta

I have an expense entry solution for a client that leverages InfoPath and workflow. At one point during the approval process, I bżonn li jiġġeneraw email li tkun kollha ta 'dik data InfoPath tajba kif ukoll l-annessi nnifishom sabiex (daqqa) xi ħadd jista 'jieħu dik id-data u manwalment mill-ġdid muftieħ f'applikazzjoni database Oracle.

It’s not very difficult to get at or parse the InfoPath form. I didn’t know how to handle the attachments, madankollu. After an hour or two of poking around the Internets (eternity!) Sibt dan l-artikolu: http://support.microsoft.com/kb/892730

It provide some handy code to extract the attachment from a node in the form. (Inti xorta jkollok bżonn biex isibu l-node u dak kollu li, iżda li biss parsing XML).

I know that the attachment is base64-encoded and I originally went down the path of just extracting the the base64 data, decoding it and saving it. Madankollu, I quickly realized I didn’t know how to get the file name itself until I found the aforementioned article.

I had actually found that quite early, but I was put off by its split personality. On the one hand, the article *says* it’s good for InfoPath 2007. Madankollu, the code and instructions are all about Visual Studio 2003 and references to InfoPath 2003.

Bottom line, the code that article provided is working well for me (s'issa). I can get my InfoPath form, I can parse it, I can find and decode the attachment and I know its name. What more can one ask of one’s life?

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Jekk int inkwetat li l-ambjent SharePoint tiegħek jista 'jkun tad ħżiena għas-saħħa, let me jgħinuk jiffissaw dak ma 'kontroll tas-saħħa.

SharePoint Shop terġa Talk għal 10-08-2009

6 tweġibiet

SharePoint Talk Shop lum koperti firxa wiesgħa tas-soltu tagħha ta 'suġġetti:

  • 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, imma meta tibda titkellem dwar out loud, 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, liċenzjar (liċenzja tiegħek SharePoint intranet jista 'ma jkunx, u probabbilment mhux se jkun, biżżejjed), SharePoint konfigurazzjoni (AAM, li testendi l-applikazzjonijiet web għal żoni li probabilment jkollhom HTTPS ppermettiet), eċċ. 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 (s'issa).
  • 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, a Shop Talk SharePoint regolari, jirrimarka dan blog dħul: 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.
  • Iddiskutejna custom forom jeditjaw (li inti toħloq 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

Din il-ġimgħa, aħna introduċiet karatteristika ġdida fejn aħna jintefqu madwar 10 minutes demonstrating an interesting tip/trick in a SharePoint environment. Din il-ġimgħa, aħna wera kif miżjud parti kontenut tal-web editur (u fil-fatt xi parti web) to a newitem.aspx page. F'dan il-każ, 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. Ġimgħa d-dieħla, we do plan to show a jQuery tip/trick. Nittamaw li tara int hemm.

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

SharePoint Shop Talk 10/08/08 fil 12:30 PM EDT

Ħalli Risposta

Aħna qed hosting ġimgħa li jmiss SharePoint sessjoni tagħna Talk Shop għada fil 12:30 PM EDT.

Din hija Q miftuħ&A and general kibitzing session on all topics SharePoint related.

Inti tista 'taqra recaps varji ta' sessjonijiet qabel hawn biex jiksbu sens ta 'dak li nagħmlu fuq dawn is-sejħiet hawn: http://paulgalvin.spaces.live.com/?_c11_BlogPart_BlogPart=blogview&_c=BlogPart&partqs=cat%3dPublic%2520Speaking

Ir-reġistrazzjoni hija up u lesta dritt hawn: https://www.livemeeting.com/lrs/8000043750/Registration.aspx?pageName=0z40kg9nb0t0842f

Twitter mistoqsijiet tiegħek lili, "Imħaded.

Email lill- questions@sharepointshoptalk.com or just show up on the line and ask them out loud.

Nittamaw li tara int imbagħad!

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Għall-Blog jew Mhux għall-Blog - Dan huwa l-Mistoqsija (għall-Blog About)

1 Irrispondi

Innota: This was originally posted to www.endusersharepoint.com.

A few weeks ago I had the chance to speak at SharePoint Saturday in New York. Għal darb'oħra, a tremendous event. Din id-darba, I spoke about “learning SharePoint” – a very broad topic. During the presentation (which you can get here), I talked about a variety of techniques for “learning” SharePoint, including stuff like book learning, class room training, creating your own VM and most importantly (lili), 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, I’m scratching that itch by blogging about it.

Some people seem to think that there are so many quality bloggers out there on the scene today and that so many quality blog entries have been written that in a sense, there’s nothing new to write about. Jew, 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.

For starters, if you’re blogging because it’s part of your personal attempt at learning SharePoint well, it’s really irrelevant if someone has written on your topic or not. One of the drivers behind community participation, whether it’s for personal learning or not, is that you need to get it right. 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, you’re going to think the subject through more carefully, eċċ. Thus, you’re thinking, studying and considering this topic from all kinds of angles, left to right, up to down, inside and out (or at least you should be). That’s a very valuable exercise. Fil-fatt, 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. Of course, you do want to push the post button anyway for a variety of reasons, but I digress. The bottom line is that blogging is a valuable learning exercise in and of itself, period.

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, different writing styles, different approaches to the same problem – they all help me understand what I need. In my opinion, the community is no where close to reaching a saturation point on good quality blog articles on any topic in the SharePoint world.

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

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

M'għandekx Be Bull fil-Shop Ċina

Ħalli Risposta

A Storja qasira tal SharePoint (Mill-perspettiva ta Newcomer relattiva tal)

Innota: This article was originally posted to www.endusersharepoint.com. I forgot to post it to my own blog 🙂

SharePoint evolviet ħafna sa mill-bidu tagħha bħala tip ta 'teknoloġija inkubazzjoni Microsoft –huwa evolviet kważi bħal movie orrur, where the mad scientist’s creation takes on a life of its own, breaking free of its creator’s expectations and rules. The technical evolution is obvious – the WSS 3.0 object model is richer and more complex than 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, madankollu, SharePoint’s evolution is even more significant.

In the early days, 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, it followed a relatively traditional pattern of End User <-> IT relationship. A lot of End Users, communicating and working with a very small number of It people to deliver solutions that solve business problems:

image

The overall problem domain for which SharePoint is a suitable delivery platform is small (especially compared to today’s SharePoint. End Users and IT worked in a more classic arrangement with IT: define requirements to IT, wait for IT do their work behind the curtain and take delivery of the final product.

As SharePoint evolved to the 2.0 world (WSS 2.0 and SharePoint Portal Server), several things happened. Ewwel, the “problem domain” increased in size. By problem domain, I mean the kinds of business problems for which SharePoint could be a viable solution. Per eżempju, you wouldn’t think too hard about implementing a serious search solution in a SharePoint environment until SPS (and even then, it wasn’t as good as it needed to be). Fl-istess ħin, End Users have an unprecedented ability to not only define, but also implement their own solutions with little or no IT support.

The 3.0 platform (WSS and MOSS) maintained and increased that momentum. The problem domain is enormous as compared to the 2.0 platform. Virtually every department in a company, ranging from manufacturing health and safety departments to marketing, from sales to quality control – they can find a good use for SharePoint (and it’s not a case of mashing a round peg into a square hole). Fl-istess ħin, 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. The 3.0 platform turns previously stable roles on their heads. Suddenly, End Users are effectively judge, jury and executioner analista negozju, 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, let’s consider the elephant in the room.

Peering into the Crystal Ball

How will SharePoint 2010 affect this pattern? Will it be incremental or revolutionary? Will more, fewer or about the same number of End users find themselves empowered to build solutions 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?

There’s enough information “out there” to safely say that the general answer is:

  • The problem domain is going to dramatically expand.
  • End Users will find themselves even more empowered than before.

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.

No Bulls in My China Shop!

This sounds great, but from my point of view as a SharePoint consultant and putting myself into the shoes of an IT manager, I see this vision. I own a China shop with beautiful plates, crystal, eċċ (my SharePoint environment). 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, but in anticipation, 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 tnejn bulls and even a wolf. Then I notice that there are some sheep. Sheep are hekk bad, but are they maybe disguised wolves? I don’t want bulls in my china shop!

It gets worse! When I rented the space, I couldn’t believe how nice it was. Wide and open, terrific amenities, very reasonable price. Madankollu, now I’m realizing that the wide open spaces and the huge door is just perfectly sized for a bull to come wandering in and lay waste to my china.

I’m pushing this analogy too far, tal-kors. End Users are not bulls (most of them, xorta waħda) and IT departments don’t (or surely should not) view their user community with that kind of suspicion. Madankollu, there is this sort of perfect collision taking place already in the the 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.

That’s great and all, but the fact is that it’s still a very technical product and still calls for the kind of vigorous business requirements analysis, 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 is going to change the game a bit and it’s going to play out differently and in slow motion as companies roll out their SP 2010 solutions over 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, per eżempju. They need to understand fundamental concepts like CRUD (create, update and delete), dev/test/qa/prod environments and how to use that infrastructure to properly deploy solutions that live a nice long time and bend (not break) in response to changes in an organization.

In the coming weeks, I plan to try and provide some of my own new ideas, as well as link to the great work done by many other authors (fuq www.endusersharepoint.com u bnadi oħra) so that interested End Users can learn that old time IT religion. Keep tuned.

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin