Indeed, Basic 1

Doesn't work. End of story.

You could probably write an AddOn that parses the CSS and tries to modify the chrome it displays, but I doubt that would work (in case it would, someone would have done it already).

It works the same as for any other Website. Maybe google a bit for what you are trying to do (like, POST some form fields in C#) or look at RFC 2616 and related.

You dont need to take care of cookies yourself, the Cookie Container does that for your; just make sure to include the same container for all requests. Just call GetRequestStream() on the Request object, and use whatever method you like to write to it (StreamWriter for example). Then, simply close t...

You need to use a different url to log in, store the cookie, and then submit your answer. The cookie container is correct for the latter, but you still need to go to login first. And you'll need to write your HTTP to the request stream you obtain from the HttpWebRequest object before getting the res...

It does draw the graphics, but this is not the correct way to achieve permanent stuff. The control will redraw itself after some time, which will delete your rectangle. Attach that painting to c.Paint (or, if you have your own class derived from Control, override the OnPaint method) to get it perman...

I suppose you are talking about self-modifying code? I don't think this is possible in managed languages like Java, since you don't have access to the lower levels where the VM actually runs your code. Even if you did, I could imagine it will block such attempts. And you usually dont need the JDK (D...

The try/catch approach to this problem is very slow, and might yield false positives. A lot of operations on the .Net Framework follow the asynchronous pattern, and provide either BeginXxx/EndXxx methods, or a related XxxAsync method that runs in background. Keep a (thread-safe) storage that knows a...

Yes, you can. Infact, you might have to for cases like my a/b example.
You only put them into header files to have better separation, and allow stuff to be distributed as sort-of API (you know the functions, but you dont have to know the code).

Those forward declarations (also called prototypes) only define how the function is going to look like. While compiling, the compiler of choice does a top-down parse and throws if it doesnt know functions: void a() { b(); } //will fail, b is not known void b() { a(); } //a was defined before b, so y...