Today I started to evaluate the new VC.NET 2003 compiler. I like what I see so
far. I decided to try because the Big M is making it nicer for DirectX
developers to develop on the new compiler. With the DX9 Summer update, they've
integrated the current help into the compiler, added a shader
debugger that doesn't work with so well with VC6.0, and an integrated D3D
debugging environment. That's nice. There's also some less technical reasons.
For instance, right now I'm writing this daily inside an html page on my
compiler Pretty sweet. No more need to manage 2 applications, this
environment is pretty much my desktop.
Along with the new compiler comes new headaches of course. The compiler is
stricter than the last. That's no surprise. I've been dealing with that since
MSVC1.0. My WorkspaceWhiz doesn't load because I didn't do the full upgrade
path from VS.NET 2002. I didn't have the MFC7.0 installed and so it doesn't
load. I have MFC7.1 now. The website said that he'd put out a new build as soon
as he got his compiler in. I'll just wait for that. Actually, that's it. Oh
yeah, one more thing. Nobody else here uses it and I DON"T THINK THEY WANT TO
SWITCH! But, who knows, if I can make a strong enough case, maybe they will. I
can try to push for the new projects, but I think they'll be reluctant for
these existing projects.
Check out the debugging support you get in this compiler.
Here's a breakpoint set in an effect file...
You get to see the variables in the effect file...
You also get to peak at the current render targets and set textures.....
Here's a full picture: Image
With all that support, why would I want to go back to VC6.0?
The rest of the day was dedicated to checking in the effect stuff.
Unfotunately, wasn't so smooth. Things that work in EffectEdit aren't working
in code. I can't figure out why. I'll get it eventually though.
Also discussed what would be needed from for a map editor.