CODEWITHSUNDEEP
.netvb.netdynamicassemblies
user410989
user410989

Reputation:

Debug dynamically loaded assembly

I am debugging an assembly which I loaded dynamically with Assembly.Load(Byte[]), but I am facing some problems.

First of all, I can't move the yellow arrow in Visual Studio 2010 to step into other lines of code, and also I am getiing exceptions ("Cannot find the method on the object instance.") when trying to do a quick watch on objects from a third party library (controls from Infragistics for example.)

Dim data = My.Computer.FileSystem.ReadAllBytes(file.FullName)
Assembly.Load(data)

When using Assembly.Load(String), everything works fine, and there are no problems.

Assembly.Load(IO.Path.GetFileNameWithoutExtension(file.Name))

Any idea why the behaviour is that much different? Anyway to fix this?

I tried loading the debugging symbols for my assembly with Assembly.Load(byte[]. byte[]), but I still get exceptions when trying to debug objects from third party libraries.

Upvotes: 10

Views: 6267

Answers (2)

ladenedge
ladenedge

Reputation: 13419

The debug symbols for your assembly are not being loaded into the application domain. When you use the string variety, .NET automatically looks for a .PDB alongside the filename you specify.

To load an assembly and its symbols from byte arrays, use Assembly.Load(byte[], byte[]), like so:

Dim data = My.Computer.FileSystem.ReadAllBytes(file.FullName)
Dim pdbData = My.Computer.FileSystem.ReadAllBytes(pdbFile.FullName)
Assembly.Load(data, pdbData)

Upvotes: 15

Mark Cidade
Mark Cidade

Reputation: 99957

When you pass it an array of bytes there's no way to know what file it comes from (or if it even comes from a file) so it can't locate the PDB file with the source code line information.

You can fix this by saving the byte[] as a file and making sure there's a PDB for it with the same file name.

Upvotes: 1

Related Questions