So I am trying to begin programming homebrew with my dev that does not have a sidecar. I just did a clean full install of the sdk (21173.4) with visual studio 2010. I made a hello world application but now I am trying to figure out how to run this on my xdk. Every time I try to run it ask for me to plug in the sidecar to my computer. Do I need a sidecar to debug?
To my knowledge, you do not need a sidecar to debug (poke memory values). But you do need a sidecar to do DVD emulation, so you might need a sidecar to push your code to the xdk on the fly. If you can't get it to work, just compile the .xex and copy/paste it to the xdk with xbox neighborhood. It just takes a little bit longer. I hope this helps. I'm still learning myself.
Thanks for the reply. I have been copy and pasting but it just takes SO fucking long, compared to on the fly debugging. I remember running code on the fly but I forgot how to do it. Would you teaching me how to poke memory values?
I recommend using Vis Studio 2005/ 2008 if you can find it because it will automatically compile the code into an XeX which you can burn to a disk or put on your XDK's hard drive without a sidecar. BTW: You said you were on 16202 on another thread lol Welcome to Assembler!
Im on flash 16202, sdk 21173.4. Big arse of a difference lol Visual Basic 2010 compiles to a xex too.
I'm not sure if your visual basic 2010 has a tool to poke memory or not. However, there are many apps you can download to poke memory. Some are game specific; some are more robust. Here's an example of one of those programs: https://code.google.com/p/peek-poker/ Poking memory is useful for testing changes. For example, if a vehicle's maxSpeed is a value stored in memory, you can increase that value to see how it performs, instantly.
I misread that sorry. I have never had any luck compiling with 2010 but whatever. If the kit is a full Debug kit then it will have full memory poking abilities whether it has a sidecar or not, just use peekpoker or the SDK tools.
If you do not have a sidecar you need to go into the projects properties through visual studio, and when I say project I mean the project not the solution. Then go to the Xbox 360 tab and change deloployment to the hard drive. Then it will deploy and debug fine.