RackAfx / Visual Studio 2015 Integration problem:
I have Visual Studio 2015 Professional installed under Windows 10 and have for quite some time, everything working well.
I installed RackAfx v18.104.22.168 (yesterday) and it is working in the sense that it generates a buildable project. If I manually launch visual studio, I can successfully build the project.
However, if I select the Open Compiler toolbutton from the RackAfx GUI, or if I right click on the background of the first control in the GUI (In my case Knob Grp 0 since my view is set to modern), I get the following error messages:
from toolbutton: Error in CreateProcess() for compiler path:
c:\Program Files(x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenev.exe
from Knob Grp 0 right background click:
compiler is not alive/available yet (while visual studio is open and running)
I have verified this is a valid path to my Visual Studio installation and devenv.exe is present, I am logged in as Administrator, and
in View,Preferences on the RackAfx Main menu I have set the Visual Studio C++ compiler droplist choice to 2015 Professional/Enterprise/Community
Furthermore, if I double click on the .vcxproj file in Windows File Explorer, Visual Studio autoloads the project just fine.
Any help / suggestions would be appreciated. I did look through the Faqs but did not see this addressed there and I did not see this specific issue addressed in this forum, but (Famous Last Words) I may have overlooked something.
I was able to resolve this issue by changing the RackAFX desktop shortcut properties under the compatibility tab . Run as Administrator.
Didn't think this should be needed since my login to the workstation has Adminstrator rights, but I am just reporting this worked for me in case it might help someone else. Not sure why it would be necessary.
Thanks - I'm running the same setup on Win10 but do not have the admin issue.
The CreateProcess( ) function is used to invoke Visual Studio and it inherits whatever admin rights the user has when they logged on. In theory (at least) it should not be much different from double-clicking on the devenv.exe executable. But each new release (and update) of Windows tends to change something with security so I'm guessing that may have been what happened.
Thanks again for the report on this.
Most Users Ever Online: 152
Currently Browsing this Page:
Guest Posters: 1
Moderators: W Pirkle: 656