Help with Interoperability VB.NET 2005 DLL.

[mjk9564]

I created a dll in VB.NET 2005 and I’m trying to access it in FoxPro 9. This works fine on the development machine, but after I register it on the test machine I get errors saying the file cannot be found. After doing some research I found out that the development machine has a CodeBase registry entry and the test machine didn’t I added this to the test machine and it worked. I’m wondering why REGASM didn’t add this setting to the registry and if there is another command I need to run when I try to register this. I have read a lot about installing it in the GAC, but gacutil does not seem to be in .NET 2.0 framework. Is there a new command for this in 2005 or at least a command to automatically put the CodeBase entry into the registry?

Here is the article I read, but it is on older framework

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/callnetfrcom.asp.

Command I used for to register it on the test machine.

regasm /tlb:shutdownprocess.tlb shutdownprocess.dll

Thank you!

 

[stravis]

Just use the /codebase parameter with the regasm tool to specify the location of strong-named assembly. This will create your registry entry for you.

stravis

 

[mjk9564]

Would the command look like this then?

regasm /tlb:shutdownprocess.tlb shutdownprocess.dll /codebase
[\code]

Do you know if there is a GAC utility in .NET 2.0?

 

[stravis]

Yes that is the correct syntax.

The GAC utility is now installed with Visual Studio and the SDK only. I guess they are trying to encourage developers to not install in the GAC.

stravis