I found a workaround which I generally use.

1. Create 2 variables from dates. I’m converting both dates to US format and then to a number with year, month and date sequence to ensure correctness.

<xsl:variable name="ExpiryDate1" select="number(ddwrt:FormatDateTime(string(@ExpirationDate), 1033, ‘yyyyMMdd’))"/>

<xsl:variable name="OtherDate2" select="number(ddwrt:FormatDateTime(string(@OtherDate), 1033, ‘yyyyMMdd’))"/>

2. Compare them to find out which one is greater

<xsl:choose>
<xsl:when test=’ExpirationDate-OtherDate >= 0′>

   // Do Something
</xsl:when>
<xsl:otherwise> 

  // Do Something

</xsl:otherwise>
</xsl:choose>

I don’t claim that this the best solution I have got, while it works very well. If you know anything better, please share!

Setting disable-output-escaping="no" doesn’t work in this case, because then it displays the HTML coding for the link (‘a’ tag).

The easiest solution to get rid of ‘A’ tag is to remove it completely using sub-string function.

For example if you are showing a column named “Category”, in this case you can replace

<xsl:value-of select="@Category" disable-output-escaping="yes"/>

with

<xsl:value-of select="substring-before(substring-after(@Category, ‘&gt;’), ‘&lt;’)" disable-output-escaping="yes"/>

You must be looking for a control which will allow you to create formatted text as shown in below given image.

InputFormTextBox is the correct control you will ever need. This is available under Microsoft.SharePoint.WebControls namespace. (Only MOSS 2007)

How to use it? Very simple.

InputFormTextBox richMessage = new InputFormTextBox();
richMessage.RichText = true;
richMessage.RichTextMode = SPRichTextMode.FullHtml;

You may also use following useful properties:

richMessage.AllowHyperlink = true;
richMessage.TextMode = TextBoxMode.MultiLine;
richMessage.Wrap = true;
richMessage.Rows = 10;
richMessage.Width = System.Web.UI.WebControls.Unit.Percentage(100);

Check another thread for known issues with InputFormTextBox Control.
InputFormTextBox width, Enabled, ReadOnly Properties not working properly



If you found this post helpful then please share it.

This exception is thrown when you are trying to delete items of a collection in a for loop or using a for each loop.

The ideal solution could be to use a for loop with a descending counter.

Problem:

for e.g.

If suppose you are executing any of following code snippets

1.

for (int listcounter = 0; listcounter < ReferenceOwnersList.Items.Count; listcounter++)
{
ReferenceOwnersList.Items.Delete(0);
}

2.

foreach (SPListItem Li in ReferenceOwnersList.Items)
{
Li.Delete();
}

Here ReferenceOwnersList is a collection.

Now whenever this code will execute for the first time, the number of items reduce. So the second item gets the first index.
I tried deleting 0th item everytime but still I got the exception. Again changing index may cause skipping the items in most senerios.

And the collection throws the “Collection was modified; enumeration operation may not execute” exception.

Solution:

Solution
Use a reducing for loop.

for (int cntLi = ReferenceOwnersList.Items.Count – 1; cntLi >=0 ;cntLi — )
{
ReferenceOwnersList.Items.Delete(cntLi);
}

so that even if the last item is deleted, the index of other items wont change.

I’m Jay. Welcome to my blog. I have created this blog to share my experiences while working on different technologies.

The theme for this blog is “Coding for future”.

Coding for future is all about reducing the time required for software development.

The ways I have figured out is;

Building reusable code, and making it public!

Though practically exposing code could be harmful to some organizations, programmers can sharing technical issues faced and their solutions!

I believe if 80% of the issues and solutions are shared then we will see a rapid application development and we will soon be building more complex solutions that world is actually going to see may be 50 years later.

This is “coding for future” all about!.