Purpose (problem description)

This page provides multiple solutions based on the scenario for the error "None of the selected projects or websites has its target framework installed in a DotNet analysis".

Observed in CAST Extension Version


Release

Yes/No

1.0(tick) 
1.1(tick) 
1.2(tick) 
1.3(tick) 
1.4(tick) 
Observed on RDBMS
RDBMS
Yes/No
CSS4(tick)
CSS3(tick)
CSS2(tick)
Step by Step Scenario
  1. Deliver the source code
  2. Discover the project
  3. Run the analysis, you will get the error: "None of the selected projects or websites has its target framework installed in a DotNet analysis".
Action Plan
  1. Check if correct Frame work is installed.
    1. Check in the analysis machine, whether it is the same version of the .NET framework as the one specified in the project. If the project specifies 3.5, and there is only the 4.5 version installed, even if 4.5 is more recent than 3.5, Analyzer checks for the exact same version. Additionally, we should only install full version of the framework, not client profile.
    2. Check if there is an issue with detecting the right version of the framework to use for a project that has been migrated from a previous version of Visual Studio. This has been corrected in 7.3.4 version.
      However, we can apply the workaround to all project files that contain a <TargetFrameworkVersion> tag.
    3. Edit the project file to replace <ProductVersion>9.0.21022</ProductVersion> by <ProductVersion></ProductVersion>

      The reason why we have to remove the product version from project files that contain a <TargetFrameworkVersion> tag is because when the analyzer reads the Product Version it converts it into framework and uses the same framework as target framework rather than reading the tagged target framework.
  2. Check if If you can install all the frameworks used in the source

    1. Check If you have multiple frameworks used in your application and you have problems in installing the multiple frameworks on your system. If there is, use the following workaround which is a better way of packaging which would help to analyze the code and the assemblies better.

      1. Get the Microsoft Installation Folder of the required Framework.

      2. Create through the DMT a Resource Package pointing to this folder as shown on below screenshots


  3. Check if the analysis Units path is properly configured

    1. Open CMS, go to current version tab and open the analysis units of .Net package.

    2. Check the project path and actual path (by opening the deployment folder) of the analysis units

    3. Re package and deliver the .net package if you have mismatch in the path.

  4. Run the analysis.

  5. If the above solutions do not help you to solve the issue,then contact CAST Technical Support with the following Relevant input for reproduction of the issue

Notes/comments


Related Pages