I don't know what it was made in, but I don't need to import anything like that to use it. I can simply add a reference in the project properties, and all the methods I need are available. My guess is that the DLL was made in VB6, but I don't know that for sure.
I always just drag & dropped it into c:\windows\assembly. It's worked for other .NET assemblies, including interops that other publishers provided themselves. When I try it on these, nothing happens at all.
If I run gacutil on the interops that were generated by VS2010, it refuses and states...
I have a COM dll called "Magic.dll." I did not make it. It exposes some classes which are useful to me, but referencing it directly creates a large number of warnings. Refrencing it directly *also* generates two new assemblies, "Interop.Magic.dll" and "Interop.VBA.dll."
I found that if I...
Nevermind. Figured it out myself. But if anyone knows a better way to do it than what I did, I'd be happy to hear it.
My situation is that my own machine is running Visual Studio 2010, but I need to access a VSS repository. VS2010 appears to have built-in functionality for accessing TFS repos...
Let's say I have an executable which relies on a set of rules, defined in an XML file. My main function looks something like this:
Sub main()
Dim rulesEngine As New RulesEngine("rules.xml")
DoStuff(rulesEngine)
End Sub
Later, I find that in practice, this executable...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.