If Im not using the SQL Membership I usually call a helper class that has a few methods just for this.
start here passing credentials:
protected static bool LoginUser(string user, string pass)
{
Logger l = new Logger();
return l.IsUser(user.Trim(), pass.Trim());
}
The IsUser Class:
/// <summary>
/// Check to see if user is legal
/// </summary>
/// <param name="user">User name </param>
/// <param name="pass">User password </param>
/// <returns>True if is a user</returns>
public bool IsUser(string user, string pass)
{
using (SqlConnection conn = new SqlConnection(ConfigurationManager.ConnectionStrings["conn"].ConnectionString))
{
bool b;
//// Send info to DB and see if I get a record
SqlCommand cmd = new SqlCommand("sproc", conn);
cmd.CommandType = CommandType.StoredProcedure;
cmd.Parameters.AddWithValue("@user", user);
cmd.Parameters.AddWithValue("@pass", pass);
SqlParameter isAUser = cmd.Parameters.Add("@IsUser", SqlDbType.Char, 3);
isAUser.Direction = ParameterDirection.Output;
conn.Open();
b = Convert.ToBoolean(cmd.ExecuteScalar().ToString());
if (b)
{
string u = Convert.ToString(isAUser.Value);
HttpContext.Current.Session["UserID"] = u;
b = true;
}
else
{
b = false;
}
conn.Close();
return b;
}
}
The bool value will be used to validate if user credentials are valid.
Nothing wrong with classic ASP. I have many sites that I maintain that are still running ASP. And they work just as good as anything new. The only issue I have is the time needed for some of the reporting sites, but this only on the larger ones.
Generally, if its part of the page or menu structure then put it in the CSS, using the background-image property.
If its part of the content, then in the markup. That way you can make sure the Alt tag is filled out properly and an individual that's using an AT (Assistive Technology) device can understand what the image is about.
Some code snips to get you going, and it includes sorting to. I'm creating a DataSet for the initial load but then creating a DataTable and storing it in ViewState for the paging. You could also, for efficiency, call only the page that is going to be shown, but thats a different solution. As long as your not pulling thousands of records you should be ok.
Only time you should redirect to a login page is if the user clicks a link to go there, or they've bookmarked a page that requires them to be authenticated. If they're just viewing public pages, then there is no reason to have a user login.
Another thing to watch out for is HttpValueCollection Key size. This is how many data elements are allowed on a page. Out of the box its around 1000, which is a decrease from framwwork 1.0. MS decreased it to prevent DoS attacks. On large gridviews this is easily exceeded, so to increase the number of keys allowable add this to the web.config:
stultuske, if I can make a web site show or do something that the programmer did not intend for me to see or do ... thats "Hacking". And through that you can attemplt some "Social Hacking". And there is source and generated source. Copying a generated source and modifying it has potential on any website.
protected void btnExport_Click(object sender, EventArgs e)
{
Response.Clear();
Response.AddHeader("content-disposition", "attachment;filename=FileName.xls");
Response.Charset = string.Empty;
// If you want the option to open the Excel file without saving then
// comment out the line below
// Response.Cache.SetCacheability(HttpCacheability.NoCache);
Response.ContentType = "application/vnd.xls";
System.IO.StringWriter stringWrite = new System.IO.StringWriter();
HtmlTextWriter htmlWrite = new HtmlTextWriter(stringWrite);
gridView.RenderControl(htmlWrite);
Response.Write(stringWrite.ToString());
Response.End();
}
If I'm reading you correctly, you want to be able to turn a group of links on and off from an admin page. To do so you would need a way to store the information, wheather they are visible or not and then be able to read that information on the page they are on.
An easy way is to handle this is to read and write to a simple text file. Not very secure, but it works well and is easy to implement.
Well ... you could view source and change hidden and/or disabled fields to visible and/or enabled. This in turn would allow you to post or get form information that would otherwise be unavailable.
This is always a problem with tabular data on a phone or tablet ... just not enough room for a big table.
What you could do is have a seperate table that is only shown, after the other is hidden, using media queries.
Another option is to check for a phone or tablets user agent and dynamically change the number of rows shown. Only issue with that is the User Agents for some of the higher end phones are becoming indistinguishable from a desktops.
If the site is using a CMS and as long as the site is not presenting presentation elements in its code, any framework will do. Its simply a wrapper for your content. But like tomparker said ... "converting an ecommerce site of this magnitude to mobile is big undertaking".
If they kept a seperation of content and presentation it should be fairly cut and dried ... should be anyway. :-)
Like JorgeM said, reasearch on your own first. Sites like this are to help other programmers. They're not a collection of free programmers to get work from.
