Menu ▾ ▴

Compilation issue in VS2008

Help
Anonymous
2011-10-26
2013-06-12

  • Anonymous

    Anonymous - 2011-10-26

    I am getting below errors while compiling - (using .NET framework 3.5 profile) 

    Error   1   error C2065: 'Audit_AccountLogon_KerbCredentialValidation' : undeclared identifier  c:\Users\XXX\Downloads\ovaldi-5.10.1-src\src\probes\windows\AuditEventPolicySubcategoriesProbe.cpp  346 OVALInterpreter
Error   2   error C2065: 'Audit_Logon_NPS' : undeclared identifier  c:\Users\XXX\Downloads\ovaldi-5.10.1-src\src\probes\windows\AuditEventPolicySubcategoriesProbe.cpp  347 OVALInterpreter
Error   3   error C2065: 'Audit_ObjectAccess_DetailedFileShare' : undeclared identifier c:\Users\XXX\Downloads\ovaldi-5.10.1-src\src\probes\windows\AuditEventPolicySubcategoriesProbe.cpp  348 OVALInterpreter

    Am I missing an include file?

     

  • Anonymous

    Anonymous - 2011-10-26

    Btw, if I compile the code with Visual Studio 2010, it works fine.

     

  • Danny Haynes

    Danny Haynes - 2011-10-26

    The audit events mentioned above are only in Windows 7 and you need the Windows 7 SDK.  By default, I do not think Visual Studio 2008 comes with the Windows 7 SDK.  Here is the link to the download.

    http://www.microsoft.com/download/en/details.aspx?id=8279

    It is also important to mention that after ovaldi-5.10.1, we will be using a Visual Studio 2010 project file (.vcxproj) and will no longer be supporting the Visual Studio 2008 project file (.vcproj).

    Please let me know if you have any other questions.

    Thanks,

    Danny

     

  • Anonymous

    Anonymous - 2011-10-26

    Great! Thanks Danny.
    The only reason I was using VS2008 was because VS2010 targets .NET Framework 4.0 by default. After a lot of research, I was able to locate this link which shows how to target .NET 3.5.

    But the problem is that GAC gets messed up if you install VS 2008 after VS 2010.

    I will try to include Win7 SDK in VS2008 and see if that works.

     

  • Anonymous

    Anonymous - 2012-01-17

    Make sure that your WindowsSdkDir environment variable points to v7 of the SDK. In my case, I installed the Windows 7 SDK to the default location of C:\Program Files\Microsoft SDKs\Windows\v7.0.

    i.e.
    $(WindowsSdkDir)\ should reference C:\Program Files\Microsoft SDKs\Windows\v7.0\

     

Log in to post a comment.