The Boost11 issue may be related to MC7, the plug-in is part of it's core installation by design. MC7 is now based on the new version of SONAR.

mettelus
Your explanation is truly your interpretation of the OP? Being able to recall content from posts so readily, yet applying assumption (to reach one's own ends) just as readily comes off "rather odd."

I really don't understand why this is so complicated. OP wanted easy access to new help files. SONAR has built-in easy access to new help files, which apparently the OP didn't know. In post #3 I told him how to take advantage of this easy access by clicking on Help > What's New, and even included an illustration. That sure seemed like a solution to his problem. But if you don't think that qualifies as a solution, that's fine. I just disagree that using a program's built-in help system is a workaround for finding help.
 
After that posts my posts dealt with issues raised in subsequent posts. 

scook
The Boost11 issue may be related to MC7, the plug-in is part of it's core installation by design. MC7 is now based on the new version of SONAR.

It's resetting the Boost 11 file path entry in the registry hive, rather than honoring it on every install, and the DLL version is incrementing upon each monthly release even though there is no code change.
 
This means boost11 is always being reinstalled as a new version on every release, and not even honoring the registry file path. That is two bugs from a developer perspective. It's probably the way they are building their solution in Visual Studio and dodgy upgrade logic.
 
If it's part of the core installation by design then it either needs to be separated from the core, or the core installation logic needs changing but that is an entirely separate matter to the behaviour.

Doktor Avalanche
It's resetting the Boost 11 file path entry in the registry hive, rather than honoring it on every install, and the DLL version is incrementing upon each monthly release even though there is no code change.
 
This means boost11 is always being reinstalled as a new version on every release, and not even honoring the registry file path. That is two bugs from a developer perspective. It's probably the way they are building their solution in Visual Studio and dodgy upgrade logic.
 
If it's part of the core installation by design then it either needs to be separated from the core, or the core installation logic needs changing but that is an entirely separate matter to the behaviour.

Have you elucidated this in the Problem Reports forum, or PMed one of the Cakewalk folks about this? The odds are remote of them finding this at the end of a thread that was about not knowing how to find the new help files. I'm sure the kind of specific information you seem willing to provide would be helpful to Cakewalk.

I doubt it will come as any revelations to Cakewalk, they must have been well aware of it before the patch was even released. The developers will understand how to fix the situation as I do (they have other code that works).

Doktor Avalanche
I doubt it will come as any revelations to Cakewalk, they must have been well aware of it before the patch was even released. 

Maybe not, if it's something longstanding that's been hanging around version after version, and no one noticed previously because it happened only once a year. Again, I don't understand how code and installers work, but for all I know what's there currently is just the regular installer with extras to accommodate monthly payments etc.

I'm sure this is all my fault... I decided that I was going to keep my new DAW organized so I got CCC...  (Just Kidding...)
Anyway, now I am more confused than ever as to how to get and stay organized.
 
Carry on... everything seems to be working. I'll figure it out.
 
J
 

Doktor Avalanche
I doubt it will come as any revelations to Cakewalk, they must have been well aware of it before the patch was even released. 

Anderton
Maybe not, if it's something longstanding that's been hanging around version after version, and no one noticed previously because it happened only once a year. Again, I don't understand how code and installers work, but for all I know what's there currently is just the regular installer with extras to accommodate monthly payments etc.

 
Already in problem report forums twice:
Music-Creator-7-Cant-See-Boost-11
CWBRN31812-CCC-installs-old-version-of-Boost
 
I still can't post links yet...