17.0.0 Beta 3 - Windows 10
Printed From: Codejock Forums
Category: Codejock Products
Forum Name: Toolkit Pro
Forum Description: Topics Related to Codejock Toolkit Pro
URL: http://forum.codejock.com/forum_posts.asp?TID=22803
Printed Date: 25 December 2024 at 1:25am
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: 17.0.0 Beta 3 - Windows 10
Posted By: Kenneth
Subject: 17.0.0 Beta 3 - Windows 10
Date Posted: 26 November 2015 at 2:34pm
I am testing the 17.0.0 Beta 3 on Windows 7 and Windows 10. On Windows 7, all is working so far. However on Windows 10 I have problems with the Codejock Deploy Wizard.
I download and install the MFC Beta 17.0.0.092115 in the Program Files (x86) directory. Then the Deploy Wizard starts and asks for the location of the vcvars32.bat file and advances to the "Select Build Configuration" and I complete the options as I do on Windows 7. I advance to the "Ready to Build!" panel then advance. It the gives the error message "An error occurred during build process, the Deployment Wizard is unable to continue." When I select the OK button to the message, I get the following:
Starting build, please be patient this may take a while to complete...
----------------------------------------------------------------------------
'MSDEV' is not recognized as an internal or external command,
operable program or batch file.
----------------------------------------------------------------------------
IMPORTANT: If your Visual Studio environment crashed during the build, try
disabling all of your addins and try again. To disable addins:
1. Start Visual Studio
2. Go to Tools/Add-in Manager
3. Uncheck all the checkboxes in the Startup column
----------------------------------------------------------------------------
I am using Visual C++ version 6.0
|
Replies:
Posted By: Kenneth
Date Posted: 27 November 2015 at 4:51pm
Problem solved. Everything works now, and from my initial testing, it the 17.0.0 release looks good.
I have no idea what was causing the Deploy Wizard to fail yesterday. I decided to try it again and see if I could isolate the failing area, and
where it failed yesterday on attempting to start msdev, it worked today!
|
|