Support Board
Date/Time: Tue, 01 Jul 2025 06:02:58 +0000
Post From: VisualCCompile.Bat calls vcvarsall.bat not installed
| [2020-01-02 04:06:46] |
| User701453 - Posts: 176 |
|
Fair enough, but if it is already so obvious to you, why make the statement below implying that you expected VS debug to somehow work if you followed the SC instructions, even though the debug build had failed.
Perhaps you shouldn't offer an apology, then get upset when it is accepted.Sounds like SJW types of apologies. Also, I know the cpp file is not going to debug if the"Build with Visual C++ -Debug" doesn't complete correctly. I'm also trying to debug using the same cpp file within the VS Solution that it was developed in. This isn't just a simple dll indicator, its an complex autotrading strategy. I need either of the debugging methods to work correctly, prefer both of them to work correctly Simply upgrading to a newer version is not necessarily helpful, as unless the header files have been revised since the earlier version they may not be re-downloaded.
So in other words SC customers have to go back and fix half ass upgrades.Did you actually try a clean install i.e. a new complete download to a new location? After following the upgrade procedure documentation. Since I use broker provided AT trading platform and SC is installed in the required brokers folder. The last thing I need to do is screw up being able to place trades and use my other working dlls, charts and work spaces. Date Time Of Last Edit: 2020-01-02 04:21:45
|