Skip to Content
author's profile photo
Former Member

Problem with removal of V1.0.2: "Load of property <x> failed"

I am having a problem with Visual Studio.Net 2003 which is apparently caused by the removal of the SAP .Net Connector version, v1.0.2.

After removal of version 1.0.2, VS.Net can't load project files correctly, and it generates errors for all project properties, displaying messages like

"Load of property 'AllowUnsafeBlocks' failed."

"Load of property 'ApplicationIcon' failed."

"Load of property 'AssemblyKeyContainerName' failed."

... and so on, in the Task List pane.

Removal of 1.0.2 is evidently causing something in VS.Net 2003 to be corrupted. Another symptom is that when I click on a project file in Solution Explorer, the display in the Properties pane is incorrect. Normally it would show the project name followed by "Project properties", as in "BDC_Map_Lib Project Properties". But after removal of 1.0.2, it shows only "Project Properties", and the pane which should display the actual properties is blank, or shows only the "Policy File" property. If I click around some (for instance clicking on one of the files in the project), it eventually shows the project name, but still fails to show all the properties, displaying only "Policy File" in the "small" properties pane. And when I right-click on the project and display the "big" properties window, all the project properties are blank until I am able to get it display the project name, after which some of the properties are still blank (such as the Default Namespace).

This is repeatable and consistent, and installing V2 doesn't make it clear up. I'm testing in MS Virtual PC, so I can reproduce the problem quickly, and I've tested it about 5 times with the same result. Before removal of 1.0.2, VS.Net properly displays the project properties, and after removal, it has the problem.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Aug 06, 2004 at 07:39 AM

    Hello Joseph,

    thanks for the information.

    Can you try if one of the following commands fix the situation:

    regsvr32 "C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\vcpackages\csproj.dll"

    regasm "C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE\PublicAssemblies\VSLangProj.dll"

    devenv /resetskippkgs

    I assume that the first command will do it - and of cause analize why NCo 1.0.2 uninst causes these problems.

    Thanks again for the help,

    Reiner.

    Add comment
    10|10000 characters needed characters exceeded