Në Falënderimi i jQuery Enhanced search-si-ti-Type (nga Jan Tielens)

Lini një përgjigje

Unë jam duke punuar në një demo BPOs (së shpejti të jenë në dispozicion deri në faqen e Microsoft-it) and I wanted to add a little pizzazz. I’ve known about Jan Tielen’s efforts for quite a while and I thought it would be a great technique to add to the 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 (and maybe is somewhere).

I add just two points to what he already created / wrote about:

  1. This does, në të vërtetë, work in a BPOS (SharePoint online) mjedis.
  2. To make it work without an annoying popup message prefix the reference to the jquery library with https instead of http, si në:
<Lloji script ="text/javascript" src ="https://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js"></dorëshkrim>

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 🙂

</fund>

Kjo është një tjetër post në tim në vazhdim seri e se si të përdorin jQuery me SharePoint.
Nëse doni të mësoni më shumë në lidhje me jQuery, I highly recommend: jQuery në Veprim nga Bear Bibeault dhe Yehuda Katz.

Abonohen në blogun tim.

Atëherë ejani pas meje në Twitter në http://www.twitter.com/pagalvin

Technorati Tags:

Talk SharePoint Shop e enjte 10/29 në 12:30 EDT

Lini një përgjigje

The next SharePoint Shop Talk takes place this Thursday at 12:30EDT.

We’ve taken two weeks off (due to SharePoint Conference last week) and as a result, we have a number of questions in queue, 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.

Regjistrohu këtu: https://www.livemeeting.com/lrs/8000043750/Registration.aspx?pageName=p663256djrrflfdw

As usual, send any questions or discussion topics to questions@sharepointshoptalk.com, email me directly or twitter to @pagalvin.

We hope to see you there!

</fund>

Abonohen në blogun tim.

Atëherë ejani pas meje në Twitter në http://www.twitter.com/pagalvin

Technorati Tags:

Hit i shpejtë: Leximi XML InfoPath direkt nga një SPListItem në SharePoint

1 Përgjigje

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 (të cilat janë vetëm fotografi XML, kështu që është e vërtetë mjaft e lehtë).

Ndërsa unë ishte ndërtuar projektin, I started by downloading an InfoPath form and saving it to my local hard drive. My c# code was reading directly from that instance. Megjithatë, 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. Megjithatë, there’s no need to go through those hoops as you can read it directly from the library. This little snippet shows how:

/// Përkufizimi Klasa gjëra këtu, duke përfshirë:
privat SPFile mySharePointFile; /* Pjesë e një SPList */
// Kodi More shkon këtu dhe në brendësi të një metodë të klasës kemi:
XmlTextReader textReader;
textReader = i ri XmlTextReader(mySharePointFile.OpenBinaryStream());

textReader.WhitespaceHandling = WhitespaceHandling.Asnjë;

textReader.Read();

// Nëse nyjen ka vlerë

ndërsa (textReader.Read())
{

… and so on and so forth …

Ata bit kyç sipër është se ne mund të lexoni InfoPath direkt nëpërmjet OpenBinaryStream() method call on the SPFile as a parameter to the constructor on XmlTextReader. It works great.

</fund>

Abonohen në blogun tim.

Atëherë ejani pas meje në Twitter në http://www.twitter.com/pagalvin

Technorati Tags:

Quick dhe Easy: Dërgo email duke përdorur Gmail Server SMTP në. NET C #

2 Përgjigje

Kjo nuk është saktësisht një temë të re, por kur unë e nevojshme për të bërë atë, I found a lot of “why won’t this work for me” and not too many direct answers. I hope someone finds this useful.

Bit e mëposhtme të kodit do të dërgoni një email duke përdorur vetë llogarinë time gmail për të bërë atë, duke përfshirë të bashkëngjitni skedarë:

përdorim System.Net.Mail;
përdorim System.Net;

NetworkCredential loginInfo = i ri NetworkCredential("[My Gmail ID]", "[My Gmail Password]");
MailMessage msg = i ri MailMessage();
msg.From = i ri MailAddress("[M Gmail Id]@gmail.com");
msg.To.Add(i ri MailAddress("paul.galvin@arcovis.com"));
msg.Subject = "Test infopath dev subject";
msg.Body = "<html><trup><strong>A strong message.</strong></trup></html>";
msg.IsBodyHtml = i vërtetë;

foreach (varg aFile në NIPFD.GetAttachmentNamesAndLocations())
{
    msg.Attachments.Add(i ri Attachment(aFile));
} // Adding attachments.

SmtpClient client = i ri SmtpClient("smtp.gmail.com");
client.EnableSsl = i vërtetë;
client.UseDefaultCredentials = i rremë;
client.Credentials = loginInfo;
client.Port = 587;
client.EnableSsl = i vërtetë;
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". Kështu, if my gmail email address is “sharepoint@gmail.com” and my password is “xyzzy” then the line would look like:

NetworkCredential loginInfo = i ri 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.
  • Në rastin tim, 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 had two attachments and they both worked fine.

I used visual studio 2008 to write this code.

</fund>

Abonohen në blogun tim.

Atëherë ejani pas meje në Twitter në http://www.twitter.com/pagalvin

Technorati Tags: ,,,

SharePoint Konferenca 2009 - Të marrë të dhëna Real kohën tuaj të papërpunuara nga Twitter

Lini një përgjigje

I expect that nearly everyone knows this 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, atje është një shumë e marrëzi dhe "ne" shaka, but if you can get past that, check it 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

</fund>

Abonohen në blogun tim.

Atëherë ejani pas meje në Twitter në http://www.twitter.com/pagalvin

Technorati Tags:

Programmatically Nxjerrjen Attachments nga forma InfoPath (Duke përfshirë edhe emrat e tyre!)

Lini një përgjigje

I have an expense entry solution for a client that leverages InfoPath and workflow. At one point during the approval process, Unë kam nevojë për të gjeneruar një email që ka të gjithë se të dhënat InfoPath të mira si të bashkëngjitni skedarë vetë në mënyrë që (psherëtimë) dikush mund të marrë që të dhënat dhe manualisht ri-kyç atë në një kërkesë bazë të dhënash Oracle.

It’s not very difficult to get at or parse the InfoPath form. I didn’t know how to handle the attachments, megjithatë. After an hour or two of poking around the Internets (një përjetësi!) Kam gjetur këtë artikull: http://support.microsoft.com/kb/892730

It provide some handy code to extract the attachment from a node in the form. (Ju ende nevojë për të gjetur nyjen dhe gjithçka që, por kjo është vetëm XML parsing).

Unë e di se shtojcë është base64-koduar dhe unë shkova fillimisht poshtë rrugën e vetëm nxjerrjen e të dhënave base64, decoding it and saving it. Megjithatë, Unë shpejt e kuptuan që unë nuk e di se si të merrni File Name veten deri sa kam gjetur artikullin e lartpërmendur.

Unë kisha gjetur në fakt që mjaft herët, por unë u shty nga personaliteti i saj të ndarë. Nga njëra anë, the article *says* it’s good for InfoPath 2007. Ende, Kodi dhe udhëzimet janë të gjitha në lidhje me Visual Studio 2003 dhe referencat ndaj InfoPath 2003.

Bottom line, Kodi neni, me kusht që është duke punuar mirë për mua (deri tani). I can get my InfoPath form, Unë mund të kuptoj atë, I can find and decode the attachment and I know its name. What more can one ask of one’s life?

</fund>

Abonohen në blogun tim.

Atëherë ejani pas meje në Twitter në http://www.twitter.com/pagalvin

Technorati Tags: ,,

Nëse jeni të shqetësuar se mjedisi juaj SharePoint mund të jetë një fëmijë i sëmurë, më lejoni të ju ndihmojë të rregullojmë se me një kontroll shëndetësor.

SharePoint Radhitje Shop Talk për 10-08-2009

6 Përgjigje

Talk SharePoint sotëm Shop zakonshme mbuluar gamën e saj të gjerë temash:

  • 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, por kur ju filloni duke folur me zë të lartë, 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, licencimit (Licenca intranet tuaj SharePoint nuk mund të jetë, dhe ndoshta nuk do të jetë, i mjaftueshëm), SharePoint konfigurimit (AAM, zgjerimin e aplikacioneve web në zonat që ndoshta kanë HTTPS aktivizuar), etj. 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 (deri tani).
  • 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, një Talk Shop SharePoint rregullt, thekson këtë term 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.
  • Ne diskutuam me porosi forma edit (që ju të krijoni nëpërmjet 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

Këtë javë, ne kemi prezantuar një tipar të ri, ku ne kemi shpenzuar rreth 10 minutes demonstrating an interesting tip/trick in a SharePoint environment. Këtë javë, kemi treguar se si për të shtuar një editor web content pjesë (dhe në fakt çdo pjesë web) to a newitem.aspx page. Në këtë rast, 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. Next week, we do plan to show a jQuery tip/trick. We hope to see you there.

</fund>

Abonohen në blogun tim.

Atëherë ejani pas meje në Twitter në http://www.twitter.com/pagalvin

Technorati Tags:

SharePoint Talk Shop 10/08/08 në 12:30 EDT

Lini një përgjigje

Ne jemi hosting pasardhësenext tonë javor Shop SharePoint sesion Talk nesër në 12:30 EDT.

Ky eshte nje Q hapur&A and general kibitzing session on all topics SharePoint related.

Ju mund të lexoni recaps të ndryshme të seancave të mëparshme këtu për të marrë një kuptim të asaj që ne bëjmë në këto thirrjet këtu: http://paulgalvin.spaces.live.com/?_c11_BlogPart_BlogPart=blogview&_c=BlogPart&partqs=cat%3dPublic%2520Speaking

Regjistrimi është i lart dhe i gatshëm të drejtë këtu: https://www.livemeeting.com/lrs/8000043750/Registration.aspx?pageName=0z40kg9nb0t0842f

Twitter pyetjet tuaja për mua, "Jastëkët.

Email ato për questions@sharepointshoptalk.com or just show up on the line and ask them out loud.

Ne shpresojmë të shohim ju pastaj!

</fund>

Abonohen në blogun tim.

Atëherë ejani pas meje në Twitter në http://www.twitter.com/pagalvin

Technorati Tags:

Për blog ose Jo në Blog - Kjo është Pyetje (në Blog Rreth)

1 Përgjigje

Shënim: This was originally posted to www.endusersharepoint.com.

A few weeks ago I had the chance to speak at SharePoint Saturday in New York. Once again, a tremendous event. Këtë herë, 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 (mua), 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. Ose, 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, etj. 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. Në të vërtetë, 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. Sigurisht, 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.

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

</fund>

Abonohen në blogun tim.

Atëherë ejani pas meje në Twitter në http://www.twitter.com/pagalvin

Technorati Tags: ,

Mos të jetë një Bull në Shop Kinë

Lini një përgjigje

Një histori e shkurtër e SharePoint (Nga këndvështrimi relativisht i sapofutur në)

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

SharePoint ka evoluar në një marrëveshje të madhe që nga ditët e tij të hershme si një lloj i teknologjisë inkubacion në Microsoft –ajo evoluar gati si një film horror, 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, megjithatë, 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. I parë, the “problem domain” increased in size. By problem domain, I mean the kinds of business problems for which SharePoint could be a viable solution. Për shembull, 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). Në të njëjtën kohë, 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). Në të njëjtën kohë, 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 / 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, etj (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 dy bulls and even a wolf. Then I notice that there are some sheep. Sheep are kështu keq, 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. Megjithatë, 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, sigurisht. End Users are not bulls (most of them, dosido) and IT departments don’t (or surely should not) view their user community with that kind of suspicion. Megjithatë, 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, for instance. 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 (në www.endusersharepoint.com dhe gjetkë) so that interested End Users can learn that old time IT religion. Keep tuned.

</fund>

Abonohen në blogun tim.

Atëherë ejani pas meje në Twitter në http://www.twitter.com/pagalvin

Technorati Tags: ,