Uncategorized

A common requirement for a form is to remember its last location. Usually, this information
is stored in the registry. The code that follows shows a helper class that automatically stores
information about a form’s size and position using a key based on the name of a form.
public class FormPositionHelper
{
public static string RegPath = @”SoftwareApp”;
public static void SaveSize(System.Windows.Forms.Form frm)
{
// Create or retrieve a reference to a key where the settings will be stored.
RegistryKey key;
key = Registry.LocalMachine.CreateSubKey(RegPath + frm.Name);
key.SetValue(“Height”, frm.Height);
key.SetValue(“Width”, frm.Width);
key.SetValue(“Left”, frm.Left);
key.SetValue(“Top”, frm.Top);
}

public static void SetSize(System.Windows.Forms.Form frm)
{
RegistryKey key;
key = Registry.LocalMachine.OpenSubKey(RegPath + frm.Name);
if (key != null)
{
frm.Height = (int)key.GetValue(“Height”);
frm.Width = (int)key.GetValue(“Width”);
frm.Left = (int)key.GetValue(“Left”;
frm.Top = (int)key.GetValue(“Top”);
}
}
}
To use this class in a form, you call the SaveSize() method when the form is closing:

private void MyForm_Closing(object sender, System.ComponentModel.CancelEventArgs e)
{
FormPositionHelper.SaveSize(this);
}
and call the SetSize() method when the form is first opened:

private void MyForm_Load(object sender, System.EventArgs e)
{
FormPositionHelper.SetSize(this);
}

Some time developer/coder have to choose appropriate location of windows form on the screen, But limitation comes with the size and resolution of monitor. The solution is used Screen Class which gives right gives you working area of screen of monitor. Then Form load Event will look like this

private void dynamicSizeForm_Load(System.Object sender, System.EventArgse)
{
Screen scr = Screen.PrimaryScreen;
this.Left = (scr.WorkingArea.Width – this.Width) / 2;
this.Top = (scr.WorkingArea.Height – this.Height) / 2;
}
You can use above code to fix the location and size of windows form when it loads

Screen.PrimaryScreen 

Returns a Rectangle structure that represents the bounds
of the display area for the current screen, minus the space
taken for the taskbar and any other docked windows.

Session State is useful for storing values that must be persisted across
multiple pages by the same user. ViewState is useful for storing
serializable data that must be persisisted across PostBacks by a single
page. If you use Session State, the value you insert will remain in memory
until (1) The Session times out, or (2) Your code removes it. If you use
ViewState, the value you insert will remain in ViewState until the user
requests a different page.

ViewState stores data betwen PostBacks by putting it into a hidden form
field on the client HTML doc. when the doc is Posted Back, the values are
read from the hidden form field and stored in memory until the page has
finished processing. If ViewState is particularly large (and I’m talking KBs
here, not 6 bytes), it can negatively affect the speed at which the HTML doc
is downloaded by the browser.

Use the right tool for your job. I think after my explanation, it should be
obvious that you would want to use ViewState in your specific case.

• It should be as short as possible. Don’t sacrifice consistency or obviousness, but be brief.

• Organize and name things logically. ASP.NET isn’t always helpful in keeping a clean structure, so I highly recommend that you use a URL rewriting module. URIs should be ‘hackable’ – see http://www.useit.com/alertbox/990321.html.

• URIs should be deterministic.

  • No two URIs should ever display the same page

  • The same URI should always display the same content.

• The query string should only contain data that AFFECTS THE QUERY. If it doesn’t describe the content, it doesn’t belong.

• The URI path should not rely on cryptic or numerical identifiers. If it does, it should also provide a human-readable title. It’s really nice to be able to look at a URL and guess what it contains – especially when you have a long list of them. As a bonus, search engines absolutely love URIs that match keywords. Tip: Don’t try to spam URLs with keywords. Density algorithms are applied here, also. As with page titles, pick exactly 1 keyword and stick with it.

Further reading (written by Tim Berners-Lee): http://www.w3.org/Provider/Style/URI.

Bad examples:

• /Default.aspx?tabid=3

• /Products/ShowProduct.aspx?prodid=4982

• /showblog.aspx?articleid=98

Better examples:

• /Default.aspx?tabid=3&title=ContactUs

• /Products/ShowProduct.aspx?id=4982&product=Nokia_Wall_Adpater_12V

• /showblog.aspx?articleid=98&title= Why_you_should_never_concatenate_SQL_commands

Best:

• /contact/

• /products/4982_Nokia_Wall_Adapter_12v

• /blog/98_Why_you_should_never_concatenate_SQL_commands

 Reference

http://www.beansoftware.com/ASP.NET-Tutorials/URI-Design.aspx