No, not nescesarily. I don't know what the user is supposed to do in your
application, but if you want to keep the page warm for example to reduce on
on initial compile time you could put a timer on a form and within the timer
routine fire off a webrequest to call the page. Notice that I, the user,
have not physically navigated to the page, I just let the timer do the dirty
work for me - which is actually being performed on another thread by the
way. You can expand from this base however you see fit.
string url = "
https://www.hotmail.com";
Uri ourUri = new Uri(url);
// Create a 'WebRequest' object with the specified url.
WebRequest myWebRequest = WebRequest.Create(url);
// Send the 'WebRequest' and wait for response.
WebResponse myWebResponse = myWebRequest.GetResponse();
// Use "ResponseUri" property to get the actual Uri from where the response
was attained.
if (ourUri.Equals(myWebResponse.ResponseUri))
Console.WriteLine("\nRequest Url : {0} was not redirected",url);
else
Console.WriteLine("\nRequest Url : {0} was redirected to
{1}",url,myWebResponse.ResponseUri);
// Release resources of response object.
myWebResponse.Close();
regards