Is there any easy way to deploy to multiple Xboxes when I want to run my project? For instance can I add a post build event or better still modify MSBuild to send my project to a second Xbox upon deployment?

You could use xnapack from a post-build event or custom MSBuild task. Run it once to build a .ccgame package, then again once per Xbox to deploy and run that .ccgame.

I don't generally find it's worth the hassle of setting that up, though. Most often when I'm writing network code, I fairly quickly get to a point where my network protocol is roughly stable, and I'm just iterating on fine details. Once I'm in that state, I generally get one machine set up as the host, using ctrl+F5 to launch, then create a session on that box, and just leave them sat in it. I can then change my target Xbox (via the new combo selector in the Visual Studio toolbar) and use regular F5 to deploy and test new builds on my second Xbox as I iterate on the code. I can often work for as much as an hour just iterating on code on one box, while joining the same original host session. Only quite rarely do I make a change so big that it breaks the network protocol, at which point I have to quit out of the host session, change Xbox again via the toolbar, and redeploy to the host console.

When I'm working on projects that are churning more rapidly, I usually just have two instances of Visual Studio open with the same solution in both. Again use the toolbar to pick a different target Xbox for each, then you can just alt+tab between them and F5 to deploy. Two copies of VS is by far the easiest way to have a debugger attached to two Xboxes at once.

Presumably two copies of VS allow the code to be debugged on 2 Xboxes at the same time? I've no idea if I will ever have to do that though!

Yep. It's useful having two debuggers connected even if you aren't single-stepping through the code, so you can get trace output from both machines, and also so that if anything unexpected happens, you get the exception message and callstack. You can't predict whether it's the host or client that is likely to crash, so it's useful to be ready for either if something goes wrong!

I know this may sound a little lazy, but I have 2 Xbox's, one in my bedroom upstairs and one downstairs.  I do most my development downstairs, but on occasion would like to start deploying test builds form my laptop upstairs, say, before bed.  Do I need to have 2 XNA Memberships? for this? 

 

I just got the second Xbox. I read that I can get a memory card to transfer my profile to the new Xbox, but that I will need to re-download any Live games that I want to play on both of them.  Jsut a little confused ont eh whole process.  I was goign to make my brother another Live Gold acct so we could play against each other.  But for now, I'm intersted in the deploying aspect. 

 

Does anyone know if the memory card is used to jsut transfer or does it only live on the memory card then?

The memory card is kind of like an RV.  It can be used to transfer, but it can also permanently remain on the card.  When you transfer your profile to your memory card it will move to your memory card.  In order for you to use it, it will have to be in the slot.  Transferring the profile from the card to the Xbox will move it (there is no option copy).

You can copy XBLA games to memory card as well (if its large enough).  Otherwise you can download a game you've payed for on the new Xbox and play it so long as your memory card with your profile is in a memory slot.  Once you take it out, you take your profile with it.  The XBLA software will still be there, but won't have a "license" per say.  The other option is to "recover" your profile on the Xbox each time.  This can be a lengthy process, though

 

Thanks for the clarification.  I went ahead and got a 512MB to be safe, even though I mainly need to use it for the profile.  But I guess if i ever get my game working, I can load it on there to show people easier maybe.