I know VSI is hard work, any chance of VSI integration like devkitpro.

Does anyone use BeebASM with Visual Studio - any version?

If not, I'll just try my old setup from the early GBA days.

richard

PS Done the nmake option - BeebASM is so fast that just setting BeebASM as the build tool and BeebEM as the exe to debug then Ctrl-F5 is fine - at least on the relocate sample.

Unfortunately I don't even have a full version of VS (stuck with the Express versions), so I can't even start trying to write plugins.

But yeah, I tend to just use a makefile to build the code and launch B-Em - which I can run in a keypress from Textpad (haven't worked out how to do it in Notepad++ yet, but I'm sure it's more than feasible).

How have you dealt with things like syntax highlighting in Visual Studio?

I haven't bothered, but you can add a single list that has its own colour, so I could add the key words to that.

I have been using beebasm for quite a while with VS and only just thought to change the error message format so that go to error works!

Just change:
src\asmexception.cpp line 61
from:
cerr << m_filename << ":" << m_lineNumber << ": error: ";
to:
cerr << m_filename << "(" << m_lineNumber << "): error: ";


It is also easy to use an NMake project in VS to build/run by setting:
Configuration Properties | NMake | General:
| Build Command Line
$(ProjectDir)..\Tools\beebasm.exe -i project.asm -do project.ssd -boot GAME -v
| Clean Command
del project.ssd
| Output
project.ssd

and if you want to run from VS too:
Configuration Properties | Debugging:
| Command
path to your favourite emulator.exe
| Command Arguments
$(ProjectDir)$(ProjectName).ssd
| Working Directory
$(ProjectDir)

Richard,

This sounds like it might be useful information to put up on the wiki - fancy writing a guide for us?

Sam.