This section describes how to initialize Visual Studio and then fix common issues after you verify that Visual Studio initialized properly.
Initializing Visual Studio
If you do not virtualize the toolchain and did not initialize Visual Studio on every agent host for each ECloudInternalUser during installation, you must do the initializations manually. Each agent runs as user ECloudInternalUser1, ECloudInternalUser2, and so on.
On each agent host:
-
Log into the user account.
-
Run Visual Studio.
-
Choose Tools > Options and browse to Project and Solutions > Build and Run.
-
Set the maximum number of parallel project builds to 1.
-
Choose Help > Customer Feedback Options.
-
Initialize the Customer Experience Improvement Program to either Yes or No.
If you still encounter issues, go to the CloudBees Build Acceleration Knowledge Base and search for “Visual Studio.” Also refer to https://ask.cloudbees.com/ for answers to common issues with Electrify and the Visual Studio Integration.
Visual Studio is missing the CloudBees Build Acceleration menu
Description
The Visual Studio IDE Converter is installed, but the CloudBees Build Acceleration menu is missing and the Tools menu item is corrupted (shows "CloudBees Build Acceleration").
3:Error: Adding Build menu item: Could not load file or assembly 'stdole, Version=7.0.3300.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
Solution
"%PROGRAM_FILES%\Microsoft SDKs\Windows\v7.0A\Bin\gacutil.exe" -i "%PROGRAM_FILES%\Common Files\Microsoft Shared\MSEnv\PublicAssemblies\stdole.dll"
Run Visual Studio and check if the CloudBees Build Acceleration menu is present.
-
If Step 3 doesn’t work, install the Office 2003 Update: Redistributable Primary Interop Assemblies from https://download.cnet.com/Office-2003-Update-Redistributable-Primary-Interop-Assemblies/3000-2064_4-10742122.html.
-
Run:
devenv.exe /ResetSettings
This resets the menus.
Application Data folder could not be created. make: * [all]
Solution
Do one of the following:
-
Use one of the solutions described in the “What does it mean when Visual Studio reports "The Application Data folder for Visual Studio could not be created"?” Ask article at https://ask.cloudbees.com/questions/707/what-does-it-mean-when-visual-studio-reports-the-a.html.
-
Use ecdevenv locally (so that
devenv.exe
does not need to run on the agent).
Build terminated with “not making progress” error
The build is slow (not parallelized) and/or each line of the build output is prefixed with 1>, 2>, etc
When virtualizing the Visual Studio toolchain, regsvr32 fails trying to register a DLL that uses debug CRT DLLs
Solution
Do one of the following:
-
See https://docs.microsoft.com/en-us/previous-versions/visualstudio/visual-studio-2008/aa985618(v=vs.90)
-
Copy debug DLLs from
<VSINSTALLDIR>\VC\redist\Debug_NonRedist
to the target directory (the location of the DLL that is being registered) -
Copy
Microsoft.VC90.DebugCRT.manifest
andmsvcr90d.dll
from<VSINSTALLDIR>\VC\redist\Debug_NonRedist\x86\Microsoft.VC90.DebugCRT