PC Review


Reply
Thread Tools Rate Thread

Com Interop error

 
 
=?Utf-8?B?U3RldmVT?=
Guest
Posts: n/a
 
      3rd Aug 2004
After working fine for months, today, when I ran my project I received the message:

"COM Interop registration failed. Could not find a type library for assembly 'Microsoft.VisualBasic'."

I chose to continue and the code ran as normal; however, I cannot build the release version of the project.

Naturally, I don't recall doing anything that would have caused this. How can I recover? Has a reference become corrupt?
 
Reply With Quote
 
 
 
 
Peter Huang
Guest
Posts: n/a
 
      4th Aug 2004
Hi Steve,

Did the problem occurred in the compile time or runtime?

You may try to follow the steps below to see if the problem persists.

1. Open Visual Studio .Net command prompt
2. Navigate to .Net framework directory
WindowsDirectory\Microsoft.NET\Framework\v1.1.4322 (If you are running .net
framework 1.1 otherwise use 1.0)
3. Run following command to register Microsoft.VisualBasic.dll assembly
with COM:
regasm Microsoft.VisualBasic.dll /codebase /tlb
4. Rebuild your solution Please let me know whether that works for you.


Best regards,

Peter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

 
Reply With Quote
 
=?Utf-8?B?U3RldmVT?=
Guest
Posts: n/a
 
      4th Aug 2004


""Peter Huang"" wrote:

> Hi Steve,
>
> Did the problem occurred in the compile time or runtime?
>
> You may try to follow the steps below to see if the problem persists.
>
> 1. Open Visual Studio .Net command prompt
> 2. Navigate to .Net framework directory
> WindowsDirectory\Microsoft.NET\Framework\v1.1.4322 (If you are running .net
> framework 1.1 otherwise use 1.0)
> 3. Run following command to register Microsoft.VisualBasic.dll assembly
> with COM:
> regasm Microsoft.VisualBasic.dll /codebase /tlb
> 4. Rebuild your solution Please let me know whether that works for you.
>
>
> Best regards,
>
> Peter Huang
> Microsoft Online Partner Support
>
> Get Secure! - www.microsoft.com/security
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>


Peter,

I was not familiar with the .Net command prompt environment so I did what you suggested through the W2k command prompt window. I received the following message:

..IVbHost.GetParentWindow(#0), Microsoft.VisualBasic'. Warning: Type library exp
orter could not find the type library for System.Windows.Forms.IWin32Window. IU
nknown was substituted for the interface.

and the message that the type library was registered successfully.


AND......the problem is now resolved. However, should I be concerned about the message above?

 
Reply With Quote
 
Peter Huang
Guest
Posts: n/a
 
      9th Aug 2004
Hi Steve,

Did my reply help you?
If you still have any concern, please feel free to post here.

Best regards,

Peter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
COM Interop Error on 64 bit OS =?Utf-8?B?QU5lZWxpbWE=?= Microsoft Dot NET Framework 1 14th Nov 2006 02:47 AM
Interop Error: Causes generic TypeLoad error... Robert Bouillon Microsoft Dot NET Compact Framework 6 30th May 2006 01:36 AM
interop error mcnewsxp Microsoft VB .NET 5 24th Mar 2006 07:13 AM
MC++ interop with C# error xiaodao Microsoft VC .NET 0 10th Feb 2006 11:33 AM
Fw: Com Interop error!!! Ramakant Microsoft Dot NET 3 2nd Jan 2005 09:41 PM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 09:23 PM.