Buwanang Archive: Oktubre 2009

Sa Papuri ng jQuery Pinahusay na Paghahanap-Bilang-ka-type (sa pamamagitan ng Jan Tielens)

Mag-iwan ng reply

Ako ay nagtatrabaho sa isang demo BPOS (sa lalong madaling panahon upang maging magagamit hanggang sa Microsoft site) and I wanted to add a little pizzazz. I’ve known about Jan Tielen ni pagsisikap para sa lubos isang habang at naisip ko na gusto itong maging isang mahusay na paraan upang idagdag sa ang 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 (at marahil ay sa isang lugar).

Idagdag ko lang ang dalawang punto sa kung ano siya ay nilikha na / sinulat ni tungkol sa:

  1. Ito ang ibig, sa katunayan, magtrabaho sa isang BPOS (SharePoint online) kapaligiran.
  2. Upang gumawa ito gumagana nang walang isang nakakainis na popup mensahe prefix ang reference sa jquery library na may https sa halip na http, tulad ng sa:
<script type ="text/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 🙂

</dulo>

Ito ay isa pang post sa aking on-pagpunta serye kung paano gamitin jQuery may SharePoint.
Kung gusto mong matuto nang higit pa tungkol sa jQuery, Ko lubos na inirerekomenda: jQuery sa Aksyon sa pamamagitan ng Bear Bibeault at Yehuda Katz.

Mag-subscribe sa aking blog.

Sundin ako sa Twitter sa http://www.twitter.com/pagalvin

Technorati Tags:

SharePoint Shop Talk Huwebes 10/29 sa 12:30 PM EDT

Mag-iwan ng reply

Ang susunod na ng SharePoint Shop Talk tumatagal ilagay ang Huwebes sa 12:30PM EDT.

Namin kinuha ng dalawang linggo off (dahil sa SharePoint Conference noong nakaraang linggo) at bilang isang resulta, kami ay may isang numero ng mga katanungan sa queue, not to mention all kinds of cool stuff to talk about regarding SharePoint 2010. All of the panel members attended SPC, kaya dalhin ang iyong SP 2010 mga tanong sa tawag o email ang mga ito sa questions@sharepointshoptalk.com.

Bukod sa isang magandang bahagi ng tawag na magtabi upang makipag-usap tungkol sa ilang SP 2010 kabutihan, gagamitin din namin talakayin:

  • Bakit SharePoint Ipinapakita ng iba't ibang mga pagpipilian sa pag-navigate sa ilalim ng mga setting ng site (ito ay nag-iiba batay sa mga tampok at configuration site)
  • Binabago ang versions.aspx - problema, kahirapan sa paggawa nito (I”m not surprised 🙂 ).
  • Pag-embed ng mga RSS feed sa isang site kapag ang pinagmulan ay napatotohanan.
  • Paggamit ng stsadm upang pamahalaan ang pag-log.

Magrehistro dito: https://www.livemeeting.com/lrs/8000043750/Registration.aspx?pageName=p663256djrrflfdw

Gaya ng dati, magpadala ng anumang mga katanungan o mga talakayan sa mga paksa questions@sharepointshoptalk.com, email sa akin nang direkta o sa nerbiyos @ pagalvin.

Umaasa kaming makita ka doon!

</dulo>

Mag-subscribe sa aking blog.

Sundin ako sa Twitter sa http://www.twitter.com/pagalvin

Technorati Tags:

Quick Hit: Binabasa ang InfoPath XML Direkta Mula sa isang SPListItem sa SharePoint

1 Sumagot

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 (na lamang ang XML file, kaya talagang medyo madali).

Habang ako ay pagbuo up ang proyekto, I started by downloading an InfoPath form and saving it to my local hard drive. My c# code was reading directly from that instance. Gayunman, 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. Gayunman, there’s no need to go through those hoops as you can read it directly from the library. This little snippet shows how:

/// Class kahulugan bagay-bagay dito, kasama:
pribado SPFile mySharePointFile; /* Bahagi ng isang SPList */
// Higit pang code dito napupunta at sa loob ng isang pamamaraan ng klase mayroon kami:
XmlTextReader textReader;
textReader = bago XmlTextReader(mySharePointFile.OpenBinaryStream());

textReader.WhitespaceHandling = WhitespaceHandling.Wala;

textReader.Read();

// Kung ang node ay may halaga

habang (textReader.Read())
{

… and so on and so forth …

Sila key bit sa itaas ay na maaari naming basahin ang InfoPath nang direkta sa pamamagitan ng OpenBinaryStream() method call on the SPFile as a parameter to the constructor on XmlTextReader. It works great.

</dulo>

Mag-subscribe sa aking blog.

Sundin ako sa Twitter sa http://www.twitter.com/pagalvin

Technorati Tags:

Mabilis at madali: Magpadala ng Email Paggamit ng Gmail SMTP Server sa. NET C #

2 tugon

Ito ay hindi eksakto ng isang bagong paksa, ngunit kapag ako ay kinakailangan na gawin ito, I found a lot of “why won’t this work for me” and not too many direct answers. I hope someone finds this useful.

Ang mga sumusunod na piraso ng code ay magpadala ng email gamit ang aking sariling gmail account upang gawin ito, kabilang ang mga attachment:

paggamit System.Net.Mail;
paggamit System.Net;

NetworkCredential loginInfo = bago NetworkCredential("[Aking Gmail ID]", "[Aking Gmail Password]");
MailMessage msg = bago MailMessage();
msg.From = bago MailAddress("[M Gmail Id]@ Gmail.com");
msg.To.Add(bago MailAddress("paul.galvin@arcovis.com"));
msg.Subject = "Test infopath dev subject";
msg.Body = "<html><katawan><malakas>Ang isang malakas na mensahe.</malakas></katawan></html>";
msg.IsBodyHtml = totoo;

foreach (pisi aFile sa NIPFD.GetAttachmentNamesAndLocations())
{
    msg.Attachments.Add(bago Pagkakabit(aFile));
} // Pagdaragdag ng mga attachment.

SmtpClient client = bago SmtpClient("smtp.gmail.com");
client.EnableSsl = totoo;
client.UseDefaultCredentials = hindi totoo;
client.Credentials = loginInfo;
client.Port = 587;
client.EnableSsl = totoo;
client.Send(msg);

Ang ilang mga susi piraso na pinabagal akin down at iba pang mga obserbasyon / mga tala:

  • Ang unang linya na lumilikha ang loginInfo bagay na kailangang gamitin ang gmail ID Nakuha ang "@ Gmail.com". Kaya, kung ang aking gmail email address ay "Sharepoint@gmail.com"At ang aking password ay" xyzzy "pagkatapos linya ang magiging itsura:

NetworkCredential loginInfo = bago NetworkCredential("sharepoint", "xyzzy");

  • Ang aking gmail account ay naka-set up upang gamitin ang SSL at na ay hindi isang problema.
  • There is some conflicting information out there on what port to use. I used port 587 at ito ay nagtrabaho fine para sa akin.
  • Sa aking kaso, 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, Mayroon akong dalawang mga attachment at sila ang parehong nagtrabaho fine.

Ginamit ko ang visual studio 2008 upang isulat ang code na ito.

</dulo>

Mag-subscribe sa aking blog.

Sundin ako sa Twitter sa http://www.twitter.com/pagalvin

Technorati Tags: ,,,

SharePoint Conference 2009 - Kumuha ng iyong Real Time Raw Data Mula sa Twitter

Mag-iwan ng reply

Inaasahan ko na halos lahat alam ito pa rin, 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, may isang pulutong ng kahangalan at "in" na mga jokes, ngunit kung maaari kang makakuha ng nakalipas na, subukan ito. I do my best to respond to comments or questions directed to me and I know that a lot of others do as well, kaya ito ay hindi lamang isang one-way na daloy ng impormasyon.

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

Tingnan ang kaba feed dito: http://twitter.com/#search?q=%23spc09

</dulo>

Mag-subscribe sa aking blog.

Sundin ako sa Twitter sa http://www.twitter.com/pagalvin

Technorati Tags:

Programming Extracting Attachment Mula Forms InfoPath (Kabilang ang kanilang Pangalan!)

Mag-iwan ng reply

I have an expense entry solution for a client that leverages InfoPath and workflow. At one point during the approval process, Kailangan ko upang bumuo ng isang email na may lahat ng mga mahusay na data InfoPath pati na rin ang kalakip ang kanilang mga sarili upang (buntong-hininga) isang tao ay maaaring tumagal ng data na iyon at manu-manong muling key ito sa isang application Oracle database.

It’s not very difficult to get at or parse the InfoPath form. I didn’t know how to handle the attachments, gayunman. After an hour or two of poking around the Internets (isang kawalang-hanggan!) Nakita ko ang artikulong ito: http://support.microsoft.com/kb/892730

It provide some handy code to extract the attachment from a node in the form. (Kailangan mo pa rin mahanap ang node at ang lahat na, ngunit ito lamang ay parse ng XML).

Alam ko na ang attachment ay base64-encode at ako nagpunta ang orihinal pababa sa landas ng extracting lamang ang mga base64 data, decoding it and saving it. Gayunman, Ako mabilis na natanto Hindi ko alam kung paano makuha ang pangalan ng file mismo hanggang sa nakita ko ang nabanggit na artikulo.

Talagang ako ay natagpuan na masyadong maaga, ngunit ako ay ilagay off sa pamamagitan ng split pagkatao. Sa isang banda, the article *says* it’s good for InfoPath 2007. Pa, ang code at mga tagubilin ay ang lahat ng tungkol sa Visual Studio 2003 at mga sanggunian sa InfoPath 2003.

Ika-line, ang code na ibinigay artikulo ay mahusay na gumagana para sa akin (hanggang ngayon). I can get my InfoPath form, Maaari ko bang i-parse ito, I can find and decode the attachment and I know its name. What more can one ask of one’s life?

</dulo>

Mag-subscribe sa aking blog.

Sundin ako sa Twitter sa http://www.twitter.com/pagalvin

Technorati Tags: ,,

Kung ikaw ay nag-aalala na ang iyong SharePoint kapaligiran ay maaaring maging isang tad masama sa katawan, hayaan mo akong makatulong sa iyo na ayusin may isang kalusugan tseke.

SharePoint Shop Talk para sa pagbabalik-tanaw 10-08-2009

6 tugon

SharePoint Mamili Ngayon Talk sakop karaniwan nitong malawak na hanay ng mga paksa:

  • 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, ngunit kapag sinimulan mo ang pinag-uusapan nang malakas, 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, paglilisensya (ang iyong intranet SharePoint lisensya ay maaaring hindi, at marahil ay hindi magiging, sapat), SharePoint configuration (AAM, pagpapahaba ng mga web application upang zone na marahil na HTTPS pinagana), at iba pa. 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 (hanggang ngayon).
  • 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, isang Talk SharePoint Shop regular, point out sa blog na ito 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.
  • Tinalakay namin pasadyang mga form edit (na lumikha sa iyo sa pamamagitan ng 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

Sa linggong ito, ipinakilala namin ang isang bagong tampok na kung saan namin na ginugol tungkol sa 10 minutes demonstrating an interesting tip/trick in a SharePoint environment. Sa linggong ito, kami ay nagpakita kung paano Nagdagdag ng nilalaman ng web editor bahagi (at talagang anumang web bahagi) to a newitem.aspx page. Sa kasong ito, 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. Sa susunod na linggo, we do plan to show a jQuery tip/trick. Umaasa kaming makita ka doon.

</dulo>

Mag-subscribe sa aking blog.

Sundin ako sa Twitter sa http://www.twitter.com/pagalvin

Technorati Tags:

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

Mag-iwan ng reply

Kami ay nagho-host sa aming mga susunod na linggo-linggo SharePoint Shop Talk session bukas sa 12:30 PM EDT.

Ito ay isang bukas na Q&A and general kibitzing session on all topics SharePoint related.

Maaari mong basahin ang iba't-ibang mga recaps ng naunang session dito upang makakuha ng ideya ng kung ano ang ginagawa namin sa mga tawag na ito dito: http://paulgalvin.spaces.live.com/?_c11_BlogPart_BlogPart=blogview&_c=BlogPart&partqs=cat%3dPublic%2520Speaking

Pagpaparehistro ay up at handa dito mismo: https://www.livemeeting.com/lrs/8000043750/Registration.aspx?pageName=0z40kg9nb0t0842f

Twitter ang iyong mga tanong sa akin, "Unan.

I-email ang mga ito sa questions@sharepointshoptalk.com or just show up on the line and ask them out loud.

Umaasa kaming makita ka pagkatapos!

</dulo>

Mag-subscribe sa aking blog.

Sundin ako sa Twitter sa http://www.twitter.com/pagalvin

Technorati Tags:

Upang Blog o Hindi upang Blog - Iyon ay ang mga Tanong (sa Blog Tungkol sa)

1 Sumagot

Nota: Ito ay orihinal na post sa www.endusersharepoint.com.

A few weeks ago I had the chance to speak at SharePoint Saturday in New York. Minsan pa, a tremendous event. Oras na ito, I spoke about “learning SharePoint” – a very broad topic. During the presentation (kung saan maaari kang makakuha dito), Ako uusapang tungkol sa iba't-ibang mga pamamaraan para sa "pag-aaral" SharePoint, kabilang ang mga bagay tulad ng pag-aaral libro, class na kuwarto ng pagsasanay, paglikha ng iyong sariling VM at pinaka-mahalaga (akin), 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, Ako scratching na pangangati sa pamamagitan ng pag-blog tungkol dito.

Ang ilang mga tao tila sa tingin na may mga kaya maraming mga kalidad ng mga blogger out doon sa scene ngayon at na kaya maraming mga kalidad blog entry na nakasulat na sa isang kahulugan, there’s nothing new to write about. O, 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.

Para sa starters, kung ikaw ay blogging dahil ito ay bahagi ng iyong personal na pagtatangka sa pag-aaral na rin SharePoint, it’s really irrelevant if someone has written on your topic or not. One of the drivers behind community participation, kung ito ay para sa personal na pag-aaral o hindi, ay na sa iyo kailangan upang makakuha ng ito ng tama. 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, ka pagpunta sa tingin ng paksa sa pamamagitan ng mas mabuti, at iba pa. Thus, pinag-iisipan mo, pag-aaral at isinasaalang-alang sa paksang ito mula sa lahat ng uri ng mga anggulo, kaliwa hanggang kanang-, hanggang pababa, loob at sa labas (o hindi bababa sa dapat mong maging). That’s a very valuable exercise. Sa katunayan, 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. Talaga, mo nais na itulak ang pindutan post pa rin para sa isang iba't ibang mga kadahilanan, but I digress. The bottom line is that blogging is a valuable learning exercise in and of itself, panahon.

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, iba't ibang mga estilo ng pagsulat, different approaches to the same problem – they all help me understand what I need. In my opinion, ang komunidad ay walang kung saan malapit sa pag-abot sa saturation point sa magandang kalidad ng mga artikulo blog sa anumang paksa sa mundo SharePoint.

Kaya, blog ang layo! You won’t hear me complaining about it. Ginagarantiya ko ito 🙂

</dulo>

Mag-subscribe sa aking blog.

Sundin ako sa Twitter sa http://www.twitter.com/pagalvin

Technorati Tags: ,

Huwag Maging isang Bull sa China Shop

Mag-iwan ng reply

Isang Maikling Kasaysayan ng SharePoint (Mula sa pananaw ng isang bagong dating Kamag-anak ni)

Nota: This article was originally posted to www.endusersharepoint.com. Nakalimutan kong mai-post ito sa sarili kong blog 🙂

SharePoint ay umunlad ng mahusay na deal nito mula noong unang bahagi ng araw bilang isang uri ng pagpapapisa ng itlog ng isang teknolohiya sa Microsoft –ito ay umunlad halos tulad ng isang pelikula malaking sindak, 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, gayunman, 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: tukuyin ang mga kinakailangan sa IT, maghintay para sa IT gawin ang kanilang trabaho sa likod ng tabing at kumuha ng paghahatid ng panghuling produkto.

Tulad ng SharePoint upang umunlad ang 2.0 mundo (WSS 2.0 at SharePoint Portal Server), several things happened. Una, the “problem domain” increased in size. By problem domain, I mean the kinds of business problems for which SharePoint could be a viable solution. Halimbawa, hindi mo gusto sa tingin masyadong matigas tungkol sa pagpapatupad ng isang seryosong solusyon sa paghahanap sa isang kapaligiran sa SharePoint hanggang sa SPS (at kahit na pagkatapos, ito ay hindi bilang mabuting bilang ito kinakailangan upang maging). Sa parehong oras, Mga End User magkaroon ng isang hindi pa nagagawang kakayahan upang hindi lamang tukuyin ang, 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). Sa parehong oras, 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 business analyst, 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 / Lumot?

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

  • The problem domain is going to dramatically expand.
  • Mga End User ay mahanap ang kanilang mga sarili kahit na higit pa kaysa empowered bago.

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.

Walang Bulls sa Aking China Shop!

Ito mahusay na tunog, ngunit mula sa aking mga punto ng view ng bilang isang consultant SharePoint at paglalagay ng sarili ko sa shoes ng isang IT manager, I see this vision. I own a China shop with beautiful plates, kristal, at iba pa (aking SharePoint kapaligiran). 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, ngunit sa mga pag-asa, 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 dalawa bulls and even a wolf. Then I notice that there are some sheep. Sheep are kaya masama, 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. Gayunman, 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, mangyari pa. End Users are not bulls (most of them, gayon pa man) and IT departments don’t (o dapat ay tiyak na hindi) view their user community with that kind of suspicion. Gayunman, mayroong ganitong uri ng perpektong banggaan nagaganap pa sa mga 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.

Iyan ay mahusay at lahat, ngunit ang katotohanan ay na pa ito sa isang napaka-teknikal at produkto pa rin ng mga tawag para sa uri ng malusog na kinakailangan pagtatasa ng negosyo, 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, halimbawa. 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 (sa www.endusersharepoint.com at sa ibang lugar) so that interested End Users can learn that old time IT religion. Keep tuned.

</dulo>

Mag-subscribe sa aking blog.

Sundin ako sa Twitter sa http://www.twitter.com/pagalvin

Technorati Tags: ,