Comments on: MASM Assembly in Visual Studio 2010

By: Wang

Wang — Fri, 21 Sep 2012 13:47:11 +0000

How it works in visual studio 2012 ？
It seems this way does not work in visual studio 2012.

By: Tim

Tim — Tue, 29 May 2012 04:28:50 +0000

All I get is this error on compile. My dummy test file was called texst66.asm

Tried several simple MASM sources that work fine under QEditor that comes with MASM. Every single one gives this line. Looked up Error 1- and the MSB3721- but not much out there- some CUDA devs using VS2010 for MASM-

any thoughts ?

Nice tutorial though, just didn’t work for me.

With VS2010

Error 1 error MSB3721: The command “ml.exe /c /Zi /Fo”Debug\texst66.obj” /W3 /errorReport:prompt /Tatexst66.asm” exited with code 1. C:\Program Files\MSBuild\Microsoft.Cpp\v4.0\BuildCustomizations\masm.targets 49 6 test1

By: xcrypt

xcrypt — Mon, 14 May 2012 17:07:37 +0000

Nvm, the problem I was having was solved by D-side’s comment

By: xcrypt

xcrypt — Mon, 14 May 2012 16:07:53 +0000

Very helpful tutorial, but I’m still getting a few errors:

CODE:

.586
.model flat, stdcall
option casemap :none

; To get unicode support
include \masm32\macros\ucmacros.asm

include \masm32\include\windows.inc

include \masm32\include\kernel32.inc
includelib \masm32\lib\kernel32.lib

include \masm32\include\user32.inc
includelib \masm32\lib\user32.lib

.data

; WSTR gets you a unicode string definition
WSTR wstrTitle, “Hello”
WSTR wstrMessage, “World”

.code

main:
invoke MessageBoxW, NULL, ADDR wstrMessage, ADDR wstrTitle, MB_OK
invoke ExitProcess, eax
end main

DEBUG INFO:

1>_MASM:
1> Assembling [Inputs]…
1>test.asm(19): error A2008: syntax error : WSTR
1>test.asm(20): error A2008: syntax error : WSTR
1>test.asm(25): error A2006: undefined symbol : wstrTitle
1>test.asm(25): error A2114: INVOKE argument type mismatch : argument : 3
1>test.asm(25): error A2006: undefined symbol : wstrMessage
1>test.asm(25): error A2114: INVOKE argument type mismatch : argument : 2
1>\masm32\macros\ucmacros.asm(13): error A2052: forced error
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\BuildCustomizations\masm.targets(49,5): error MSB3721: The command “ml.exe /c /nologo /Zi /Fo”Debug\test.obj” /W3 /errorReport:prompt /Tatest.asm” exited with code 1.
1>
1>Build FAILED.

I’m also wondering where these \masm32 includes come from, I can’t seem to find any directory on my computer like that?

Thanks in advance

By: Duncan

Duncan — Fri, 27 Apr 2012 08:09:51 +0000

I only looked at 32-bit.

By: Florian Mücke

Florian Mücke — Fri, 27 Apr 2012 07:58:02 +0000

Nice post. I never used MASM directly from within Visual Studio but I did MASM32 (www.masm32.com) a lot before even using Visual Studio. Nice to see both combined.
The debugging just works marvellous.

By: bill

bill — Tue, 03 Apr 2012 20:53:22 +0000

is this 32 or 64 bit assembly?

By: D-side

D-side — Mon, 26 Mar 2012 23:28:58 +0000

Step-by-step following actually worked until it came up to testing. I copied your code and failed to compile it. That was solved quite easily, there was a “forced error” amongst all, and the text in ucmacros.asm said that it should not be used anymore, as it’s now inside macros.asm. So I wiped “uc” and shifted down that macro inclusion after all the others. It all went right after that step.
Thanks, that was really useful! Quick Editor is also cool, but not that much.

By: Duncan

Duncan — Mon, 28 Nov 2011 16:08:09 +0000

Yes. But I don’t know about you but I don’t create that many completely new projects… I guess if it became an issue you could script it… I think all the config files are text based.

By: Waleed Ehsan

Waleed Ehsan — Mon, 28 Nov 2011 15:44:24 +0000

thanks and we have to do for every new project…………?