VC add files to folder failure

VC-> add files to folder failed, depressed for a long time, the last online search, said office2007 caused by the fault. With a try, I uninstalled the office, which I just got used to, just a short time ago. After I restarted it, I found it quite easy!

In fact, office2007 is still very useful, but unfortunately!

 

After unloading the file, go to the Internet to check the file and find a solution to the conflict:

The open-fileplug-In msdev.exe application is displayed when vc6.ProgramError. The "0x00000004" memory referenced by the "0x73d311c7" command cannot be "read ". When you right-click the file and add it to the project, vc6.0 reports an error and exits. There is no problem in enabling workplace.

So I uninstalled vc6.0 and re-installed it again, but the problem still exists. Today I changed the English version and re-installed it again. The problem still exists. Google once said that office2007 is in conflict with vc6.0, so you can use office2007 without vc6.0. In fact, my S10 was co-existent between office2007 and vc6.0 without any problems. But now there is a problem, I immediately thought of updating the sp2 of office2007 several days ago. It is obvious that the sp2 of office2007 conflicts with vc6.0, And the SP2 is uninstalled, and vc6.0 returns to normal, so that office2007 and vc6.0 have nothing to worry about.

The solution is as follows:

First download a filetool (http://download.microsoft.com/download/vc60ent/s1/6.0/w9xnt4/en-us/filetool.exe download decompressed), download is a C ++ original file, need to compile through VC to generate a filetool. dll

Copy this plug-in
X: \ Program Files \ Microsoft Visual Studio \ common \ msdev98 \ addins

Re-open vc6, tools-> Customize-> add-ins and macro files, and select filetool developer studio add-in.

Open vc6 with a floating toolbar (a o). Click a to add the file to the project, and click o to open the file. Isn't it strange that a plug-in has been made, and the original conflicts have not been improved.

The following errors are also solved:

Access violation (0xc0000005) in devshl. dll at 0x5003eaed.
Devshl. dll referenced memory at 0x0000000. The memory cocould not be read.

Msdev. exe-application error: "0x00000004" memory referenced by the "0x73d311c7" command. The memory cannot be "read"