Is there a problem using different MASM binaries ?, Using non-standart components in the masm32\bin directory

Is there any problem in modifying the masm32\bin directory components?

I have installed Masm32 9.0.

But now i am using new versions of ml.exe, link.exe, and rc.exe along with its necessary files. First i had some problems when assembling with windows.inc and i commented that line(a single line) which caused me problems and after that there was no problem and apps created runs fine on my two windows(SP2 with Dotnet Framework 2 and SP2 with Framework 1).

I haven't checked it on other computers. The line that i commented is this and i used default assembling options of WinAsm Studio.

Now my ml.exe is of version 8.00.50727.104(Microsoft's site) or 7.10.3077(From VS2003)
and link.exe is of 7.10.3077(from VS 2003) or 8.00.50727.42(From VB2005 Express Edition); Both works
and rc.exe 5.2.3668.0(From VS 2003)

will it cause me any problems in future ?????.

Will these new ml.exe and link.exe create any dot net codes in my app.

I will attached some apps created using new ml.exe and link.exe.

__Lahar__

Attached File ( Number of downloads: 9 )
 test_app.zip

Don't be afraid about .NET code inserted by MASM v8.0.

However, better try to say good-bye to the "newer is always better"-attitude, which you might have. The more professional approach is: "never change a running system", that is, don't change your tools unless you have good reasons to do so.

AFAIK MASM v8.0 causes some troubles, v6.15 and v7.0 are preferable.

Great points japheth.

Lahar had me wondering about this topic.

Like your point about changes to what works, I haven't changed anything to the original MASM32 install. Although I did get newer versions of ML and NMAKE from Iczelion's site, and set them aside just in case the need arises.

Thanks for these posts fellas. ;)

Lahar,

I would recommend using the MASM32 package as its integrity.

The reason behind this, is that that the package is tested by many users for any incompatibilities of the sort you mentioned, before it gets to be released to the public.

If you want to use different binaries, it's ok, as long as they behave _exactly_ as the old ones.
Modifying headers in order to get binaries to work, IS NOT A GOOD IDEA.

Imagine that: You just downloaded a cool project that makes use of any of the modified / removed members of the header.
What will you get instead of that cool project ?

Answer: HEADACHE & FRUSTRATION !

Also, what happens in the case that you need to use the removed members of the header? Drop the project ?

In conclusion, if the new binaries don't behave exactly like the old ones, avoid using them.
Even if they seem to behave the same, just in case, before you actually replace the old ones, save a backup of the original MASM installation folder.

Also, as Japheth pointed out, the ml.exe will not inline/inject .IL to your project, in any case.
In addition, i don't think that the MASM binaries have any dependency whatsoever on any version of the DotNet framework.