VS 2017 help

Hello @SharonLevy ,

The most common reason for such issue is missing workloads in Visual Studio. See here for details:
https://docs.parasoft.com/display/CPPTESTPROVS20201/IDE+Support

Basically, you need to make sure that both Universal Windows Platform and C++ development workloads are installed for C/C++test plugin to work.

Hi @SharonLevy ,

I can think of many possible reasons and things to check now. The issue seems related to specifics of this particular environment or installation. Therefore, at this point I would recommend to contact our support team to look closer into the issue.

You can contact us either through the Parasoft Customer Portal or by writing to support@parasoft.com.

See here for details: https://www.parasoft.com/support/

Hi @SharonLevy,

I would need to have a look at the complete and verbose Console Tab output from C/C++test run to see if I can tell what is going on or at least narrow down on the possibilities.
Can you do the following:
1. Verify that C/C++test is functioning correctly on one of example projects shipped with the product.
2. Go to Parasoft menu> Preferences> Parasoft> Console and set verbosity level to "High".
3. Launch your analysis again on your project, and attach full console output here.

In case the output contains sensitive content, you can contact suport team instead of using forum.

Hi @SharonLevy ,

Again, i strongly recommend to contact our support. This sounds like either configuration or installation issue which prevents C/C++test to work, but first: I cannot be sure with so limited information, and second: there is myriad of possibilities to check now, so working with our support team is the most efficient scenario.

Hello @SharonLevy ,

It seems there is something wrong locale settings in the environment. Can you try the following diagnostic steps and paste here the outcomes:
1. Run Control Panel> Region> Administrative Tab> press Copy Settings button, and take screenshot of displayed settings.
2. Launch command prompt, run "chcp" command, and collect the output.
3. Ideally, if you could also create C# solution, run the following program and collect the output, as the result may be different than with "chcp":

using System;
namespace CodePageCheck {
    class Program {
        static void Main(string[] args) {
            Console.WriteLine("OEMCodePage: " + System.Globalization.CultureInfo.CurrentCulture.TextInfo.OEMCodePage);   
        }
    }
}

Finally, you may want to try the following. It does not always help, but it is worth a shot even for diagnostic purposes:
1. Launch "Developer Command Prompt for VS2017"
2. Run the following command to change code page: CHCP 437
3. Launch VS2017 IDE from the same command prompt by running "devenv.exe"