Beeej21,
Could you please post a link to the setup file or send it to me? It seems that I have the same problem after reinstalling sonar platinum after a disk crash. I'll send you and PM just in case.
 
Tore

Tore,
 
You have private message replies awaiting you, Sir.

For anyone else who might face this same problem, here is the link that I was sent by Cakewalk Support which allowed me to download the executable file that located the control surfaces folder and then installed the correct DLL file which was missing.

You have to be sure to delete any control surfaces loaded in the preferences, then restart Sonar Platinum, and after running the EXE file, you will find in your control surfaces options the VS700 listed.
 
Please note that this is not the latest updated DLL file.  There was a replacement DLL file that came out later which I happened to find on my server.  In the meantime, the EXE file did resolve the problem effectively.
 
 

Problem/Questions:

VS 700 Control Surface plugin installer

Solutions:

Note: Per previous instructions, the VS 700 Control Surface plugin installer can be found here: http://www.cakewalk.com/Support/Knowledge-Base/2007013201/V-Studio-700-Control-Surface-Plug-in-version-1-2-update#
 

Thanks a lot Beeeji21.
Everything seems to work after running the setup again. I can not replace it with the new dll without loosing vs 700 as an option, so for now I'll stick with the old dll, and hopefully there is not to many bugs.

I don't understand why it took out from Platinum ??? I hope cakewalk fix the problem.

REZA
I don't understand why it took out from Platinum ??? I hope cakewalk fix the problem.

I don't believe it is missing in Platinum, or has been taken out.  This issue is only for those who, like in my case, have installed Platinum ON TOP of X3, and then later uninstalled X3.  It is during the uninstallation process that the DLL file gets removed inadvertantly.  Otherwise, Platinum has no issue at all with the control surface.  This is my understanding based on my experience.

There has always been a risk associated with removing older versions of SONAR after installing a newer version. The uninstall process may remove components which have not changed between versions because, to the uninstaller, these component belongs to the version being removed. The installers used through X3 issued a warning about this on the first screen of the install process.

scook
There has always been a risk associated with removing older versions of SONAR after installing a newer version. The uninstall process may remove components which have not changed between versions because, to the uninstaller, these component belongs to the version being removed. The installers used through X3 issued a warning about this on the first screen of the install process.

This is a very true statement.  However, there are also a few plus points in installing on top of an older version, which I have found to be worth it, like the importing of project file directories, and VST locations (because I always change these parameters due to my hard drive setups), amongst other minor things.  That being said, this is the first time I have ever encountered such a "dramatic" problem after uninstalling an older version.  I have always, and I mean always, installed on top of the older version.. if for no other reason, than to have the peace of mind that recent projects can still be opened in the older version if need be.  I usually wait a month or slightly more before completely uninstalling the previous version.  Whether I had waited or not, I would've encountered this same issue however.  And all things considered, it was the only issue and while I scratched my head for a while, at least it was resolvable.

Beeej21
 there are also a few plus points in installing on top of an older version, which I have found to be worth it, like the importing of project file directories, and VST locations (because I always change these parameters due to my hard drive setups), amongst other minor things.

Importing a previous version config is convenient but not recommend by Cakewalk. I rely mostly on default directories redirected at the OS level with junctions created with mklink.
 
Leaving prior versions installed have other advantages such as the ability to open projects in the version which created the project, access to plug-ins not in the new version and comparing behavior between versions while on a bug hunt. Ignoring the recent tutorial projects added to Cakewalk Content, a typical SONAR installation consumes around 200MB of disk. The rest of the disk space used is shared between all the version of SONAR installed.

My case is even worth . After i bought the platinum, I decided to reinstall win8.1 and all my vsts and programs to get better performance and also make my pc fresh. I was so excited but after installing the platinum and couldn't find the vs700 control surface i regret restoring my pc. But i already read your post and came back here and downloaded the setup file . now it works fine. 
maybe if all the users who have vs700 ask cakewalk to fix the issue, they do it. :)