Comments
Sort by recent activity
This has now been fixed in 6.5.0.55 which will soon be available as the next EAP release. / comments
This has now been fixed in 6.5.0.55 which will soon be available as the next EAP release.
Hi.
The .Addin file that you get in the bug report has an <Assembly>..</Assembly> element that gives the path to the directory where the Reflector.exe was running when the addin was installed. I imagine that this directory has been deleted and hence the load of the addin fails.
You can recreate the Addin file to point somewhere else using the Tools/Integration options dialog in Reflector - select the version and OK the dialog and a new Addin file should be generated which will point Visual Studio to the directory of the currently running reflector.exe. [You may need to uncheck and OK to get the previous Addin file removed] / comments
Hi.
The .Addin file that you get in the bug report has an <Assembly>..</Assembly> element that gives the path to the directory where the Reflector.exe was running when the addin was installed. I im...
I'd have a look at the IL view. The pinned will probably because the local is marked as pinned in the IL.
If I take the following program
struct Foo
{
public byte x;
}
void Test(int input)
{
unsafe
{
Foo foo1 = new Foo();
byte* moo = &foo1.x;
}
}
there will be a local moo
.locals init ([0] valuetype ConsoleApplication1.Program/Foo foo1,
[1] uint8* moo)
Adding a pinned modifier to the local
.locals init ([0] valuetype ConsoleApplication1.Program/Foo foo1,
[1] uint8* pinned moo)
gives a decompilation in Reflector as
Foo foo = new Foo();
byte* pinned numPtr = &foo.x; / comments
I'd have a look at the IL view. The pinned will probably because the local is marked as pinned in the IL.
If I take the following program
struct Foo
{
public byte x;
}
void Test(int input)
{
unsafe...
The optimization level in the View/Options... dialog affects this.
For example, taking the program
class Program
{
int Test { get; set; }
static void Main(string[] args)
{
Func<int> test2 = () => Int32.Parse(args[0]);
}
}
and displaying the class Program with methods expanded with level set to 2.0 shows all sorts of compiler generated things, while setting it to 3.5 displays more or less the above. / comments
The optimization level in the View/Options... dialog affects this.
For example, taking the program
class Program
{
int Test { get; set; }
static void Main(string[] args)
{
Func<int> test2 = () => ...
Thanks for reporting this.
Reflector is failing due to one of the marshalling attributes on one of the methods in the MSC.Thunder.Common.dll assembly. Specifically, the SHCreateItemFromParsingName method has an out parameter with a marshalAs interface (IL syntax)
[out] class MSC.Thunder.Common.IShellItem& marshal( interface(iidparam = 2) ) ppv) cil managed
I've logged your report in our bug tracking system as RP-694 / comments
Thanks for reporting this.
Reflector is failing due to one of the marshalling attributes on one of the methods in the MSC.Thunder.Common.dll assembly. Specifically, the SHCreateItemFromParsingName ...
This has now been fixed. Reflector was failing to decompile a MarshalAs attribute when the type was UnmanagedType.Interface and an IidParameterIndex parameter was supplied. / comments
This has now been fixed. Reflector was failing to decompile a MarshalAs attribute when the type was UnmanagedType.Interface and an IidParameterIndex parameter was supplied.
This is probably due to some of the files being marked as having come from an untrusted zone. You can unblock the files using the property menu in explorer.
See http://www.red-gate.com/messageboard/vi ... hp?t=10462 / comments
This is probably due to some of the files being marked as having come from an untrusted zone. You can unblock the files using the property menu in explorer.
See http://www.red-gate.com/messageboard...
Thanks for trying it, but we only use the COM method in VS2008 and above, so the macro I posted is expected to fail on VS2005. / comments
Thanks for trying it, but we only use the COM method in VS2008 and above, so the macro I posted is expected to fail on VS2005.
Thanks for doing the investigation.
We ought to be logging the failure in the Properties call and I'll open a bug report for that.
We check the "enable just my code" property so that we can be confident that after we have generated pdb files the debugger will start stepping into the decompiled code. / comments
Thanks for doing the investigation.
We ought to be logging the failure in the Properties call and I'll open a bug report for that.
We check the "enable just my code" property so that we can be conf...
Hi.
We try to access a property via COM to determine if JustMyCode is enabled; I imagine that call is failing for some reason.
Could you try running this small piece of Visual Basic in the Macros IDE which makes the same COM calls as our code?
Sub CheckEnableJustMyCode()
Dim props As Properties
props = DTE.Properties("Debugging", "General")
Dim prop As [Property]
prop = props.Item("EnableJustMyCode")
Dim result
result = prop.Value
MsgBox(result)
End Sub
Thanks. / comments
Hi.
We try to access a property via COM to determine if JustMyCode is enabled; I imagine that call is failing for some reason.
Could you try running this small piece of Visual Basic in the Macros I...