| T O P I C R E V I E W |
| AlexLisle |
Posted - Mar 14 2006 : 04:25:46 AM
We are currently having problems with visual assist at the 360 sdk. It seems if you have Visual Assist installed before installing or upgrading the SDK when you then try and compile anything we get loads of R6034 errors and nothing will compile, has anyone had anything similar to this? |
| 20 L A T E S T R E P L I E S (Newest First) |
| .oisyn |
Posted - Jul 26 2010 : 11:56:41 AM
quote:
Originally posted by msew
FWIW: I have no problems with VAX and XDK installations.
Me neither, and I have used both VAX and the XDK for ages.
[.edit: oh sorry, I just noticed this was a very old thread]
quote:
Originally posted by jacksparrow
Hey im looking to buy an xbox 360 xdk. i have a hunch that nobody here would know where to tell me to go to find one to buy?
As a consumer? Fat chance. You'll need to be a registered Xbox 360 developer. Also, those things cost around $10k :). But that all seems way off topic here on wholetomato. I suggest you call or email Microsoft. |
| jacksparrow |
Posted - Jun 28 2010 : 5:14:20 PM
Hey im looking to buy an xbox 360 xdk. i have a hunch that nobody here would know where to tell me to go to find one to buy? |
| gstelmack |
Posted - Jul 11 2006 : 4:54:41 PM
Well, that explains THAT problem. Thanks all! |
| RoscoP |
Posted - Jul 10 2006 : 1:48:49 PM
Excellent, thanks! |
| support |
Posted - Jul 09 2006 : 1:34:21 PM
Fixed in 1530.
VA X no longer touches devenv.manifest.exe during install. |
| support |
Posted - Jul 02 2006 : 2:58:24 PM
Than you for the workaround.
case=1542 |
| feline |
Posted - Jul 01 2006 : 5:04:54 PM
out of interest do you have any idea why the SDK would require a manifest file?
as for the installer, i will chaise support about this. we have the slightly tricky problem that people without the XBox SDK installed need the manifest removed, if we think VA installed it, but people with the SDK need it left alone. |
| evolution |
Posted - Jun 29 2006 : 2:00:36 PM
Would like to bump this thread - the Xbox XDK apparently does require a devenv.exe.manifest file in the VS.NET/Common7/IDE directory in order to successfully build Xbox 360 projects. Hopefully wholetomato will remove the code that is deleting the manifest file, but in the meantime here's a very easy way to workaround this for others getting this problem.
1. Reinstall your XDK
2. Make a backup of the VS.NET2003/Common7/IDE/devenv.exe.manifest file (i.e. devenv.exe.manifest.bak)
3. Each time you install a new version of VAX, manually restore the devenv.exe.manifest file from the backup you made.
4. Requires a restart of VS.NET for it to take effect.
Works like a charm - nothing else is required (i.e. contents of bin/obj folders don't seem to be relevant at least for the XDK's dependency on the manifest). |
| feline |
Posted - Jun 06 2006 : 3:12:48 PM
the manifest files were discussed in this thread a while ago:
http://forum.wholetomato.com/forum/topic.asp?TOPIC_ID=3952&whichpage=1&SearchTerms=devenv.exe.manifest
it does seem that they can cause problems, but no one mentioned anything quite like this. one suggestion was to delete the 'bin' and 'obj' folders from each of the project directories and then do a full rebuild.
unfortunately i am not sure what else to suggest. |
| RoscoP |
Posted - Jun 02 2006 : 11:11:58 AM
Yep, I renamed devenv.exe.manifest to something else, started devenv, started an xbox build and I get the error box. I try again after putting the file back and everything works. Seems like the culprit.
Rosco |
| feline |
Posted - Jun 01 2006 : 5:52:57 PM
for a while VA used to add a manifest file its self, specifically devenv.exe.manifest
however VA no longer does this, and it tries to remove it if one is found. we discovered that having the manifest file could cause problems.
can anyone confirm that removing the manifest file (a file that is not there by default) causes problems? anything is possible, but this does sound odd to me. |
| Mindcrime |
Posted - Jun 01 2006 : 01:24:45 AM
I believe this is because VAX seems to delete or rename the .manifest file in the same directory as devenv or cl.exe. Without the manifest file, you will see these errors. |
| RoscoP |
Posted - May 26 2006 : 8:16:51 PM
Re-installing the latest xdk has made the problem go away. Not sure what is up.
Rosco |
| RoscoP |
Posted - May 26 2006 : 8:04:44 PM
I have this problem as well. Didn't occur with the earlier version of VA I had (1418 I think). I installed the latest (1445) and started getting this problem. I still have this problem after uninstalling VA. I have the 360 XDK installed and it fails for xbox builds, but not others. Breaking into Devenv.exe with windbg yields the following callstack for the thread that shows the r6034 dialog error. Not sure if that is the final culprit, but looks promising. Hope this helps, next task is to try re-installing the XDK.
ChildEBP RetAddr
091fe9ec 77d49418 ntdll!KiFastSystemCallRet
091fea24 77d561c6 USER32!NtUserWaitMessage+0xc
091fea4c 77d6a92e USER32!InternalDialogBox+0xd0
091fed0c 77d6a294 USER32!SoftModalMessageBox+0x938
091fee5c 77d95fbb USER32!MessageBoxWorker+0x2ba
091feeb4 77d96060 USER32!MessageBoxTimeoutW+0x7a
091feee8 77d80577 USER32!MessageBoxTimeoutA+0x9c
091fef08 77d8052f USER32!MessageBoxExA+0x1b
091fef24 7813965c USER32!MessageBoxA+0x45
WARNING: Stack unwind information not available. Following frames may be wrong.
091fef68 78131c17 MSVCR80!rand_s+0x4e0
091fef8c 78132206 MSVCR80!c_exit+0x1bd
091fefc8 78132337 MSVCR80!_p__winver+0x13c
091feff8 7c91cbab MSVCR80!_p__winver+0x26d
091ff100 7c916178 ntdll!LdrpRunInitializeRoutines+0x344
091ff3ac 7c9162da ntdll!LdrpLoadDll+0x3e5
091ff654 7c801bb9 ntdll!LdrLoadDll+0x230
091ff6bc 1eeb045f kernel32!LoadLibraryExW+0x18e
091ff6f0 59a50b9f va_x!DllCanUnloadNow+0x50d78
091ff70c 7c9105c8 VCProjectEngine!DllUnregisterServer+0x37f64
091ff718 7c910551 ntdll!RtlpFreeToHeapLookaside+0x22 |
| msew |
Posted - Mar 26 2006 : 01:56:58 AM
FWIW: I have no problems with VAX and XDK installations.
|
| cbeauche |
Posted - Mar 24 2006 : 4:09:15 PM
The SDK for the XBox360 contains a add-in to copy files to the console.
I re-installed the XBox360 SDK and the problem went away.
There must be some overwriting information somewhere in the registration. |
| rhummer |
Posted - Mar 16 2006 : 9:15:11 PM
I can give this a try tomorrow morning, I need to update my XDK. I'll update then. |
| support |
Posted - Mar 16 2006 : 9:04:32 PM
Before we dig too far, how does the SDK effect the IDE? Does it include an add-in?
Does uninstalling VA X resolve the problem?
You mention, "if you have VA install before..." which makes us wonder if the problem occurs if you install VA X *after* installing/upgrading the SDK.
Some earlier versions left a file around that caused some odd behavior when compiling applications. Maybe the same is happening for you. Try removing devenv.exe.manifest from the directory in which your devenv.exe lives.
|
| bugfix |
Posted - Mar 16 2006 : 3:57:34 PM
I havent't updated my xedk for a while as im doing other stuff right now but I had no problems w/ vax upto 142x builds. Maybe some more recent xedk introduced some problems.
-bugfix |
| cbeauche |
Posted - Mar 16 2006 : 2:43:15 PM
Yes, I see the same here. |
