first i must apologize... i laughed out loud when reading your post...

i know it's wrong of me, and i'm not proud of it, but i did.

to my defense, i wasn't laughing at you, i was laughing with you.

to recompile a .rc file, you must delete the .rc file.

the build steps for the .rc compiler take effect only when that file is missing.

otherwise they just use the one that's there.

i know it sounds stupid, but here's the logic:

on windows the .r file is not used directly, and must be converted to .rc (not so on the mac).

so when you change the .r file, no change happened in the .rc. (obviously)

so when the plug-in is compiled the .rc file is used, and because it is unchanged, the compiler doesn't see a reason to recompile it...

only when that file is missing does the custom build steps for the .rc file take place.

:-)

ok...

there can also be problems with the resource compiler tool when the sdk is not installed at it's default location. (c:\program files\ect...)

that problem can also happen when the specific project you're working on is not located in the same folder as the rest of the sample projects.

is that's the case, then the custom build step command needs to be adjusted to the different paths.

and in any case, what are the exact messages you're getting from the compiler?

you could try brute-force solving of the problem.

duplicate a working sample project, and then just copy/paste your code into it's .cpp and .h files...

p.s.

i see you give your plug-ins a match name beginning the "BW".

so do i!!!

mine stands for "BitWise". what yours?

another way of trying to pinpoint the problem:

in visual studio, with the properties window open, select your project, and control + click another project that compiler correctly.

the property window will now leave all that's the same blank, and will show only what's different.

(i used that a lot to hunt down differences in settings)