Search results matching tag 'asp.net'

cryptographic failure while signing assembly

Steve — Wed, 26 Aug 2009 13:13:00 GMT

The problem is that you cannot delete a key and you cannot add the key as you do not have access to the key to delete it and the .NET framework cannot add it because of constraints on the StrongName data store.

The solution is to give yourself access to C:\Documents and Settings\AllUsers\ApplicationData\Microsoft\Crypto\RSA\MachineKeys\

Browse to c:\Documents and Settings\AllUsers\ApplicationData\Microsoft\Crypto\RSA\MachineKeys

Grant rights to Adminstrators, or whatever group you are in

Take Ownership of this folder (click Advanced under Security, and then click the Ownership tab at the top)

This worked all fine for me see how you get along.

c# how to sort an ArrayList alphabetically

Steve — Thu, 03 Jul 2008 09:28:00 GMT

With an ArrayList populated with strings we all know this is easy you call just the ArrayList.Sort() method.

However if you have objects within your ArrayList then its a different matter as when you sort you get the following error message (At least one object must implement IComparable)

To get round this issue what you need to do is implement IComparable and create an IComparable.CompareTo function within the class thats implementing it.

an example is included below which should clarify.

using System;
using System.Collections;

namespace StevesArrayListSorting
{

public partial class createtest : System.Web.UI.Page
{

protected void Page_Load(object sender, EventArgs e)
{

  // add 3 objects in non alphabetical order
            ArrayList al = new ArrayList();
            StevesCustomObject obj1 = new StevesCustomObject();
            obj1.CustomObjectName = "Alpha";
            obj1.CustomObjectID = "1";
            obj1.CustomObjectRefNo = 1;
            al.Add(obj1);

            StevesCustomObject obj2 = new StevesCustomObject();
            obj2.CustomObjectName = "Charlie";
            obj2.CustomObjectID = "1";
            obj2.CustomObjectRefNo = 2;
            al.Add(obj2);

Response.Write("</br></br>");

            StevesCustomObject obj3 = new StevesCustomObject();
            obj3.CustomObjectName = "Bravo";
            obj3.CustomObjectID = "1";
            obj3.CustomObjectRefNo = 5;
            al.Add(obj3);

            // Write out unsorted object names
            foreach (StevesCustomObject Cobj in al)
            {
                Response.Write(Cobj.CustomObjectName + "</br>");
            }

al.Sort();

            // Write out sorted object names
            foreach (StevesCustomObject Cobj in al)
            {
                Response.Write(Cobj.CustomObjectName + "</br>");
            }

}
public class StevesCustomObject : IComparable
        {
            public string CustomObjectName;
            public string CustomObjectID;
            public int CustomObjectRefNo;

            public int CompareTo(object obj)
            {
                StevesCustomObject Compare = (StevesCustomObject)obj;
                int result = this.CustomObjectName.CompareTo(Compare.CustomObjectName);
                if (result == 0)
                    result = this.CustomObjectName.CompareTo(Compare.CustomObjectName);
                return result;
            }
        }
}
}

The reponse should be

Alpha

Charlie

Bravo

Alpha

Bravo

Charlie

In this example I sorted alpabetically but you expand your IComparer class to cover other values, alphabetically seems to be the most requested though.

Hope this helps somebody.

A potentially dangerous Request.Form value was detected

Steve — Tue, 05 Feb 2008 21:12:00 GMT

This issue is caused by a form element within your page posting back what it believes to be HTML code. The text does not need to be a full HTML statement, but anything with open and close brackets (<>).

This is actually a fantastic error because it is an inbuilt security device offered by Asp.Net to stop users injecting HTML code or Script code into your application.

You have two ways to get around this problem remove the validation request from either the page in question or the entire project(not recommended at all).

To remove from a page you need to edit the page directive(top line in your aspx page) and add the following code into that line ValidateRequest="false"

For a global removal you need to add

into your web.config. This needs to go into the <system.web> section. This to confirm again will turn off request validation for every page within your application.

Steve.