WebPart
There are 35 entries for the tag WebPart
[code] /// <summary> /// Gets or sets the site URL. /// </summary> /// <value>The site URL.</value> [WebBrowsable(true), WebDescription("Url of the site to process reports on"), WebDisplayName("Site Url"), Personalizable(Personalizat... public string SiteUrl { get { if (string.IsNullOrEmpty(siteU... { return SPContext.Current.Web.Url; } return siteUrl; } set { siteUrl = value; } } [/code] The above code snippet looks like a reasonable WebPart Propperty. In-fact...
Dated: March/2008 Yes as saddening that sounds, it seems it is true. Having a bit of slack time and not being able to give VS2008 a whirl earlier due to project pressures, I broke it out today all eager to gauge what elegance this IDE brings, specially since I had the need to write a test WebPart. Out of instinct I went File -> New Project -> *hold up where is the SharePoint Category. So then me thinks ah! its not built in to the product, maybe another extension for Visual Studio. So googled...
A little obscure fact about WebPart Connections. If you are writing a WebPart that is a Provider as well as a Consumer it is better to give your ConnectionPoint's unique Ids. Infact if you have multple Providers on the same WebPartPage the connections wont work unless each ConnectionPoint like so [ConnectionProvider("Displa... "ConnectionPointId")]public IWebPartField ConnectionInterface(){return this;} Technorati tags: MOSS, WebParts, Connections, ConnectionPoint Ids Cross-posted from tariqayad.com...
Its wierd, and I cant make head or tail of it. I was writing a webpart today, and I was maintaining a generic stack collection which I wanted to place in the session. What is wierd is that if i were to add object of type Stack <T> to the session, SharePoint says an unrecoverable error has occurred. The moment I changed the stack from a generic to a plain old .NET 1.1 non-generic Stack the error was gone. tags: SharePoint, WebParts, Generics, Session Cross-posted from tariqayad.com...
Apparently there is a chart webpart at the FrontPage add-in center. Go check it out - http://www.microsoft.com/fr
Every other SharePoint blogger by now must have already praised CaveDigital's XML Form WebPreviewer WebPart So I am going to do it as well. Pedro, good job on the release. I am sure a lot of us SharePoint Developer types would be exclaiming a sigh of releif, esspeically becuase you will be saving them the trouble of explaining why each user would need to install InfoPath otherwise. Here is a link to the Product: http://www.cavedigital.com/...
59 Dr E.A. Cooray Mw, Wellawatte, Colombo 6, Sri Lanka +94 11 2360793 tariqayad@gmail.com M. Tariq Al Ayad OBJECTIVE An experienced Software Engineer in .NET Development with a keen interest in SharePoint Technologies and high-tech collaboration solutions, having experience in working on project teams as well as leading teams from a technical aspect Enjoys learning new skills and is confident working in different cultures. EMPLOYMENT STATUS I am currently employed but am open to discussing fulltime,...
Recently I had a requirement where the stakeholder for a WSS Site wanted what I call 'Visual Security' i.e. basically where the interface does not render what the user does not have rights to. The requirement wasnt too extensive, they just wanted a few links to lists and a few list forms hidden if the user didnt have the right to add items. And they werent moved by attempts to convince them that content discovery is a good thing. So in the end had to cough up a POC WebPart simmilar to the Content...
What a frustrating day. I spent hours looking for a code snippet on google on how to achieve something that I was very sure I had done. I was looking for the snippet which does not bring up the enter credential box if the user does not have rights for a sharepoint section. I knew it could be done, I had done it before. I spent an awfull long time searching the newsgroups (as i recalled the place i had seen it the first time). All this for what? just the one line below // Prevent the request for access...
Ian recently posted about a WebPart called R.A.D Editor. Which is actually super brilliant, and I am sure most of us would more than welcome a tool of its capabilities, but me as a developer am wondering whether the $349s is worthwhile considering the alternatives such as FreeTextBox and FCKEditor. For a simple WSS solutions it might be it might be cheaper to write a simple content editor based on the 2 mentioned above. In the long run considering my woes with SharePoint's RTE and image functionality...
I found this series of WebParts being linked to from Micheal Greths blog. Theres a couple of good stuff in there including a Poll WebPart & Quiz WebPart amongst others. I had previously not subscribed to Micheal Greths blog since its mainly in German, and having to language translate an RSS feed is no fun, now I think I should just in case not to miss stuff like this. ...
Breadcrumbs for SharePoint has become a very popular WebPart, amongst developers and WebPart vendors. I've seen quite a few of these and most of them have one inherrent problem. From the ones I've seen it appears that most of the developers assumed that if a user visiting a site somewhere down the site hierarchy they naturually had rights to the parentwebs. This assumption is wrong, and such an assumption should not be made because its not unusual where you would want to give rights to specific sites...
Lately I’ve been puzzled by a hypothetical scenario with regard to SharePoint’s indexing. Consider that you have a bunch of WSS Sites named A, B & C. Now it is understood that the contents of A, B & C will get indexed in their own time. But supposing a WebPart page on A had links to B & C. Now would the crawl follow those links to B & C, index the contents of those sites and then return to indexing the contents of A? Or would B & C just be queued and processed in their own time....
Good tip from Barry on WebPart development. http://www.barracuda.net/ba...
Maurice shares some thoughts on what most probably might be with the next Version of SharePoint. He also mentions vaguely the nuance of developing and deploying WebParts. The fact is SharePoint v Next will built on the next version of Asp.net. I am sure that most of you would agree that WSS is today what it is because of Asp.net. The move up from SPS 2001 or STS to SharePoint 2003 was phenomenal. All that productivity capabilities just opened up with the 2003 versions. I suspect that we can look...
As a developer wanting to create a WebPart that needs a date picker everybody will tempted to use SharePoint's date picker. Unless you know how to use it you are going to run into a couple of gotchas. Basically everybody initially stumbles, trying to find a way to get it to display. What you should ideally do to use the OWSDateField is OWSForm frm1 = new OWSForm(); OWSDateField df1 = new OWSDateField(); frm1.Controls.Add(df1); If you are creating an ASP.NET form, you would need to have the following...
I am not sure if this has been already done, but I think it’s about high time someone started consolidating a list of tools that are out for SharePoint. I am thinking of something similar to the SharpToolbox. Of course the list will not be huge like the CSharp list at SharpToolbox, but I think we’ve got enough to go around. So let me start it off by providing the ones I know, you guys can contribute by adding the ones you know to the comments system of this post, and I will update the...
If you’ve seen my earlier posts on SharePoint Single Sign-On, you would remember that I showed some curiosity regarding the role of the Canary in SharePoint. So here is Chris’s (the nice chap I mentioned in those posts) take on it. The “canary” was implemented to thwart a variety of cross site scripting / single click attacks. Examples include receiving a mail with a link to a malicious web site that then tries to either redirect you to another page or otherwise use your identity...
For a long time I’ve wanted to try out Jim Duncan’s Connectable Page Viewer WebPart, but for some reason or other, the setup never worked proper for me. It runs halfway and stops. Today with the use of a new tool I found I was able to finally install that WebPart. That tool is Make MSI. Its some freebie I found on the net, it lets you do several MSI related tasks, and one of them is to run the MSI with verbose logging. So what did the log tell me about the failed install of “Collutions Web Part -...
If you are into WebPart development then you would find Maurice Prathers post on changing a WebPart title programmatically informative, especially from the point of view of the WebPart framework event model
If you are into WebPart development then you will find Maurice Prathers post on changing a WebPart title programmatically informative, especially from the point of view of the WebPart framework event model
Some things I got burnt by recently. Hope you guys are aware of these. 1) If you right click on a WebPart Page on a document library and say Save Target As (i.e. from IE’s context menu) what you are going to get is the HTML normally sent to the browser and not the WebPart composition. It makes perfect sense actually since the browser is requesting for a ‘Smart Page’ from SharePoint and there for SharePoint sends it HTML. Now having said that even though it makes perfect sense it is not too obvious....
My earlier frustration with a programming issue I had with SharePoint Portal Server Single Sign On (SPS SSO) came to the attention of very nice chap inside Redmond . All I can say about this chap is that he is very nice, goes by the name of Chris, and works with SharePoint Portal Server; Did I say he was nice guy already? Well anyway he is a nice chap. He was able to throw a suggestion at me that actually bowled me over. It was one of those things that go totally un-noticed until someone points it...
Actually I am complaining about very simple bit of code. It is so simple that even I could write it (or copy and paste it) a million times. All I want to do is to set a user’s Credentials into the Single SignOn database from a WebPart, but the frigging thing keeps failing. string[] rgSetCredentialData = new string[2]; rgSetCredentialData[0] = "2ser"; rgSetCredentialData[1] = "rb26dett"; Credentials.SetCredentials( 1, "TestSSOAPP", rgSetCredentialData); The error returned is SSO_E_CANARY_VALIDATION_FAI...
I found out today to my surprise that you can actually use the DataView WebPart (and all all the other SharePoint WebParts) as a control in a WebPart that you are creating. Isn’t that sweet? Its also remarkably easy to use. It goes something like this class YourWebPart : Microsoft.SharePoint.WebPar... { ... private DataViewWebPart dvwp; ... protected override void CreateChildControls() { ... dvwp = new DataViewWebPart(); dvwp.DataFields = DATAFIELDS; dvwp.DataQuery = QUERY; dvwp.Xsl =...
This may be old news but… It’s nice to see a technology that was in SharePoint for sometime finally find its way in to ASP.NET. When I first got my hands on SharePoint 2003 in its early Beta stages I was totally in awe about the WebPart Framework. On this note does anyone have an idea when we will get to see what killer features would be present in SharePoint Version Next (perhaps it’s too early to ask)...
Do you guys know about these bugs? - 320439 - 817036 Well theres a simmilar issue with SharePoint, and I suspect that its ASP.NET at play underneath. Try this create a webpart that tries to transfer control onto another page in SharePoint. for e.g. protected override void RenderWebPart(HtmlTextWriter output) { try { Context.Server.Transfer(def... // Context.Server.Execute(defa... } catch (Exception e) { output.Write(e.ToString()); } } What you should see on the WebPart page is error...
Was checking compatibility of the Office 2003 WebPart today. On a machine that doesnt have Office 2003 installed the WebPart gives the following error. "To use either the Spreadsheet Web Part or the PivotView Web Part, you must have Microsoft Internet Explorer 5.01 Service Pack 2 (SP2) or later and the Microsoft Office 2003 Web Components installed on your computer. See the Microsoft Office Web site for more information. Install the Office 2003 Web Components." Interestingly enough the link pointed...
This a vital bit of information for every WebPart developer. AccessDeniedException <- wow didnt know about that one - :) Good article Patrick, thanks
Recently I noticed a neat fact about the Search Results WebPart; that is how it responded to a failure with the index database, and I think this is pretty cool - "Hats off to Microsoft, for thinking about this" Consider a situation when the SPS is unable to connect to its Search Indexes, like for instance due to a database corruption, or the configuration database account being invalid, then as a result of this severed connection the search shouldn’t work (obviously), or perhaps give horrendous error...
Draft1-(wanted to post this before I forget I was writing this in the first place :) ) Over the past few days I've been playing around with WordML; and I think the possibilities for it from the point of view of an Intranet, are really exciting . Consider Ian Morrish's example of a WordML document being displayed on a WebPart page. With a few tweaks to the XSLT, you can limit the visible portions of the document to only that neccesary for public view. Stuff you would need to play around with this...
Check out Paul Schaeflein's blog He has a lot of information published that my team learnt the hard way, through experimentation during our project's development cycle. This is going to be a great benefit to WebPart developers old and new
I am not really sure if I've posted anything on this topic before. I feel like I have, but if so I couldnt find the post in the archive. So I am risking a second post. However I did asked a similar question up on the sharepoint newsgroup some time back.Over the past few months my team has been building an intranet application based on SharePoint. We've basically being rolling out our own custom WebParts.Whats very odd about managing a WebPart development project is that, versioning is a pain.To increment...
Deploying WebParts after you make a build is a bit of a hassle especially because you have to leave you IDE to do a couple of things. The basic process is you need to 1. Compile 2. Install the assembly to the GAC 3. Copy assembly to c:\inetpub\wwwroot\bin 4. Recycle the MS SharePoint default app pool - to invoke the new instance of the assembly -> Typically you will have to switch between VS.NET, InetMgr, and the command prompt. So here’s what I do. 1. My WebPart projects have their default...
Paschal has a post at dotnetweblogs on a couple ASP.NET lessons learnt. Just a note to SPS Developers. Dont you think this does not apply to you. One thing you should learn if WebParts are your game, pay close attention to anything that happens in the ASP.NET Custom Server control arena, because they both share the same bloodline. I took a different approach with regard to sharing SPS lessons learnt. What i did was Got the team to put up a SharePoint Social Meeting workspace. Created tab pages for...