Originally posted by sail3005
is MS making the unsupported Win95 version.
Yes, the Win98 version can be installed on Win95 but it will not be supported on that platform.
Originally posted by BrianHawley
I don't entirely buy this "decompile back to source code" argument - although I agree it's worth further investigation.

Right now there are tools that will 'decompile' almost anything (including VB) back to assembler. What you get is miles and miles of undocumented code that it is almost impossible to recompile back into the original - never mind modify it.

Are we talking about something similar here?

Joacim, how is it done? Do you have any good links?

Certainly I would like to have a go at any of my commercial applications to see if this is a security issue.
You will be able to decompile or disassemble a .Net assembly.
The disassembly program I used to produce the above posted code is ildasm.exe and that is included in the .Net Software Development Kit.
The advantage you'll get with the ability to disassemble an assembly is that you can debug compiled code.
Many commersial component developers have been pressuring Microsoft to come up with some sort of obfuscator tool that can scramble data to make it harder to figure out what a particular assembly is doing.
I beleive that such a tool will be provided, if not from Microsoft from some third-party.
But this problem isn't unique to .Net - other virtual machine-based platforms (read Java) suffer the same problem.

Best regards