I’ll be one of the first to admit, Javascript is NOT my strong point.. or my favorite.. C# however is, so I amended the ASCX page to use C# throughout.<\/p>\n
2 ASP controls for the Image and text box both of which have a click event “cmdRunSearch_Click”<\/p>\n
This calls:-<\/p>\n
\r\nprotected void cmdRunSearch_Click(object sender, EventArgs e)\r\n {\r\n\tstring strEncodedUrl\r\n\t\t= SPEncode.UrlEncodeAsUrl(\"http:\/\/demosearch\/results.aspx\",false);\r\n\r\n\r\n string targetUrl = strEncodedUrl + \"?k=\" + txtSearchText.Text;\r\n \r\n Response.Redirect(targetUrl); \r\n }<\/pre>\nA little bit of styling on the asp objects and the new control adapter looks the part and performs well.<\/p>\n
The only downside to this approach is that the ascx page has to be edited manually after the feature is installed to ensure the correct URL is used for the SSE implementation.<\/p>\n
To take this further, I’m tempted to restore the scope activities that I took out of the original MS page, however this time we need to pull the scope options from the search centre, so this may need some thought.<\/p>\n
Reg.<\/p>\n","protected":false},"excerpt":{"rendered":"
I’ll be one of the first to admit, Javascript is NOT my strong point.. or my favorite.. C# however is, so I amended the ASCX page to use C# throughout. 2 ASP controls for the Image and text box both of which have a click event “cmdRunSearch_Click” This calls:- protected void cmdRunSearch_Click(object sender, EventArgs e) … <\/p>\n