Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[rk1200]

Are there other developers who are running VS2008 Pro on 64bit machines ? I noticed some of the post build events are trying to launch gacutil.exe from 'C:\Program Files\Microsoft SDKs\Windows\v6.0\bin'.

For example from OMLEngine:

"$(DevEnvDir)..\..\..\Microsoft SDKs\Windows\v6.0\Bin\GacUtil.exe" /i "$(TargetPath)" /f

On a 64 bit VS2008 that translates to

'C:\Program Files (x86)\Microsoft SDKs\Windows\v6.0\bin'

There is no v6.0 on my machine but 6.0A which corresponds to the latest SDK.

Few ways around it; modify script to be more generic i.e. test some variables and set them or modify registry or my fix I just created a a v6.0 directory and copied the gacutil exe and config file. I could care less about two files sitting off in never-never land.

Anyways I've always been part of team where we have the same tool set and obviously in a project like this that's impossible. So I am just curious who else runs in an x64 environment? Are there some other things I should be aware of ?

[STReNT]

I'm running VS2008 Dev Edition on Vista Ultimate x64.
Not sure on which which packages of Windows SDK's I've installed - but I do have a v6.0 in my x86 Microsoft SDK's folder.

[mikem2te]

I have been using Vista 64 bit as well. There are a few things you may run upon with either x86 or x64.

The latest Nunit version may require a smalll update to a couple of project references as the version no is changed.

If you intend to do any DBEditor work you will need DXPerience version 8.2.6 installed as well or you will get loads of error messages when you try to make any changes to any of the forms. I haven't tried a later version though - makes sense to stick with 8.2.6 as it works

Regarding your sdk issue, look at http://code.google.com/p/open-media-library/wiki/Compiling

Q: I get the following error compiling: Error 10 The command ""C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\..\..\..\Microsoft SDKs\Windows\v6.0\Bin\GacUtil?.exe" /i "C:\OML\OMLEngine\bin\Release\OMLEngine.dll" /f" exited with code 3. OMLEngine

A: First try to run Visual Studio as an administrator. If that doesn't help, try to go to \program files\microsoft SDKs\Windows\ if the only folder there is 6.0A then open a command prompt and go to \program files\microsoft sdk\windows and input: mklink v6.0 v6.0a. Try compiling again, should help.

[Translucent]

Yes that is an issue that we just haven't really fixed.  I personally have a hardlink from 6.0A to 6.0   Also, some of my new changes for the wix custom actions assume you have WiX 3.0 installed in its default location.  Generally I like the idea of bundling the required items in the svn repo and using those, I've done this for the MS dlls so that when building on win7 you still compile against the vista versions.

[DVDJunkie]

Are there other developers who are running VS2008 Pro on 64bit machines ? I noticed some of the post build events are trying to launch gacutil.exe from 'C:\Program Files\Microsoft SDKs\Windows\v6.0\bin'.

For example from OMLEngine:

"$(DevEnvDir)..\..\..\Microsoft SDKs\Windows\v6.0\Bin\GacUtil.exe" /i "$(TargetPath)" /f

On a 64 bit VS2008 that translates to

'C:\Program Files (x86)\Microsoft SDKs\Windows\v6.0\bin'

There is no v6.0 on my machine but 6.0A which corresponds to the latest SDK.

Few ways around it; modify script to be more generic i.e. test some variables and set them or modify registry or my fix I just created a a v6.0 directory and copied the gacutil exe and config file. I could care less about two files sitting off in never-never land.

Anyways I've always been part of team where we have the same tool set and obviously in a project like this that's impossible. So I am just curious who else runs in an x64 environment? Are there some other things I should be aware of ?

I run / build / hack / chop / & butcher using the SVN's source without ever modifying build's etc using VS2k8 Pro on Win7 x64.  I ran into your problem above, but I just added  symbolic links (mklink - http://en.wikipedia.org/wiki/NTFS_symbolic_link) when there was a discrepancy in what path the project build was looking for in a particular installation (SDK or otherwise).  As far as what other things to look out for?  Blah, cant tell yell, that was 2 weeks ago and I can't remember what I did 2 days ago....   There were a few snags, but nothing monumental, I just hashed them all out and it worked.

[msbob]

ya, lotsa fun in referencing gacutil. Was dealing with this last night for someone else...

%programfiles%\Microsoft SDKs\Windows\v6.0\Bin (vstudio 2k8)
%programfiles%\Microsoft SDKs\Windows\v6.0A\Bin (vstudio 2k8sp1)

wonder if vstudio 2k10 sticks it in v7.0....

mabe something like this as the post-build event;
@for /F "tokens=1,2*" %%i in ('reg query "HKLM\SOFTWARE\Microsoft\Microsoft SDKs\Windows" /v "CurrentInstallFolder"') DO (if "%%i"=="CurrentInstallFolder" ("%%kbin\GacUtil.exe" /i "$(TargetPath)" /f))

[msbob]

Changed the post-build for Library to the below. Looks wacky as hell but it is the same logic the "Visual Studio Command Prompt" uses to set the sdk pathing...

@call :GetWindowsSdkDirHelper HKLM > nul 2>&1
@if errorlevel 1 call :GetWindowsSdkDirHelper64 HKCU > nul 2>&1
@if errorlevel 1 exit /B 1
@exit /B 0

:GetWindowsSdkDirHelper
@for /F "tokens=1,2*" %%i in ('reg query "%1\SOFTWARE\Microsoft\Microsoft SDKs\Windows" /v "CurrentInstallFolder"') DO (
   if "%%i"=="CurrentInstallFolder" (
      SET "WindowsSdkDir=%%k"
   )
)
@if "%WindowsSdkDir%"=="" exit /B 1
"%WindowsSdkDir%bin\GacUtil.exe" /i "$(TargetPath)" /f
@exit /B 0

:GetWindowsSdkDirHelper64
@for /F "tokens=1,2*" %%i in ('reg query "%1\SOFTWARE\Wow6432Node\Microsoft\Microsoft SDKs\Windows" /v "CurrentInstallFolder"') DO (
   if "%%i"=="CurrentInstallFolder" (
      SET "WindowsSdkDir=%%k"
   )
)
@if "%WindowsSdkDir%"=="" exit /B 1
"%WindowsSdkDir%bin\GacUtil.exe" /i "$(TargetPath)" /f
@exit /B 0

:end