SELECT * FROM items Where cat_ID = ? Is an Oracle format query not TSQL. How you go about fixing this depends on what database your using. If it's SQL Server, then you'll need to amend the query to use the proper format (named parameters). If it's oracel then you'll need to swap out the datasource for the Oracle equivelent
Freestyle Interactive Ltd Martin on .Net Follow Me on Twitter
You won't be able to access the Repeater3 control from the ascx directly as a new one is created for each databound item. If you handle the OnItemDataBound event on Repeater1 you'll be able to access the Repeater3 control using: e.Item.FindControl("Repeater3")
Freestyle Interactive Ltd Martin on .Net Follow Me on Twitter
Ctrl+K,D by a long shot - sort out that formatting! Then Ctrl, Shift + Esc...why's it taking so long!
If you're not actually storing anything in session, the server won't bother persisting it. So you'll get a different sessionid each time.
With IE, using tables (particularly large wrapping layout tables) can cause an apparent delay with each page load (as IE doesn't render a table until it hits the close tag). If you can live with it, then there's no reason why not in my book.
If you've not sorted this...ScottGu's announced IIS Express. http://weblogs.asp.net/scottgu/archive/2010/06/28/introducing-iis-express.aspx[^] IIS 7 for the masses, should be available shortly.
You can put the NOINDEX meta tag on your page to prevent indexing the content. <META NAME="ROBOTS" CONTENT="NOINDEX"> Without it, I'm afraid Google will be indexing your login page. Returning 301/302 status doesn't really bother google with regards to page rank, a 301 will only prevent google from spidering your original links in future.
Can you open the folder as a website? Open VS: File -> Open -> Web Site
Can you post some simple case code that demonstrates the problem?
Can you use the standard DOM property document.links? http://richardbowles.tripod.com/javascript/section9/lesson9.htm#links[^]
This looks like some whitespace is rendered before the code snippet you've provided. If this is from the Render method of a control, it may be whitespace introduced in the designer.
The best I can suggest is to try using ffmpeg called from within .net (http://www.ffmpeg.org/[^]). It won't be pretty or particularly secure.
Yes there is, but you'll need to investigate the IIS configuration and ASP.Net settings yourself as I don't have time. My experience with this type of thing is extending the request lifetime isn't the best way and is problematic and difficult to debug. As you know, the process just dies with no notification of which timeout barrier caused the problem. I strongly suggest you look at another way to solve this, maybe many smaller requests? If this mechanism needs to reliable you may also want to look at some sort of queuing mechanic (MSMQ). WCF offers nice way's to handle both and it's well worth educating yourself in the technology.
You can create the two requests as you like and then call BeginGetResponse() on each of them (MSDN Reference[^]). This will probably be the easiest way to get what you want without getting entangled with thread pools (and possible starvation).
Sessions are usually based on cookies and it would be upto the browser as to whether tabs can share cookies or they are persited after the browser is cleared (provided you've set an expiry date). A new session is created when a valid session cookie isn't found by ASP.Net.
What happens if you add an 'onclick' attribute to your button as set is equal to window.close(); Seems a bit unnecssary to require a postback to the server for this.
It sounds like the request is being killed for taking too long. ASP.Net will kill long running requests after a set amount of time ~20 minutes I think. But if your process takes that long maybe a webservice isn't the place to do the work. Is there any scope for you to do the work in say a windows service? Otherwise, I think we'll need a bit more information about what you're trying to achieve so we can suggest a better way - what you're doing now just looks wrong.