Microsoft C++ Dev Kit 2015

Posted on  by 
Microsoft C++ Dev Kit 2015 Average ratng: 5,7/10 5534 votes
-->
  1. Visual C 2015 (also known as Visual C 14.0) was released on July 20, 2015. It features improved C11/14/17 support. 40 Without any announcement from Microsoft, Visual Studio 2015 Update 2 started generating telemetry calls in compiled binaries.
  2. To retarget your projects to use the Windows 10 SDK when you upgrade from a project version before Visual Studio 2015, follow these steps: To target the Windows 10 SDK. Make sure the Windows 10 SDK is installed. The Windows 10 SDK is installed as part of the Desktop development with C workload.

Visual C Redistributable for Visual Studio 2015. The Visual C Redistributable Packages install run-time components that are required to run C applications built using Visual Studio 2015.

The Universal Windows Platform (UWP) on Xbox development environment consists of a development PC connected to an Xbox One console through a local network.The development PC requires Visual Studio 2015 Update 3, Visual Studio 2017, or Visual Studio 2019.The development PC also requires Windows 10, the Windows 10 SDK build 14393 or later, and a range of supporting tools.

This article covers the steps to set up and test your development environment.

Visual Studio setup

  1. Install Visual Studio 2015 Update 3, Visual Studio 2017, or Visual Studio 2019. For more information and to install, see Downloads and tools for Windows 10. We recommend that you use the latest version of Visual Studio so that you can receive the latest updates for developers and security.

  2. If you're installing Visual Studio 2017 or Visual Studio 2019, make sure that you choose the Universal Windows Platform development workload. If you're a C++ developer, make sure that you also select the C++ Universal Windows Platform tools checkbox in the Summary pane on the right, under Universal Windows Platform development. It's not part of the default installation.

    If you're installing Visual Studio 2015 Update 3, ensure that the Universal Windows App Development Tools check box is selected.

Windows 10 SDK setup

Install the latest Windows 10 SDK. This comes with your Visual Studio installation, but if you want to download it separately, see Windows 10 SDK.

Enabling Developer Mode

Before you can deploy apps from your development PC, you must enable Developer Mode. In the Settings app, navigate to Update & Security / For developers, and under Use developer features, select Developer mode.

Setting up your Xbox One

Before you can deploy an app to your Xbox One, you must have a user signed in on the console.You can either use your existing Xbox Live account or create a new account for your console in Developer Mode.

Create your first app

  1. Make sure your development PC is on the same local network as the target Xbox One console. Typically, this means they should use the same router and be on the same subnet. A wired network connection is recommended.

  2. Ensure that your Xbox One console is in Developer Mode. For more information, see Xbox One Developer Mode activation.

  3. Decide the programming language that you want to use for your UWP app.

  4. On your development PC, in Visual Studio, select New / Project.

  5. In the New Project window, select Windows Universal / Blank App (Universal Windows).

Starting a C# project

  1. In the New Universal Windows Project dialog, select build 14393 or later in the Minimum Version dropdown. Select the latest SDK in the Target Version dropdown. If the Developer Mode dialog appears, click OK. A new blank app is created.

  2. Configure your development environment for remote debugging:

    a. Right-click the project in the Solution Explorer, and then select Properties.

    b. On the Debug tab, change Platform to x64. (x86 is no longer a supported platform on Xbox.)

    c. Under Start options, change Target device to Remote Machine.

    d. In Remote machine, enter the system IP address or hostname of the Xbox One console. For information about obtaining the IP address or hostname, see Introduction to Xbox One tools.

    e. In the Authentication Mode drop-down list, select Universal (Unencrypted Protocol).

Starting a C++ project

  1. In the New Universal Windows Project dialog, select build 14393 or later in the Minimum Version dropdown. Select the latest SDK in the Target Version dropdown. If the Developer Mode dialog appears, click OK. A new blank app is created.

  2. Configure your development environment for remote debugging:

    a. Right-click the project in the Solution Explorer, and then select Properties.

    b. On the Debugging tab, change Debugger to launch to Remote Machine.

    c. In Machine Name, enter the system IP address or hostname of the Xbox One console. For information about obtaining the IP address or hostname, see Introduction to Xbox One tools.

    d. In the Authentication Type drop-down list, select Universal (Unencrypted Protocol).

    e. In the Platform drop-down, select x64.

PIN-pair your device with Visual Studio

  1. Save your settings, and make sure your Xbox One console is in Developer Mode.

  2. With your project open in Visual Studio, press F5.

  3. If this is your first deployment, you will get a dialog from Visual Studio asking to PIN-pair your device.

    a. To obtain a PIN, open Dev Home from the Home screen on your Xbox One console.

    b. On the Home tab, under Quick actions, select Show Visual Studio pin.

    c. Enter your PIN into the Pair with Visual Studio dialog. The following PIN is just an example; yours will differ.

    d. Deployment errors, if any, will appear in the Output window.

Congratulations, you've successfully created and deployed your first UWP app on Xbox!

See also

-->

Important

Dynamics 365 for Finance and Operations has evolved into purpose-built applications to help you manage specific business functions. For more information about these changes, see Dynamics 365 Licensing Guide.

This topic explains how to use the Performance software development kit (SDK) to do multiuser load testing in an on-premises environment.

Important

Visual Studio 2019 will be the last version of Visual Studio with web performance and load test features. In the future, we will be publishing some recommendations for alternative solutions.

Microsoft Download C++ 2015

  • If you are using the Visual Studio and Test Controller/Test Agent for on-premises load testing, Visual Studio 2019 will be the last version. You can continue using it until the end of support cycle.

  • If you are using the cloud-based load testing service, the cloud-based load testing service will continue to run through March 31, 2020. Until then, you can continue to use all of the experiences powered by this service without interruption. Alternatively, you can switch to on-premises load testing.

For more information, see Cloud-based load testing service end of life.

Prerequisites

  • An on-premises environment that has volume data

  • A development environment that has the following characteristics:

    • Microsoft Visual Studio 2015 Enterprise or a later version is installed.
    • The Performance SDK is installed. (The SDK will likely be in K:PerfSDKPerfSDKLocalDirectory. However, depending on your environment, it might be in another location, such as C:PerfSDK.)
    • The on-premises environment can be accessed in a web browser. (The development virtual machine [VM] might be in the same domain as the on-premises environment, or the on-premises environment might have a publicly registered domain name.)

Create a single-user C# test from an XML recording

  1. Use Task recorder to create a recording of the scenario that you want to test.

    Important

    Your task recording must start on the default dashboard page. Otherwise, the test won't be able to run.

  2. Start Microsoft Visual Studio as an administrator, and build the PerfSDKSample project. This project is in the PerfSDK folder. If you've already built the project, skip this step.

  3. Select Dynamics 365 > Addins > Create C# perf test from recording.

  4. In the Import Task Recording dialog box, enter the required details, and then select Import.

    A C# test is generated in the Generated folder for the project that you selected.

    Note

    The test that is generated might have to be edited to resolve any compilation issues.

Run a single-user test by using the Performance SDK

Prepare the development environment

Follow these steps in the development environment.

  1. In Control Panel in Microsoft Windows, select System and Security > System > Advanced System Settings. Verify that the TestRoot environment variable is set to the path of the PerfSDK folder.

  2. Download the selenium-dotnet-strongnamed-2.42.0.zip and IEDriverServer_Win32_2.42.0.zip files from https://selenium-release.storage.googleapis.com/index.html?path=2.42/, and extract the files.

  3. Copy the dynamic-link libraries (DLLs) from the selenium-dotnet-strongnamed-2.42.0.zipnet40 folder to the PerfSDKCommonExternalSelenium folder. Also copy the IEDriverServer.exe from the IEDriverServer_Win32_2.42.0.zip to the PerfSDKCommonExternalSelenium folder.

  4. Generate a certificate to use for authentication for the tests. To generate a certificate file, open a Command Prompt window as an administrator, and run the following commands. When you're prompted for a private key password, select None.

    Note the following elements in these commands:

    • -n 'CN=127.0.0.1' gives a human-readable name to the certificate. The name of this certificate must be 127.0.0.1. Otherwise, the single-user tests won't be able to run.
    • -eku 1.3.6.1.5.5.7.3.1 gives the purpose of the certificate. It indicates that the certificate can be used as a Secure Sockets Layer (SSL) server certificate.

    After the script has finished running, you should see the following files in C:Temp:

    • authcert.pfx
    • authcert.cer
    • authcert.pvk

  5. Install the authcert.pfx certificate file. When you install the file, make sure that you select Local Machine.

  6. Copy the authcert.pfx file to the PerfSDK folder.

  7. Open a Microsoft Windows PowerShell window as an administrator, and run the following commands to get the thumbprint of the installed certificate.

  8. In Visual Studio, open the PerfSDKSample project that is in the PerfSDK folder.

  9. In the Visual Studio project, add a reference to the WebDriver.dll file in the PerfSDKCommonExternalSelenium folder.

  10. Open the CloudEnvironment.Config file, and replace the contents with the following template.

  11. In the CloudEnvironment.Config file, specify values for the following keys. These values replace the placeholder values in square brackets in the template.

    • HostName – Specify the URL that is used to access your on-premises environment. The URL should be [yourD365FOdomain]/namespaces/AXSF.

    • SoapHostName – Specify the same URL that you specified for HostName.

    • SelfSigningCertificateThumbprint – Specify the thumbprint that you retrieved from Windows PowerShell in step 7.

    • UserFormat – Specify the email address of a user who has the System Administrator role in your on-premises environment. The user must be an Active Directory Federation Services (AD FS) user.

    • UserPassword – Specify the password of the user whose email address you specified for UserFormat.

    • Username – Specify the same email address that you specified for UserFormat.

    • NetworkDomain – Specify the URL of the AD FS identity provider. You can find this value by running the following SQL query against the AXDB database of your on-premises deployment.

Prepare the on-premises environment

Follow these steps on each Application Object Server (AOS) VM in the on-premises deployment.

  1. Copy the authcert.cer file that you created in the Prepare the development environment section of this topic to the AOS VM.

  2. Install the authcert.cer certificate file. When you install the certificate, make sure that you select Local Machine. Also make sure that you put the certificate in the Trusted Root Certification Authorities store.

  3. Open the wif.config file in a text editor. The path of the file will resemble C:ProgramDataSFAOS1FabricworkApplicationsAXSFType_App19AXSF.Code.1.0.20180717001108.

    Note

    In the file path, the AOS number (AOS1 in this example) will vary, depending on the AOS node that you're on. Additionally, the ProgramData folder is a hidden folder. Therefore, to see the folder in File Explorer, you must enable hidden items.

  4. In the wif.config file, find the authority that is named https://fakeacs.accesscontrol.windows.net. In the list of thumbprints for this authority, add the thumbprint of the certificate that you created in the Prepare the development environment section. In the following example, the fourth thumbprint has been added to the https://fakeacs.accesscontrol.windows.net authority.

  5. Open the AXService.exe.config file in a text editor. You can find this file in the same directory as the wif.config file.

  6. Search the AXService.exe.config file for 'Aos.AosRole'. Replace the line that contains 'Aos.AosRole' with the following line.

    Note

    Setting the AosRole to AosRoleUnknown disables the limit on the number of web sessions per user. This is necessary to complete load testing with a large user load because the load test will create many sessions for a single user. Once you are finished with your load testing, reset this value to 'AosRoleWeb'.

  7. In Service Fabric Explorer, find the Code package for the AOS node, select the ellipse button (..), and then select Restart to restart the application.

Run the single-user test

  1. In the PerfSDKSample project, find the PurchaseReq.cs file. This file is a sample single-user test. In the file, comment out the following lines.

  2. Select Test > Test settings, set the Default processor architecture field to x64, and then build the solution.

  3. Select Test > Windows > Test Explorer to view the list of tests.

    Note

    Sometimes, Visual Studio might not update the list of tests after you create a test script from a task recording. In this case, restart Visual Studio, and then reopen Test Explorer.

  4. Run the sample single-user test by right-clicking CreatePurchReq. Alternatively, you can run the test that you created from your task recording. When you run the test, Internet Explorer should be started, and it should replay the scenario that you recorded.

Run a multiuser load test by using the Performance SDK

Create a multiuser test from a single-user test

After you create a single-user test by using the information earlier in this topic, you can convert it to a multiuser test. Add MS.Dynamics.TestTools.UIHelpers.Core; to your test script, and find the following line in the TestSetup method.

Replace that line with the following lines.

The test script that was generated by the Task Importer might contain a line that resembles the following line.

Remove this line from any tests that will be run as load tests. This code is required only for single-user tests and has a negative effect on the performance of load tests.

Make sure that the values that you entered when you made the task recording are randomized.

Run the multiuser load test

  1. In the Visual Studio editor, open the ProcureToPay.cs file, and append the following lines in the TestSetup method.

    Tune Up Service: Ignition System and Spark Plugs. When your vehicle is properly tuned, the ignition system, fuel system, emission system and computer system all work together in perfect harmony. This results in peak combustion chamber efficiency, improving performance, saving you money at the gas pump and making sure your car is emitting a minimal amount of pollutants. Precision auto tune tune up prices.

  2. Download the installer (.msi) file for Microsoft ODBC Driver 13 for SQL Server from https://www.microsoft.com/download/details.aspx?id=50420. (Select the 64-bit version of the .msi file.) Put the file in the Visual Studio Online folder in the PerfSDK directory.

  3. Modify the contents of the setup.cmd file in the Visual Studio Online folder so that they match the following code.

  4. Modify the contents of the CloudCtuFakeACSInstall.cmd file so that the Import command has an empty string instead of 'password'. The third line of the script should resemble the following line.

  5. In your solution files, double-click the vsonline.testsettings file to modify the test settings.

  6. In the Test Settings dialog box, on the General tab, set the Test run location field to Run tests using local computer or a test controller.

  7. On the Deployment tab, use the following settings:

    • Select the Enable deployment check box.

    • In the Additional files and directories to deploy field, make sure that the following files and directories are listed:

      • <Solution Directory>PerfSDKSamplebinDebug
      • C:PerfSDKCloudEnvironment.Config
      • C:PerfSDKauthcert.pfx
      • C:PerfSDKMS.Dynamics.Test.Team.Foundation.WebClient.InteractionService.dll.config
      • C:PerfSDKVisual Studio Online

  8. On the Setup and Cleanup Scripts tab, select the setup.cmd file that is in the Visual Studio Online folder in the PerfSDK directory.

  9. On the Hosts tab, select Run tests in 64 bit process on 64 bit machine.

  10. To run the test, open the SampleLoadTest.loadtest file, and select Run Load Test.

    When the test has finished running, you should see a summary that shows transaction results. Here is an example.

  11. To view various indicators for the test controller and test scenario, you can switch to the Graphs view.

    Note

    While tests are being run, information about your system isn't available in this view. To access this information, you must use Microsoft Dynamics Lifecycle Services (LCS) to monitor the CPU and memory usage of your AOS machine. Alternatively, you can set up perfmon directly on the AOS machine and set up the Microsoft Azure portal to monitor Microsoft SQL Server usage of Database Transaction Units (DTUs).

Troubleshooting

Zoom factor

This issue affects only single-user tests.

Error example

Solution

In Internet Explorer, you can change the zoom factor to 100 percent by changing the following registry keys:

  • ComputerHKEY_CURRENT_USERSOFTWAREMicrosoftInternet ExplorerZoomResetZoomOnStartup = 0
  • ComputerHKEY_CURRENT_USERSOFTWAREMicrosoftInternet ExplorerZoomResetZoomOnStartup2 = 0
  • ComputerHKEY_CURRENT_USERSOFTWAREMicrosoftInternet ExplorerZoomZoomfactor = 80000

Depending on the version of the local machine that is used, before you start the Remote Desktop Protocol (RDP) session, you might have to select Change the size of text, apps and other items. This field is available in Display settings in Windows.

If those steps don't work, try to change the size of your remote desktop before you start the RDP session, so that the default zoom level in Internet Explorer is 100 percent.

Certificate thumbprint errors

Error example

Solution

You might receive the error message for several reasons:

  • The certificate thumbprint that you copied into the CloudEnvironment.Config and wif.config files includes invisible Unicode characters. To determine whether the thumbprint contains invisible Unicode characters, paste it into a Unicode code converter, and see whether extra characters appear in the HTML/XML field. For example, you can use the Unicode converter that is available at https://r12a.github.io/apps/conversion/.

  • The certificate wasn't installed correctly on the AOS machine. To verify that the certificate can be found on the AOS machine, run the following Windows PowerShell script.

    If the thumbprint doesn't appear in the Windows PowerShell console after you run the script, the certificate can't be found. To fix the issue, copy and install the .cer file that you created earlier in this topic to the AOS machine.

  • If this issue occurs when you run load tests, the setup scripts might not have installed the corresponding .pfx file correctly. Verify that the password that is specified in the CloudCtuFakeACSInstall.cmd file matches the password that was set when the certificate was created.

No endpoint is listening

Error example

The tests process fails, and the following error message is shown.

Solution

This issue occurs when the host that is specified in the CloudEnvironment.Config file can't be accessed from the machine that is trying to run the tests or create users.

In the CloudEnvironment.Config file, review the values that are specified for the following keys:

  • <ExecutionConfigurations Key='HostName' Value='<web address of host>' />
  • <ExecutionConfigurations Key='SoapHostName' Value='<web address of SOAP>' />

The web addresses that are specified by these keys must be the environment that you're testing. In a web browser on your developer machine, make sure that you can open the web address that is specified for the HostName key.

Users can't be enumerated

This issue can occur when you run multiuser tests, or when you create users by using MS.Dynamics.Performance.CreateUsers.exe.

Error example

Solution

Two scenarios can cause this error:

  • The user who is specified as SelfMintingAdminUser in the CloudEnvironment.Config file must have the System Administrator role. This issue occurs when the System Administrator role isn't assigned to the user who is specified as SelfMintingAdminUser. To verify that you've specified the correct user, you can sign in to the endpoint and view the user's roles.

  • An incorrect NetworkDomain value was specified for the user who is specified as SelfMintingAdminUser in the CloudEnvironment.Config file. You can find the correct value by running the following SQL query against the AXDB database of your on-premises deployment.

At least one security token in the message could not be validated

This issue can occur when you run multiuser tests, or when you create users by using MS.Dynamics.Performance.CreateUsers.exe. It tends to occur when the AOS machine differs from the developer machine.

Error example

Solution

This issue occurs when the AOS endpoint can't validate the thumbprint of the certificate that you created. There are three possible causes:

  • In the CloudEnvironment.Config file, either a value isn't specified for the IsAdfs key, or the value is set to False. Make sure that the value for the IsAdfs key is set to True.
  • The certificate wasn't installed on the AOS machine. To fix the issue, copy the .cer file that you created earlier in this topic to the AOS machine, and install the certificate.
  • The thumbprint of the certificate wasn't added to the wif.config file on the AOS machine. To fix the issue, see step 8 in the Run a single-user test by using the Performance SDK section for information about how to add the certificate to the wif.config file. After you modify the wif.config file, be sure to restart the application through Service Fabric Explorer.

MS.Dynamics.Test.Team.Foundation.WebClient.InteractionService.dll.config is missing from the deployment items

This issue usually occurs only when you run load tests.

Error example

Solution

This issue occurs when the system can't find the MS.Dynamics.Test.Team.Foundation.WebClient.InteractionService.dll.config file when the load tests are run, because the file wasn't added as a deployment item. Verify that the MS.Dynamics.Test.Team.Foundation.WebClient.InteractionService.dll.config file is in the Out folder for the test run:

<solution path>TestResults<your test run>Out

If the file is missing, add it to the deployment items in the test settings.

Important

There are two files that have very similar names. The name of one file ends in *.dll, and the name of the other file ends in *.dll.config. The *.dll.config file must be in the deployment items in the test settings.

CloudEnvironment.Config is missing from the deployment items

This issue usually occurs only when you run load tests.

Error example

Solution

This issue occurs when the CloudEnvironment.Config file isn't present when the tests are run. The issue typically occurs when you run load tests and the CloudEnvironment.Config file wasn't added as a deployment item. Verify that the CloudEnvironment.Config file is in the Out folder for the test run:

<solution path>TestResults<your test run>Out

If the file is missing, add it to the deployment items in the test settings.

InteractiveClientId wasn't specified in the settings

Microsoft C Dev Kit 2015 2017

Error example

Solution

This issue occurs when no value is specified for the SelfSigningCertificateThumbprint key in the CloudEnvironment.Config file. In the CloudEnvironment.Config file, find the following line, and paste in the thumbprint of the certificate that you created and installed.

The remote host forcibly closed an existing connection

Error example

Solution

Microsoft C Dev Kit 2015 16

Run the following Windows PowerShell script on the development machine.

The w3svc service wasn't found on the computer

Microsoft C Dev Kit 2015 2016

This error only occurs when you run load tests by using Microsoft Visual Studio Online.

Microsoft C++ Dev Kit 2015 2017

Error example

Microsoft Visual C++ 2015 Install

Solution

Microsoft Dev Download

A hotfix is available that resolves this issue. The Microsoft Knowledge Base (KB) number is 4095640.

Coments are closed
Dev C++ Debugger Not WorkingVst Amp Rack Download Free
Scroll to top