| Thread | Last Post | Replies |
|
| WaitHandles must be less than or equal to 64 - missing documentation | 28 Dec 2006 21:43 GMT | 10 |
Calling WaitAll with array of 64 or more causes exception
WaitHandle.WaitAll(whaWaitHandlesArray);
System.NotSupportedException: The number of WaitHandles must be less
than or equal to 64.
|
| How do OS loads CLR | 13 Dec 2006 17:20 GMT | 9 |
I want to know how do OS differentiate an exe created by Visual Studio
6.0 or Visual Studio .Net ?? And if multipule versions of CLR are
there, how do it loads the required version.
Thanks in adv
|
| SuppressUnmanagedCodeSecurity doesn't work on value types | 13 Dec 2006 14:26 GMT | 1 |
Anybody specific reason why this is? There doesn't seem to be a
legitimate reason why this would be.
|
| Explicit casting | 11 Dec 2006 18:13 GMT | 4 |
Is it only a best practice to use "AS" or "IS" or are there any performance
benefits to using these over explicit casting?
Thanks for your clarifications!
|
| Good source | 08 Dec 2006 16:42 GMT | 2 |
What's good source that I can read about " "Controls" ,usage and designing?
Thanks.
=========================
|
| Is neglecting Dispose in this case acceptable? | 07 Dec 2006 21:46 GMT | 3 |
I have a persistence class with one dababase connection and no other member
objects that need management. For reasons that are not necessary to go
into, I'd rather not implement Dispose in this class. If I implement a
finalizer, and close my database connection there, I see ...
|
| outofmemoryexception | 05 Dec 2006 23:03 GMT | 5 |
hi, i have an exe that holds a very large Dictionary collection that would
takes about 2.5G in total. the machine has 4G RAM.
if i load the entire collection within an EXE, i would get
outofmemoryexception when it uses up to about 1.5G RAM. however, if i split
|
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage
Start New Thread