Comments
Sort by recent activity
I'd generate a named list of 4.0 assemblies.
File/Open List, Add, "Framework4", double-click the newly named list and choose 4.0 assemblies to populate it with.
You can go to open list to switch between different named sets of assemblies. / comments
I'd generate a named list of 4.0 assemblies.
File/Open List, Add, "Framework4", double-click the newly named list and choose 4.0 assemblies to populate it with.
You can go to open list to switch be...
You can reset the "default list" by
First selecting it, using file/open list, --Default--.
Then select the assemblies in the list one by one and delete them
Then select it again by file/open list, --Default--
This will then prompt for which framework version to fill the default list with, so you can fill with 4.0 again
ie the trick is that opening an empty list will cause a prompt to appear asking which assemblies to fill the list with. / comments
You can reset the "default list" by
First selecting it, using file/open list, --Default--.
Then select the assemblies in the list one by one and delete them
Then select it again by file/open list, ...
Hi.
The class you are seeing is generated by the C# compiler for an Enumerator - it generates a state machine which generates items when the MoveNext method is called.
It seems to be going through the StyleItems and returning those that aren't Product.ExcludedFromWeb.
We have an outstanding bug report about trying to generate C# code from the state machine, but this is quite complicated. I don't know of any add-ins that will do this. / comments
Hi.
The class you are seeing is generated by the C# compiler for an Enumerator - it generates a state machine which generates items when the MoveNext method is called.
It seems to be going through ...
Hi.
The code that Reflector generates isn't always going to work without setting up various references on the project.
In the case of Reflector Pro, the code is more there for the purposes of showing you where you are in the control flow rather than as a means of building new versions of the target assembly. / comments
Hi.
The code that Reflector generates isn't always going to work without setting up various references on the project.
In the case of Reflector Pro, the code is more there for the purposes of showi...
Hi.
The Reference Assemblies contain the metadata but not the IL code and hence Reflector will show them as blank. You need to reference the real assemblies in the GAC to see the code.
File>Open Cache should find the correct version. / comments
Hi.
The Reference Assemblies contain the metadata but not the IL code and hence Reflector will show them as blank. You need to reference the real assemblies in the GAC to see the code.
File>Open Ca...
Hi.
The add-ins are installed by placing a RedGate.Reflector.Addin file in the appropriate Visual Studio addins directory. For example, for 2005, my addin file is in
C:\Profiles\clive.tong\My Documents\Visual Studio 2005\Addins
You can simply remove that file to delete the add-in from Visual Studio. / comments
Hi.
The add-ins are installed by placing a RedGate.Reflector.Addin file in the appropriate Visual Studio addins directory. For example, for 2005, my addin file is in
C:\Profiles\clive.tong\My Docum...
JohaViss wrote:
I added the following line:
<supportedRuntime version="v4.0.30319"/> <!-- 4.0 RTM -->
And now everything works. [image]
I think that you have to add this line for the next release.
Thanks for investigating that. That line will is now in the app.config file. / comments
JohaViss wrote:
I added the following line:
<supportedRuntime version="v4.0.30319"/> <!-- 4.0 RTM -->
And now everything works.
I think that you have to add this line for the next release.
...
Ok - I only see the error here if I load the dll with the old name.
In the Add-ins dialog that is raised on failure, the location line can be double-clicked at which point data from the exception will be displayed. For example, when I load the dll I get
System.InvalidOperationException: Add-in contains no packages. / comments
Ok - I only see the error here if I load the dll with the old name.
In the Add-ins dialog that is raised on failure, the location line can be double-clicked at which point data from the exception w...
I should have mentioned that it is throwing inside the HandleItem(AssemblyDefinition) method.
This method seems to have been patched in version 1.1 of the add-in (on SourceForge) to handle null values, though I couldn't reproduce the error here. / comments
I should have mentioned that it is throwing inside the HandleItem(AssemblyDefinition) method.
This method seems to have been patched in version 1.1 of the add-in (on SourceForge) to handle null val...
In the 1.1 version the addin for Reflector is contained in an assembly named Reflexil.Reflector.dll instead of the previous Reflexil.dll.
Reflector looks for a type implementing IPackage to identity an add-in. In 1.1, Reflexil.dll no longer references reflector.exe and hence does not implement such an interface. / comments
In the 1.1 version the addin for Reflector is contained in an assembly named Reflexil.Reflector.dll instead of the previous Reflexil.dll.
Reflector looks for a type implementing IPackage to identit...