locked
Errors on Build VS 2012 RRS feed

  • Question

  • User-373571878 posted

    Hello,

    I am getting these errors when I try to run my VS 2012 program:

    ------ Build started: Project: NewsRoll, Configuration: Debug Any CPU ------
    C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(2015,5): warning MSB3304: Could not determine the dependencies of the COM reference "VB". Error loading type library/DLL. (Exception from HRESULT: 0x80029C4A (TYPE_E_CANTLOADLIBRARY))
    C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(2015,5): warning MSB3284: Cannot get the file path for type library "7c0ffab0-cd84-11d0-949a-00a0c91110ed" version 1.0. Library not registered. (Exception from HRESULT: 0x8002801D (TYPE_E_LIBNOTREGISTERED))
    C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(2015,5): error MSB3303: Could not resolve COM reference "a24fbe2b-ade4-4cd7-95df-1d2623ef0fef" version 6.0. Object reference not set to an instance of an object.
    C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(2015,5): warning MSB3284: Cannot get the file path for type library "7c0ffab0-cd84-11d0-949a-00a0c91110ed" version 1.0. Library not registered. (Exception from HRESULT: 0x8002801D (TYPE_E_LIBNOTREGISTERED))
    C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(2015,5): error MSB3303: Could not resolve COM reference "ce5e0e33-cf2a-4fa4-a16a-e1924dc2b0c5" version 6.0. Object reference not set to an instance of an object.

    These are the components listed under Recent:

    Accessibility  1.1
    Microsoft Excel 15.0 Object Lib
    Microsoft Visual Basic for Application Extensibility 5.3
    OLE Automation 2.0
    Visual Basic for Applications 6.0
    Visual Basic Objects and Procedures 6.0
    Visual Basic Runtime Objects and Procedures 6.0

    How do I know which Library these errors are referring to and how can I fix?

    thanks for your time

    Thursday, February 25, 2016 6:24 PM

Answers

  • User-373571878 posted

    Not sure of the ramifications yet of my work around, but so far it seems to work.

    I just removed those Visual Studio version 6.0 references all together.

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Thursday, February 25, 2016 8:43 PM