Thanks for your Reply Dave me too. The only thing that i need to achieve is Accept the user input from the Setup Process and change the Webconfig(ConnectionString), i dont want to move directories around, but i think i should be easy to do that. My problem in the link i gave you, is that i cant open the WEbConfig to write on it. well the code works on the page , but not on the installer Class Project. Vuyiswa Maseko, Few companies that installed computers to reduce the employment of clerks have realized their expectations.... They now need more and more expensive clerks even though they call them "Developers" or "Programmers." C#/VB.NET/ASP.NET/SQL7/2000/2005/2008 http://www.vuyiswamaseko.tiyaneProperties.co.za vuyiswa@its.co.za www.ITS.co.za

It's not listed in a file anywhere. You have to parse the .EXE and examine metadata, export and import tables. It would help greatly if you understood the PE file format. Without that knowledge, you'll find this project impossible. Google results for PE file format[^]. A guide to posting questions on CodeProject[^] Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic      2006, 2007, 2008

Ohhh...you didn't specifiy that in your question. References don't exist at runtime, so you can't get this list. But, there's is a close approximation. You can find the CURRENTLY LOADED assemblies (kind of like your references) for an AppDomain by getting the list from AppDomain.CurrentDomain.GetAssemblies(). Something like: Imports System.Reflection . . . Dim assemblies As Assembly() = AppDomain.CurrentDomain.GetAssemblies() For Each a As Assembly In assemblies Console.WriteLine(String.Format("Codebase: {0}", a.CodeBase)) Console.WriteLine(String.Format("FullName: {0}", a.FullName)) Next Now, as you run your application, this list may change as execution moves from one assembly in your app to another. A guide to posting questions on CodeProject[^] Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic      2006, 2007, 2008

The method you are using (and was suggested in my link) works for ActiveX Dlls and OCX objects. First, have your class library a module not a class: Public Module TestDll Public Sub Test() MsgBox("Hi") End Sub End Module Then use LoadLibrary to load the dll. Delegate Sub Tst() . . . Static dll_loaded As Boolean, dll_handle As Int32, fn As tst dll_handle = LoadLibrary("Testdll.dll") msgfn = GetProcAddress(dll_handle, "Test") msgfn.Invoke() By the way, why do you want to late-bind? Try using Declare which makes it much faster and more reliable!