Tor, I don't know if this will be helpful, but I've been going through the same troubles, but not with the "Plugin" or "engine" SDK, rather with the LiteC "legacy mode" samples in the "work" directory. I can now tell you some things to look out for if your are trying to compile these under VS .NET 2003.

First, make sure all common paths for "includes" and "libraries" (for any Windows project) come before those you add, under "Tools/Optins/Projects/VC ++ directories. You can use the little up and down arrow controls to move items up or down the list. If you are wondering if the includes are being used in the expected order, under the project's properties "C/C++", under "Advanced" you can set "Show Includes" to "Yes".

Now, I was working with HelloWorld.c when I ran into troubles, so some of what I had to do may be specific to this project. But, I had to change the calling convention to "__stdcall", under "C/C++","Advanced","Calling Convention". On this same property page, I had to set "Compile As" to "Compile as C++ Code". I think this is because the tools are trying to go by the ".c" extention of the source, so confused. And, just to be sure, since this project is a Windows EXE, set "Linker/System/Subsystem" to "Windows"; this should already be the case if you created an empty Win32 project.

The above fixed all my problems, except for an "unresolved _WinMainCRTStartup"; or something on that order. Though it sounds like the tools are supposed to be smart enough to know and identify the "entry point" to the Windows app, I had to explicitly set this to "WinMain", under "Linker/Advanced/Entry point".

So, if you ever want to try out building some of the "legacy mode" apps under Lite-C's "work" directory, you hopefully won't have to spend the hours I did trying to get the simplest app to comile and run