After a project is upgraded from VB6 to VB. NET, the project file cannot be opened after the upgrade, and the project file name becomes. vbproj. vs7.vbproj.

I have been hiding from the first day, and I have to skip the 15th day. I finally want to upgrade a VB6 project to VB. NET. On my colleague's computer, there is no problem with the upgrade. But on my computer, the upgrade process seems to be quite smooth, that is, when the upgrade is almost complete, the project file cannot be opened, the project file is named. vbproj. vs7.vbproj. Open this file in vs2008 and prompt to upgrade. Okay, continue to upgrade. The upgrade fails and a reference problem is reported. What's going on? Open the strange project file in notepad and find that there is a reference without name:

<Reference
Name= ""
Guid= "{D97A6DA0-A85C-11CF-83AE-00A0C90C2BD8 }"
Lcid= "0"
Versionmajor= "2"
Versionminor= "0"
Wrappertool= "Tlbimp" />
 

The reason is that this name is a Null String. by querying the registry, the original name is "Microsoft Active Server Pages Object Library", fill it in the name, and then use vs2008 to open it. You still need to upgrade it, no problem. Upgrade now. The upgrade is successful.

what I don't know is that my colleague only installed vs2008 on the machine. It's not so troublesome to upgrade and open it directly, and even the solution files are available, this is what happens on my machine where vs2008 and vs2010 coexist.