Blog Stats
  • Posts - 157
  • Articles - 0
  • Comments - 90
  • Trackbacks - 19

 

Thursday, November 30, 2006

Call of Duty 3 - XBox 360 vs PS3 vs Wii


GameTrailers.com has posted two videos that show in-game footage of CoD 3 played on an Xbox 360, PS3 and the Nintendo Wii and the differences are astonishing, I guess that me saying that I need to ask my girlfriend a Xbox 360 for X-mas says it al? The video quality on the Wii is a bummer.

http://www.gametrailers.com/gamepage.php?id=2650


Cross-posted from The .NET Aficionado
  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati

Cannot hit breakpoints when debugging ASP.NET 2.0


A couple of days ago one of our .NET developers asked me to help solve an issue on his machine. He said that his breakpoints were not being hit due to missing symbol files. I asked him to close Visual Studio and show me step by step how he debugs.

  1. He started Visual Studio 2005
  2. He opened his solution
  3. He publishes his site to c:\inetpub\wwwroot\<project>
  4. He navigates to the website using IE
  5. He sets a breakpoint
  6. He attaches to the worker process

The breakpoints will not be hit and I explained him why. Publishing your web site cause your web site to be pre-compiled using the executable apsnet_compiler.exe. The problem here, if you can even call this a problem, is that by default the debug info will be omitted.

There are several ways to solve this:

  1. Use Visual Studio 2005 Web Application Projects which shares the compilation semantics known from ASP.NET 1.1
  2. Do not publish your site instead xcopy deploy the site
  3. On your dev machine you can point the virtual directory to your ASP.NET project directory
  4. Pre-compile manually with aspnet_compiler.exe -d to emit the debug info

Cross-posted from The .NET Aficionado
  • Share This Post:
  • Share on Twitter
  • Share on Facebook
  • Share on Technorati
 

 

Copyright © Gabriel Lozano-Morán