Katika Sifa ya jQuery Enhanced Search-Kama Aina ya-Wewe- (na Jan Tielens)

Acha reply

Nafanya kazi demo BPOS (hivi karibuni kuwa inapatikana kwenye tovuti ya Microsoft) and I wanted to add a little pizzazz. I’ve known about Jan Tielen ya juhudi kwa muda kabisa na mimi walidhani itakuwa mbinu kubwa na kuongeza 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 (na labda ni mahali fulani).

Mimi kuongeza pointi mbili tu kwa kile tayari kuundwa / aliandika kuhusu:

  1. Hii haina, kwa kweli, kazi katika BPOs (SharePoint online) mazingira.
  2. Kufanya kazi yake bila ujumbe annoying popup kiambishi kumbukumbu ya maktaba na jQuery https badala ya http, kama katika:
<script aina ="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 🙂

</mwisho>

Hii ni baada ya mwingine katika wangu inayoendelea mfululizo ya jinsi ya kutumia jQuery na SharePoint.
Kama unataka kujifunza zaidi kuhusu jQuery, Mimi sana kupendekeza: jQuery katika Action na kubeba Bibeault na Yehuda Katz.

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

Tags technorati:

SharePoint duka Majadiliano Alhamisi 10/29 katika 12:30 PM EDT

Acha reply

ijayo SharePoint duka Majadiliano unafanyika hii Alhamisi saa 12:30PM EDT.

Tumekuwa kuchukuliwa wiki mbili mbali (kutokana na SharePoint Mkutano wa wiki iliyopita) na kama matokeo, tuna idadi ya maswali katika foleni, 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 (Sishangai 🙂 ).
  • Embedding RSS feeds into a site when the source is authenticated.
  • Using stsadm to manage logging.

Kujiandikisha hapa: https://www.livemeeting.com/lrs/8000043750/Registration.aspx?pageName=p663256djrrflfdw

As usual, kutuma maswali au mada majadiliano questions@sharepointshoptalk.com, email yangu moja kwa moja au Twitter @ pagalvin.

Tunatarajia kuona wewe huko!

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

Haraka Hit: Kusoma InfoPath XML moja Kutoka SPListItem katika SharePoint

1 Kujibu

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 (ambayo ni haki ya XML files, hivyo ni kweli kabisa rahisi).

Wakati mimi ilikuwa kujenga mradi, I started by downloading an InfoPath form and saving it to my local hard drive. My c# code was reading directly from that instance. Hata hivyo, 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. Hata hivyo, there’s no need to go through those hoops as you can read it directly from the library. This little snippet shows how:

/// Hatari ufafanuzi mambo hapa, ikiwa ni pamoja na:
binafsi SPFile mySharePointFile; /* Sehemu ya SPList */
// Zaidi ya kanuni huenda hapa na ndani ya njia ya darasa tuna:
XmlTextReader textReader;
textReader = mpya XmlTextReader(mySharePointFile.OpenBinaryStream());

textReader.WhitespaceHandling = WhitespaceHandling.Hakuna;

textReader.Read();

// Kama nodi ina thamani

wakati (textReader.Read())
{

… and so on and so forth …

Wao muhimu kidogo hapo juu ni kwamba tunaweza kusoma InfoPath moja kwa moja kupitia OpenBinaryStream() method call on the SPFile as a parameter to the constructor on XmlTextReader. It works great.

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

Tags technorati:

Haraka na Easy: Tuma Barua pepe Kutumia Gmail SMTP Server katika C NET. #

2 majibu

Hii si hasa mada mpya, lakini wakati mimi zinahitajika kufanya hivyo, I found a lot of “why won’t this work for me” and not too many direct answers. I hope someone finds this useful.

kidogo yafuatayo ya maadili ya kutuma email kwa kutumia gmail yangu mwenyewe akaunti ya kufanya hivyo, ikiwa ni pamoja na attachments:

kutumia System.Net.Mail;
kutumia System.Net;

NetworkCredential loginInfo = mpya NetworkCredential("[ID yangu ya Gmail]", "[Siri yangu ya Gmail]");
MailMessage msg = mpya MailMessage();
msg.From = mpya MailAddress("[M Gmail Id]@ Gmail.com");
msg.To.Add(mpya MailAddress("paul.galvin@arcovis.com"));
msg.Subject = "Test infopath dev subject";
msg.Body = "<html><mwili><nguvu>ujumbe mzito.</nguvu></mwili></html>";
msg.IsBodyHtml = kweli;

foreach (string aFile katika NIPFD.GetAttachmentNamesAndLocations())
{
    msg.Attachments.Add(mpya Attachment(aFile));
} // Kuongeza attachments.

SmtpClient mteja = mpya SmtpClient("smtp.gmail.com");
client.EnableSsl = kweli;
client.UseDefaultCredentials = uongo;
client.Credentials = loginInfo;
client.Port = 587;
client.EnableSsl = kweli;
client.Send(msg);

chache muhimu bits kwamba umepungua yangu chini na uchunguzi mwingine / maelezo:

  • mstari wa kwanza kuwa inajenga kitu loginInfo mahitaji ya kutumia ID gmail kuvuliwa "@ Gmail.com". Hivyo, kama yangu ya barua pepe ni gmail "Sharepoint@gmail.com"Na password yangu ni" xyzzy "basi line bila kuangalia kama:

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

  • Akaunti yangu ya gmail ni kuanzisha kutumia SSL na kwamba halikuwa tatizo.
  • There is some conflicting information out there on what port to use. I used port 587 na ni kazi nzuri kwa ajili yangu.
  • Katika kesi yangu, 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, Mimi nilikuwa na attachments mbili na wao wote kazi nzuri.

Nilikuwa studio ya Visual 2008 kuandika kanuni hii.

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

Tags technorati: ,,,

SharePoint Mkutano 2009 - Kupata muda wako Halisi Takwimu Malighafi Kutoka Twitter

Acha reply

Nategemea kuwa karibu kila mtu anajua hii anyway, 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, kuna mengi ya puo na "katika" utani, lakini kama unaweza kupata nyuma kwamba, kuangalia ni nje. I do my best to respond to comments or questions directed to me and I know that a lot of others do as well, hivyo si tu kati yake njia moja ya habari.

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

Angalia kulisha Twitter hapa: http://twitter.com/#search?q=%23spc09

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

Tags technorati:

Programmatically madini Attachments Kutoka Fomu InfoPath (Ikiwa ni pamoja na Majina yao!)

Acha reply

I have an expense entry solution for a client that leverages InfoPath and workflow. At one point during the approval process, Mimi haja ya kuzalisha email kwamba ina wote wa data kwamba nzuri InfoPath vilevile attachments wenyewe, ili (wanaougua) mtu anaweza kuchukua data kwamba na manually re-ufunguo ndani ya maombi database Oracle.

It’s not very difficult to get at or parse the InfoPath form. I didn’t know how to handle the attachments, hata hivyo. After an hour or two of poking around the Internets (milele!) Nimeona makala hii: http://support.microsoft.com/kb/892730

It provide some handy code to extract the attachment from a node in the form. (Bado unahitaji kutafuta nodi na wote, lakini hiyo ni XML parsing).

Najua kwamba attachment ni Base64-encoded na mimi awali akaenda chini njia ya kuchimba tu data Base64, decoding it and saving it. Hata hivyo, Mimi haraka waligundua sikujua jinsi ya kupata jina la faili yenyewe mpaka nimeona makala aforementioned.

Nilikuwa kweli kupatikana kwamba mapema kabisa, lakini mimi nilikuwa kuweka mbali na kupasuliwa utu wake. Kwa upande mmoja, the article *says* it’s good for InfoPath 2007. Hata hivyo, kanuni na maelekezo yote kuhusu Visual Studio 2003 na marejeo ya InfoPath 2003.

Bottom line, kificho kwamba makala zinazotolewa ni kazi vizuri kwa ajili yangu (hadi sasa). I can get my InfoPath form, Siwezi Hazrat ni, I can find and decode the attachment and I know its name. What more can one ask of one’s life?

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

Tags technorati: ,,

Kama wewe ni wasiwasi kwamba SharePoint yako mazingira inaweza kuwa mbaya tad, napenda kukusaidia kurekebisha kwamba na kuangalia afya.

SharePoint duka Majadiliano kurejea kwa 10-08-2009

6 majibu

Leo SharePoint duka Majadiliano kufunikwa pana yake ya kawaida ya mada mbalimbali:

  • 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, lakini wakati wewe kuanza kuzungumza juu ya sauti, 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, leseni (yako intranet SharePoint leseni inaweza kuwa, na pengine kuwa na, kutosha), SharePoint Configuration (AAM, kupanua matumizi ya mtandao wa maeneo ya kwamba pengine HTTPS kuwezeshwa), nk. 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 (hadi sasa).
  • 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, Duka SharePoint Majadiliano ya mara kwa mara, pointi nje kuingia hii blog: 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.
  • Sisi kujadiliwa desturi aina hariri (kwamba kujenga kupitia 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

Wiki hii, sisi ilianzisha kipengele mpya ambapo sisi alitumia kuhusu 10 minutes demonstrating an interesting tip/trick in a SharePoint environment. Wiki hii, sisi ilionyesha jinsi ya mhariri aliongeza maudhui ya mtandao sehemu (na kwa kweli sehemu yoyote ya mtandao) to a newitem.aspx page. Katika kesi hiyo, 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. Wiki ijayo, we do plan to show a jQuery tip/trick. Tunatarajia kuona wewe huko.

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

SharePoint duka Majadiliano 10/08/08 katika 12:30 PM EDT

Acha reply

Sisi ni mwenyeji wa kila wiki yetu ijayo SharePoint duka Majadiliano kikao kesho saa 12:30 PM EDT.

Hii ni wazi Q&A and general kibitzing session on all topics SharePoint related.

Unaweza kusoma recaps mbalimbali ya vikao vya kabla ya hapa kupata hisia ya kile sisi kufanya juu ya simu hizi hapa: http://paulgalvin.spaces.live.com/?_c11_BlogPart_BlogPart=blogview&_c=BlogPart&partqs=cat%3dPublic%2520Speaking

Usajili ni juu na tayari hapa hapa: https://www.livemeeting.com/lrs/8000043750/Registration.aspx?pageName=0z40kg9nb0t0842f

Twitter maswali yako kwangu, "Mito.

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

Tunatarajia kuona wewe basi!

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

Kwenye Blogu au si kwa Blogu - Hiyo ni Swali (kwenye Blogu Kuhusu)

1 Kujibu

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

A few weeks ago I had the chance to speak at SharePoint Saturday in New York. Mara nyingine tena, a tremendous event. Wakati huu, 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 (kwangu), 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. Au, 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, nk. 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. Kwa kweli, 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. Bila shaka, 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.

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

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

Tags technorati: ,

Je, si Kuwa Bull katika duka China

Acha reply

Historia fupi ya SharePoint (Mtazamo kutoka Mgeni Uzito ya)

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

SharePoint imebadilika mpango mkubwa tangu siku yake ya kwanza kama aina ya teknolojia ya incubation saa Microsoft –ni tolewa karibu kama horror movie, 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, hata hivyo, 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. Kwanza, the “problem domain” increased in size. By problem domain, I mean the kinds of business problems for which SharePoint could be a viable solution. Kwa mfano, 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). Wakati huo huo, 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). Wakati huo huo, 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 biashara mchambuzi, 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, nk (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 mbili bulls and even a wolf. Then I notice that there are some sheep. Sheep are hivyo mbaya, 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. Hata hivyo, 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, bila shaka. End Users are not bulls (most of them, anyway) and IT departments don’t (or surely should not) view their user community with that kind of suspicion. Hata hivyo, 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, kwa mfano. 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 (on www.endusersharepoint.com na mahali pengine) so that interested End Users can learn that old time IT religion. Keep tuned.

</mwisho>

Kujiunga na blog yangu.

Kufuata yangu juu ya Twitter kwa http://www.twitter.com/pagalvin

Tags technorati: ,