|
Hi all. This is a bit of a weird question, but I actually need to determine what assembly a delegate's definition resides in. That is, if an instance of a delegate is passed-into my class, I need to determine where the code that that delegate represents comes from.
Any thoughts?
“Time and space can be a bitch.”
–Gushie, Quantum Leap
{o,o}.oO( Looking for a great RSS reader? Try FeedBeast! )
|)””’) Built with home-grown CodeProject components!
-”-”-
|
|
|
|
|
Ah, looks like I can do it with:
theDelegate.Method.Module.Assembly;
That wasn't so hard as I was expecting. 
“Time and space can be a bitch.”
–Gushie, Quantum Leap
{o,o}.oO( Looking for a great RSS reader? Try FeedBeast! )
|)””’) Built with home-grown CodeProject components!
-”-”-
|
|
|
|
|
|
Hi there.
I want to send and get a web request by C# (get and post)
Which classes do we need to use ?
Thanks an advance.
|
|
|
|
|
|
logan1337 wrote: System.Net.HttpWebRequest, though it may be obsolete now
No, it's not obsolete, but the WebClient class has been added which contains methods that wraps common uses of the WebRequest classes.
Despite everything, the person most likely to be fooling you next is yourself.
|
|
|
|
|
You can use Request.QueryString() and Request.Form() to get things from get and post (use the overloads to get specific things).
I'm unsure of the namespace that the Request object is in. I believe that you should be able to use it in a web project without adding any references, but I may be wrong.
|
|
|
|
|
The WebClient class contains convenient methods to do web requests. If you need more advanced aspects, like controling the timeout, you need to use the HttpWebRequest class directly.
Despite everything, the person most likely to be fooling you next is yourself.
|
|
|
|
|
Yes HttpWebrequest is the chose one. It has got all the function a programmer may need. From SSL requests to the regular http form posts.
|
|
|
|
|
Hi,
What does it mean when you have:
<br />
for ( ;; ) {
Is it an infinite loop?
Cheers,
Mark Brock
"We're definitely not going to make a G or a PG version of this. It's not PillowfightCraft." -- Chris Metzen
Click here to view my blog
|
|
|
|
|
|
Because you have to wait forever to tell for certain if a loop is infinite: he hasn't got the time.
Steve
|
|
|
|
|
|
That gets a +5 from me :P
|
|
|
|
|
Stephen Hewitt wrote: Because you have to wait forever to tell for certain if a loop is infinite: he hasn't got the time.
Consider that an eternity for the computer is a short time for a human. 1 000 000 000 000 000 iterations would only take a week or so... 
Despite everything, the person most likely to be fooling you next is yourself.
|
|
|
|
|
MarkBrock wrote: Is it an infinite loop?
Yes.
It equals with :
while (true) { ... }
|
|
|
|
|
It is infinite loop. But I would not do that if I where you, I would probably use Threading.Sleep if the purpose is to wait for an event to happen. infinite loop keeps utilize a lot of cpu...
|
|
|
|
|
Infinite loops are legitimate for certain things, especially when implementing threads and stuff that need to continuously run and wait (i.e. actually block, thus not using the cpu) for things.
Personally I prefer while ( true ) because it's more obvious what it is.
“Time and space can be a bitch.”
–Gushie, Quantum Leap
{o,o}.oO( Looking for a great RSS reader? Try FeedBeast! )
|)””’) Built with home-grown CodeProject components!
-”-”-
|
|
|
|
|
for ( ;; ) is the recommended way to do an infinite loop.
Steve
|
|
|
|
|
Is there a reason that is so?
“Time and space can be a bitch.”
–Gushie, Quantum Leap
{o,o}.oO( Looking for a great RSS reader? Try FeedBeast! )
|)””’) Built with home-grown CodeProject components!
-”-”-
|
|
|
|
|
When you maximize warnings the "while(true)" is correctly flagged as using a constant in a conditional expression.
Anyone who thinks he has a better idea of what's good for people than people do is a swine.
- P.J. O'Rourke
|
|
|
|
|
Well aside from this (which as I see it is just a problem with the warning that it doesn't make an exception for obviously intentional infinite loops), there's no functional difference so I can't see why one is "recommended" over the other.
Nevertheless, do what you will, I'm only saying I like it better because it's more readable.
“Time and space can be a bitch.”
–Gushie, Quantum Leap
{o,o}.oO( Looking for a great RSS reader? Try FeedBeast! )
|)””’) Built with home-grown CodeProject components!
-”-”-
|
|
|
|
|
From a code generation perspective there is no difference. But there are many constructs which have no functional difference, but which generate warnings because they are prone to error.
Anyone who thinks he has a better idea of what's good for people than people do is a swine.
- P.J. O'Rourke
|
|
|
|
|
why not while(1)? (or while(true))
Is there a difference?
Mark Brock
"We're definitely not going to make a G or a PG version of this. It's not PillowfightCraft." -- Chris Metzen
Click here to view my blog
|
|
|
|
|
You'd like to think the compiler is smart enough to produce optimal code in any of these cases, but I haven't verified this in C#. Nevertheless, for ( ; ; ) is the preferred way to express an infinite loop.
Steve
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
