Comments
Sort by recent activity
Sorry regarding step one I mistakenly thought this the project Refector was a sample I got from Redgate given the name; Disregard this instead following these instructions
1) In VS2010 create a new project specify the .NET library to be 3.5 _not_ the default 4..0.
2) Add the below code snippet or create your own which references a .NET class library I really don't think it matters.
3) Follow steps 2) through 4 in my original post. You will see the 2nd or 3rd time you use Reflector that DevStudio dies. My suspicion given the circumstance is this has to do with the VS Reflector Addin.
thx
bob
=====================================
using System;
using System.Collections.Generic;
namespace ConsoleApplication1
{
class Program
{
static void Main(string[] args)
{
List<int> l = new List<int>();
}
}
} / comments
Sorry regarding step one I mistakenly thought this the project Refector was a sample I got from Redgate given the name; Disregard this instead following these instructions
1) In VS2010 create a new...
I have tried the current build of Reflector x.399 I am no longer seeing the error regarding the mutex not being able to be opened.
I am also able to decompile and navigate into .NET assembly using the same steps which I mentioned in the orginal post.
Prior to this build I could not unless I was an Admin
thx
bob / comments
I have tried the current build of Reflector x.399 I am no longer seeing the error regarding the mutex not being able to be opened.
I am also able to decompile and navigate into .NET assembly using ...
sorry neglicted to tell you the build of Reflector I'm using 7.0.0.375 / comments
sorry neglicted to tell you the build of Reflector I'm using 7.0.0.375
I don't believe I mentioned this but yes this is 64 bit Win7 I'm running with.
I will check back tomorrow or Thursday, download the update and see whether your fix resolves this issue.
thx
bob / comments
I don't believe I mentioned this but yes this is 64 bit Win7 I'm running with.
I will check back tomorrow or Thursday, download the update and see whether your fix resolves this issue.
thx
bob