Clever Geek Handbook

Harden, no .NET assemblies found

I'm trying to set up a Fortify scan but it keeps giving me errors like this:

Cannot find class 'System.Object' in the specified search path and Microsoft .NET Framework Libraries

I added .NET build locations on the command line, but it still doesn't work.

Any ideas?

+3


source to share


1 answer


Fortify tries to find .NET assemblies and cache them. He searches for Visual Studio in the Windows registry to find the .NET version he should be using.

You need to use -vsversion

to specify the version of Visual Studio that was used when generating the .NET code:

  • VS2005 = 8.0

  • VS2008 = 9.0

  • VS2010 = 10.0

  • VS2012 = 11.0

  • VS2013 = 12.0

  • VS2015 = 14.0

If not, use:

-Dvs.<VS Ver w/o the .>.dotnet.clr.version=<CLR version>

For example VS2012:



sourceanalyzer -b MyProj -vsversion 11.0 <your translation args>

or

sourceanalyzer -b MyProj -vsversion 11.0 -Dvs.110.dotnet.clr.version=v4.0.30319

Here are all the "fallback" VS arguments:

-Dvs.110.dotnet.clr.version=v4.0.30319
-Dvs.100.dotnet.clr.version=v4.0.30319
-Dvs.90.dotnet.clr.version=v2.0.50727
-Dvs.80.dotnet.clr.version=v2.0.50727
-Dvs.71.dotnet.clr.version=v2.0.50727
+3


source






More articles:


All Articles