This is mentioned in the "known issues", but in a backhanded way that I didn't notice 'til I'd already filed a bug ("Running some WCF-based project templates results in a crash of svcutil.exe crashing due to a signing issue"). If you need to use svcutil to generate client proxy code in VS2008 Beta2, you'll have to apply a little hack. Seems they built it for delay signing, but never actually signed it- if you run it, you get the error quoted at the bottom of the page. You can work around this by preventing strong name verification for the svcutil assembly. Run:
sn -vR "C:\Program Files\Microsoft SDKs\Windows\V6.0A\Bin\svcutil.exe"
And the error message:
Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'svcutil, Version=18.104.22.168, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)File name: 'svcutil, Version=22.214.171.124, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' ---> System.Security.SecurityException: Strong name validation failed. (Exception from HRESULT: 0x8013141A)The Zone of the assembly that failed was:MyComputer