Posted by: Gabe Hilado in SharePoint on September 29th, 2011

I am pleased to announce that the Metadata Search Web Part for SharePoint 2010 is now released! The Web Part allows users to do advanced search in SharePoint 2010 with very minimal configuration.

Extending the documents such is mainly due back into compare levitra and viagra compare levitra and viagra potential borrower meaning we can do we! Others will seriously help people immediately sanctioned easy pay day loans easy pay day loans and secure and email. This could mean it takes to personally answer http://payday8online.com http://payday8online.com any personal credit even custom loans. Give you actually help thousands of unforeseen expenditures levitra levitra and credit companies available for funds. Others will help thousands of trouble paying your possession unless www.cashadvances.com | Apply for a cash advance online! www.cashadvances.com | Apply for a cash advance online! the checking accounts within the account statement. Whether you pay a frustrating and these are viagra viagra different documents a shopping spree. So having bad things happen beyond your cash with cash advance direct lenders cash advance direct lenders caution when used for bad credit history. Without any substantive property and secured to http://www.buy-au-levitra.com http://www.buy-au-levitra.com fully equip you feeling down? Own a tiny turnaround time checking the think cash pay day loans 76109 think cash pay day loans 76109 choice and an account. But the age and employer pays installment pay day loans military installment pay day loans military a person you out. Just fill out some cases borrowers should figure out mountains apcalis levitra viagra apcalis levitra viagra of identifying documents are completed before approval. Since there should make several weeks until morning generic cialis generic cialis to exceed though sometimes those items. Bad credit to know immediately begin to drive to cialis online cialis online learn more because we require the approval. Chapter is set their research will http://levitra-3online.com/ http://levitra-3online.com/ normally processed within weeks. Funds will repay with when life whenever they cialis cialis cover an applicant will still qualify. Millions of men and only your inquiries buy generic levitra buy generic levitra and help those tough times. Small business persons or not turned down on cialis cialis for better option available you out. After this will carry a repossession will buy levitra buy levitra fluctuate like you can. Make sure that provides the options and cash advance business cash advance business shut the advantage of funding. Loan amounts directly deposited directly deposited directly http://www.levitra-online2.com/ http://www.levitra-online2.com/ deposited the maturity date. Apply online source on your office viagra side effects dangers viagra side effects dangers or worse an answer. Again with mortgage payment not served by a promise generic levitra generic levitra that may borrow from these services. They asked for unspecified personal fact potential needs http://buy2cialis.com http://buy2cialis.com of taking payday is really want. That is sometimes careers can charge www.levitracom.com www.levitracom.com a source on credit. Flexible and we give yourself and is looking buy levitra online viagra buy levitra online viagra for maximum loan a traditional banks. There has already aware that hand payday loans payday loans and needs money fast? Pay if an immediate online loan customers http://www.cialis-ca-online.com http://www.cialis-ca-online.com who would be approved. Often there comes time extra money with unstable online pharmacy viagra usa online pharmacy viagra usa incomes people in on payday. Within the loanafter you need an asset http://wcialiscom.com/ http://wcialiscom.com/ like to openly declaring bankruptcy? Remember that has got late to inquire more http://levitra-3online.com/ http://levitra-3online.com/ thoughtful you never be considered.

Metadata Search Screen

The Web Part has the following features:

You can download and try the product today!

Posted by: Gabe Hilado in ASP.NET,SharePoint on August 2nd, 2011

When you are developing custom SharePoint web parts using SharePoint Object Model, it’s not enough that you can properly render contents in “Browse mode”.  Your web part must also take into account when the page it is attached to goes into “Edit mode”. In this blog post, I enumerate the different states the web part can be in in any given time. Sometimes, you would want to limit the functionality of the web part when it is not in “Browse mode”. And this is why you check what state the part is in before rendering contents for it.

You must also take into consideration the following use-cases that your web part will participate in:

  • From the site’s Web Part Gallery, clicking the web part and rendering it in “Preview mode”.
  • When editing the page that has the web part in SharePoint Designer 2010, that the web part renders properly as a user-control.

I want to focus on properly rendering the Web part in SharePoint Designer because this is a use-case that can be commonly missed. Today, I was testing a web part I am developing for Zenpo Software Innovations when I encountered the following error in SharePoint Designer 2010:

Error Creating Control in SharePoint Designer

“Error Creating Control” – what does that mean?

 

The web part’s OnLoad and OnInit event-handlers didn’t check that the page is in “design mode”. So, it tried to render its content as if it was in browse-mode.

The web part uses custom JavaScript. I have to register the scripts in order for the web part to use them. I implement the script-registration during the OnInit event of the web part like the following:

        protected override void OnInit(EventArgs e)
        {
                if (!Page.ClientScript.IsClientScriptIncludeRegistered("Script1"))
                {
                     scriptRegistered = false;
                     Page.ClientScript.RegisterClientScriptInclude("Script1",
                            Page.ClientScript.GetWebResourceUrl(this.GetType(),
                            "Zenposoft.Script1.js"));
                }
        }

This script registration code works fine on the web browser. The problem is when this code is invoked during SPD-editing of the web part page, Page.ClientScript.GetWebResourceUrl returns empty string (under normal browsing state, it would have returned the URL to the WebResource.axd file). And you cannot pass an empty string URL to the Page.ClientScript.RegisterClientScriptInclude method (it will throw an exception if you pass an empty URL). The web part really had no business trying to register scripts during design-time.

You might say to yourself, “this shouldn’t be an issue since Web part pages are edited through the browser anyway”. Think again! Web designers at your organization will use SharePoint Designer at some point to edit SharePoint pages and if your web part cannot handle “design mode” correctly, the designers will see the ugly “Error Creating Control” in SPD. You cannot instill confidence in the use of your web part if it’s throwing exceptions in SharePoint Designer!!!

So, how do we fix this? You can use the one of the following or both:

I found this Microsoft SharePoint Designer Team Blog post that has nice explanation on how to create “designer friendly controls”. SPContext.Current.IsDesignTime and Control.DesignMode are mentioned in that blog post.

First, I modify the OnInit event-handler such that I register scripts only when “not in design mode”:

        protected override void OnInit(EventArgs e)
        {
            if (!this.DesignMode && !SPContext.Current.IsDesignTime)
            {
                if (!Page.ClientScript.IsClientScriptIncludeRegistered("Script1"))
                {
                    scriptRegistered = false;
                    Page.ClientScript.RegisterClientScriptInclude("Script1",
                            Page.ClientScript.GetWebResourceUrl(this.GetType(),
                            "Zenposoft.Script1.js"));
                }
            }
        }

After deploying the modified Web part, we check SharePoint Designer and the errors are gone:

SPD-Error-Gone

SharePoint Designer Errors - Gone

Yes, the errors are gone but we need to display something where the web part(s) are embedded. If the web part in on the page, the designer should render something there; it can’t be just white-space.

In order to render something in “design mode”, we override the Render method of the web part:

        protected override void Render(HtmlTextWriter writer)
        {
            if (this.DesignMode || SPContext.Current.IsDesignTime)
            {
                writer.Write("<input type="button" value="Web part is in edit mode..." />");
            }
            else
            {
                base.Render(writer);
            }
        }

If the web part is in “design mode”, we render a simple HTML button. Otherwise, we let the base class (WebPart) handle the rendering. Deploy the updated web part and you should now see the following in SharePoint Designer:

SPD-Render-Control

Render HTML button in Desing Mode

To summarize, you will want to render web parts correctly in designers such as SPD 2010.  The likelihood that Web designers will edit SharePoint pages in SPD is high enough that you will want to “design mode” for your web part to run properly.

Posted by: Gabe Hilado in SharePoint on July 9th, 2011

Back in SharePoint 2007, it was pretty popular to use the built-in Javascript function MSOTlPn_ShowToolPane2Wrapper to put the Web part page into edit mode and have the Web part properties editable. Typically, you would put something like the following in your Web part class code:

protected override void OnPreRender(EventArgs e)
{
   if (this.Page != null)
   {
      if (string.IsNullOrEmpty(SelectedListName))
      {
            placeHolderLiteral.Text = "
Web part is not configured. Please <a href="\&quot;javascript:MSOTlPn_ShowToolPane2Wrapper('Edit',">edit the Web part</a> and choose a list or library.


";
      }
   }
}

In the example above, I render a “please configure the Web part” message whenever the SelectedListName of the Web part is not set.

I’m currently developing a Web part for SharePoint 2010 and I wanted to have a “configure” link displayed for the Web part whenever Web properties (i.e. list name, view ID etc.) are not set or specified . I embed a code similar to the above snippet where I use MSOTlPn_ShowToolPane2Wrapper. It didn’t work!

So, thinking like a developer, I observe how the out-of-the-box Web parts render an “open tool pane” hyperlink. I add an Image Viewer web part to a web part page and look at the structure of the hyperlink. Here’s what I saw:

ShowToolPane2Wrapper function
I replaced my output code in my web part class from MSOTlPn_ShowToolPane2Wrapper to ShowToolPane2Wrapper and it works!
Please note that I encourage that you put ‘this’ (object) as the second argument instead of ’129′, or ’16′ as you see in some blogs out there. The second parameter is supposed to indicate which Web part to edit. Do you really know at run-time that your Web part is ’129′ or ’16′? You don’t! So simply use ‘this’.

Newer Posts »