OT-OK Todd (and any body else who has a good answer)...

Post #205,947 by jb4 5/4/05 7:03:55 PM Reply	OT-OK Todd (and any body else who has a good answer)... Exactly (and I mean exactly, using standard English and not some Marketing-speak) what is "managed code"? Not being an MS drone (and having happily escaped the .NET ~~revulsion~~revolution), I haven't drunk the Kool-Aid, and haven't therefore added this euphemism to my vocabulary yet. Nonetheless, I do find that I need to know what it means (esp. because somebody I respect used it in the parent to this posting). So, to paraphrase..."Whachewtalkingbout, Willis?" jb4 shrub\ufffdbish (Am., from shrub* + rubbish, after the derisive name for America's 43 president; 2003) n. 1. a form of nonsensical political doubletalk wherein the speaker attempts to defend the indefensible by lying, obfuscation, or otherwise misstating the facts; GIBBERISH. 2. any of a collection of utterances from America's putative 43rd president. cf.* BULLSHIT
Post #205,949 by ChrisR 5/4/05 7:15:11 PM Reply	Probably not a good answer...but... ...unmanaged code is capable of accessing any system resource with no type constraints (i.e. you can cast any kind to and kind). Managed code just means you are playing in the sandbox, similar to the JVM. Best correlary in the Java world is JNI, but in the case of .net you can basically write native code that still runs within the .net virtual machine. Certain ILM instructions are only available in unmanaged states (i.e. buffer overrun this machine).
Post #205,958 by tuberculosis 5/4/05 8:17:09 PM Reply	That's a pretty good answer IOW, in "managed code" its not possible to do things like manipulate arbitrary memory in the machine - a behavior relied upon by things like some viruses and worms. C# has no pointer construct and so you are playing in "the sandbox" as Chris said. You can't hurt anything from there and your code is subject to user defined security policies. Unmanaged code is like C/C++. You can do anything to any byte in the machine. No safety rails, no sandbox, no second chances. "Whenever you find you are on the side of the majority, it is time to pause and reflect" --Mark Twain "The significant problems we face cannot be solved at the same level of thinking we were at when we created them." --Albert Einstein "This is still a dangerous world. It's a world of madmen and uncertainty and potential mental losses." --George W. Bush
Post #206,086 by jb4 5/5/05 11:35:07 AM Reply	Any byte in the machine, or... ...any byte in your process's address space? (I assume that my process cannot touch your process's stuff...) jb4 shrub\ufffdbish (Am., from shrub* + rubbish, after the derisive name for America's 43 president; 2003) n. 1. a form of nonsensical political doubletalk wherein the speaker attempts to defend the indefensible by lying, obfuscation, or otherwise misstating the facts; GIBBERISH. 2. any of a collection of utterances from America's putative 43rd president. cf.* BULLSHIT
Post #206,089 by ChrisR 5/5/05 11:52:30 AM Reply	As much protection as the Operating System provides... ...which for Windows is to say None At All. Unmanaged code is the umbrella of native code that's not managed within the sandbox. All those VBX or COM or COM+ or DCOM things can be invoked within the unmanaged state.

Welcome to IWETHEY!