Thank you for the response
I assume that when you say "the hotfix implements exactly this" (with a thread reference), that you mean (quoted from Lee's response to the referenced thread):
This workaround only address the issue of error markers not appearing in 12.0.1 release and only where they were appearing in the 12.0.0 release.
The current status of the error marking feature is that are currently only available for Build and Rebuild project commands and but only when using vsbuild for the build system (which is usually automatic for gcc projects and java projects). It is not automatically available for the Compile command or any custom build commands, and it is also not automatically available for building associated projects (Visual Studio for example) without tweaking or workarounds. It has been problematic making it work for all of the use cases available to SlickEdit users. In future releases, we are looking into making it uniformly available for all project commands
Of course the issue I seem to be having is that one of the things that was working in 12.0.0 (using Visual Studio devenv instead of vsbuild) is now not working. Lee's response does not say whether the hotfix or the workaround addresses any issues using devenv (instead of vsbuild).
I guess what I'm asking is should I download the hotfix for my copy of 12.0.1 or should I download the error_marker_workaround.e patch/workaround? Or perhaps both? Or will neither of these help me with this issue?
Also thanks for the hint on using error markers with custom tools. I had seen this suggestion before but had not implemented it yet. I'm more concerned with getting a normal "Build" to mark the errors(like it did before) and with why set-error-markers seems to do nothing regardless of the executed tool (Build, Rebuild, or custom tool).
Thanks
Les