Hey guys, I finally got around to setting up VS2005 SP1 and doing a full installation of the SDK a few days ago, but I've got a bit of an issue and I'm actually not sure what to do. I'm trying to attach to my XeDK's active process/title, but VS2005 doesn't even finding my 360 as an active device to attach to. I attach to local processes on my computer :\. I've been told that the SDK should automatically integrate your 360 into the VS Debugger as long as it's part of the neighborhood, but right now that doesn't appear to be happening. I've also been told there's a way to manually add your Kit in VS2005, but I haven't seem to found any way to, so I'm not sure how sturdy that claim is. Not sure if this has anything to do with the above problem, but I've had issues with various third party programs I've been given for use with my kit. They fail on attempted connection to the XeDK. Why? I really don't know. But to make it weirder, if I take a screenshot with one of said applications, and then do memory edits, everything works fine. If I simply startup the application and try to do memory edits, it just fails and the program(s) crash. example: So I know it doesn't have to do with my firewall, and the 360 neighborhood never has any issues. Also, just to note that I know I don't have a test kit, so that's not the issue ;p For the record, I'm using Windows 7 Ultimate x64. I've heard of Dev Win7 owners having these issues in regards to connection issues, but I'm wondering if anyone has solved or concluded on why it crashes. But I do need help with getting VS2005 to work though, as that's the main subject of this post. -Doom
If you install VS2005 over the sdk It kinda overwrites all of the xbox 360 settings, the best thing to do is unistall everything. Install VS2005 and then the sdk and all the settings should be ok.
Yep, 100% sure, It's not a test kit . Anyways, I've figured out the problem with the connection thingy. It has to do with an extender DLL used, it's messed up in some way, and it's used in said problematic applications. I'll have that sorted soon hopefully. As for VS, I'm doing as you suggested leo. -Doom
Doing as leo instructed worked just fine. Initially I had only tried uninstalling and reinstalling the SDK after I got VS2005 installed, but for some reason that didn't work. So for future reference, uninstall the SDK, then VS2005. Afterwards install VS2005, then the service pack update for it, then the SDK. After multiple reboots for the installations, VS2005 seems to find my kit fine and works just as it should . Thanks, -Doom
