Wireshark-dev: Re: [Wireshark-dev] setting up for win32 development
Date: Mon, 4 Apr 2011 09:25:23 -0400
I found that my Visual Studio's SetEnv.Cmd file had bugs in it - mostly missing backslashes in paths - that I had to fix before I could run Wireshark's Makefile.nmake without errors.
  
Not sure that's your issue, but if so it would explain why upgrading WS doesn't help.