>>>>Hi All,
>>>>We need a .NET dll, it should work with VFP. Our developer generates .NET DLL but VFP cannot see that DLL. That doesn't matter .COM .DLL or not. Just work with VFP enough for us... What he should do when generates DLL for VFP?
>>>
>>>Should be straightforward. Create a .NET class library. e.g:

namespace ClassLibrary1
>>>{
>>>    [ClassInterface(ClassInterfaceType.AutoDual)]
>>>    [ProgId("Class1Library.Class1")]
>>>    public class Class1
>>>    {
>>>        [ComVisible(true)]
>>>        public string Doit()
>>>        {
>>>            return "Hello World";
>>>        }
>>>    }
>>>}

In the project 'Properties/Application' page click 'Assembly Information' button and make sure 'Make assembly COM visible' is checked. Build the application. If all is well then Class1Library.Class1 should appear in the registry.
>>>
>>>In VFP:

object = CREATEOBJECT("Class1Library.Class1")
>>>? object.Doit()

Note I deliberately made this a bit more complicated than ness. in that I've defined a ProgId that is different to the Class namespace.
>>
>>Viv
>>
>>How would one register the class if it had been built on another machine?
>
>You would need to use regasm.exe : http://msdn.microsoft.com/en-us/library/tzat5yw6(v=vs.110).aspx
>(Does the same type of thing as regsvr32 but specifically for .NET assemblies...)

Is there any way use regsvr32 for .net .dll's? Because I use Molebox, Molebox can move registries from development machine to customer machines as virtual except registries created with regasm.