Yes.

Better is a relative term. If "better" == "safer", then new byte[requiredSize] is better. If "better" == "faster", then you'll get better performance by P/Invoking HeapAlloc or similar. The problem with this approach is that the memory is unmanaged by the CLR so it can't track it. You could marshal it to an IntPtr and use that in managed code, but the buffer is still allocated on the unmanaged heap (or stack if you used something like _alloca). You'll have to free it explicitly. This is where wrapping such functions in a class following the disposable pattern is handle, and .NET 2.0 will introduce the SafeHandle for just such a purpose. You can either define your own now, or take a look at the GCHandle and HandleRef structs under System.Runtime.InteropServices which may be helpful depending on how you're using the memory (especially if you need to marshal managed types to native memory). There is yet another way, though. Read about C#'s stackalloc operator keyword. This, of course, will alloc memory on the heap and give you an unsafe (i.e., has access to direct memory and is not GC'd) pointer. HTH This posting is provided "AS IS" with no warranties, and confers no rights. Software Design Engineer Developer Division Sustained Engineering Microsoft [My Articles] [My Blog]

Thanks a LOT!!:):rose:

Honestly, there's no reason an exception should be thrown to the message pump. Following the doctrine of "never trusting user input", all input should be validated prior to doing anything with it. In any case, Application.ThreadException should typically do the trick. Even the event documentations states about what I said above, though. Always validate user input as close to the input as possible (i.e., the presentation layer or in methods and property set accessors that can be called by outside code). Microsoft MVP, Visual C# My Articles

Well, as I said, I do get SSL to work, but the SSL settings are deleted when the virtual directories are read from ESM when restarting the services, so I need to enter them there instead of in IISAdmin. I have several ips on the Exchange server to enable two companies to use the same one with different public folders and only port 443. Thank you for your exchaustive answer though.:rose:

Doesn't really matter if you don't agree with me - it's documented in the .NET Framework SDK. I suppose, then, that you disagree with Microsoft. I didn't say that ignoring the AsyncResults doesn't incur a certain performance hit with memory consumption, I said it didn't incur any memory leaks. There is a difference. The very fact that the GC was able to collect the unused references proves that the objects where indeed tracked. The GC would've collected them eventually. Memory leaks are when memory is lost and unreferenced, so it cannot be freed again, like when a variable references an alloc'd region of memory which is not freed. Once that variable goes out of scope it's practically impossible to free that memory again. The fact remains that calling methods or setting properties (often getting as well) on controls from a different thread may cause problems. This is what's documented well in the .NET Framework if you read the right topics. Sometimes things may work. Other times they may not. Often times it is certain functionality that doesn't work as expected. It call comes down to the synchronization of threads, like it or not. Microsoft MVP, Visual C# My Articles

My pleasure. :) I've read the article a couple of times now, and still don't think that I've managed to stay coherent all the way through. :wtf: There is a lot of stuff there. --Jesse

Heath Stewart wrote: If you don't want VS.NET doing things for you Being able to disable this behaviour would be nice... ;p top secret

There is nothing to enable. You should be able to double click a stored proc and have it open, or right click a table ans select design table. If you don't have these then there is probably something wrong with your installation.

Hugo Hallman wrote: Is a hamster closely related to a hoarder? Does a hamster hoard? It seems you are not that far off. Have a look at: http://lexikon.nada.kth.se/cgi-bin/sve-eng Select en->sv and enter "hoard" and they do list hamsters. Going from that to calling them hoarders might be a stretch, but I don't really know. So, when I say hamster, do you think of hoarding? No. I think of a rather cute little rodent that's short-sighted, dumber than a horse and often tries to excape to roam the place one's living behind anything there is to hide behind. Like mice they love walls (might be their way to get out of labyrinths), though they're more like rabbits and ferrets when it comes to the love of "Oh so lovely plastic and yummy rubber cables" that just happens to carry mains power. :-) Oh, and I do, like Roger, tend to think of them more in terms of "packrat".

Trollslayer wrote: Do you think they would get on with my teddybear ? Well, mine are really macho, I'd hate to see a fight ;P $500 for a penny people, cheap at the price, just 500 big ones for a penny! Don't shove, there's enough pennies for everyone! - Daffy Duck, manning a wishing well

Sign in at the top left part of the web page. -Steven "the yellow dart" Hicks CPA CodeProjectAddict Actual Linux Penguins were harmed in the creation of this message. More tutorials: Ltpb.8m.com: Tutorials |404Browser.com (Download Link)

thanks a lot. I didn't know of autoexp.dat, but have always suspected something like it. Thank you very much for telling me of it. (Thought it was built into vstudio. -darn M$)

Remember to define both UNICODE and _UNICODE - Anders Money talks, but all mine ever says is "Goodbye!"