Hi! Thanks for testing the new version.
On the 2.0 versus 4.0 folder; it's about the fact that the 2.0(and 3.X) and 4.0 frameworks are different runtimes. I'll add a task to explain the need for and use of these folders.
Re: backwards compatibility, I haven't tackled that one yet, but it hopefully should be as simple as replacing those .targets files with copies that directly import the 2.0 .targets file.
I'm disappointed to hear that you are still getting the vague preprocessor error! I did a lot of refactoring to make the errors more informative. If there is any way for you to provide a test project that I can use for testing, that would help a lot.
I'm afraid I haven't encountered the error you're describing with the 'VS installed template.' You should just see the standard "Instrumented XXX" projects under the C# Projects node. If you look under your <<VS 9.0>>\Common 7\IDE\Project Templates\CSharp\Windows
folder, do you see the .zip files for the Instrumented projects? If you do see them, try running "devenv.exe /installvstemplates" to get VS to refresh its cache.
On the components; NTrace now installs a Visual Studio package that delivers a property page for instrumented projects. This property page allows you to modify the list of components (flags) that you can associate trace messages with, and this set of flags
can be used in your EtwTrace.Trace() calls by using the overloads that take EtwTraceFlag parameters.
If you are retrofitting an existing project to use this VSPackage, you need to add a ProjectTypeGuids element to your project such as: