Comments
Sort by recent activity
That icon is for a private static variable definition (e.g. the code behind it will be something like "private static string _strFooBar;") / comments
That icon is for a private static variable definition (e.g. the code behind it will be something like "private static string _strFooBar;")
After speaking to Philipee.
The failure occurred when trying to decompile an assembly with a member variable initialised to a lambda expression. This gave a "System.InvalidOperationException: Stack empty" exception message.
The workaround is to decompile the assembly to C# 2.0 or Visual Basic 8.0 (i.e. a language without lambda expressions).
Hope this helps anyone who comes across this error message. / comments
After speaking to Philipee.
The failure occurred when trying to decompile an assembly with a member variable initialised to a lambda expression. This gave a "System.InvalidOperationException: Stack...
What type of application are you trying to debug (a web app / desktop / windows service)?
We have come across this problem on web applications where the multi-threaded version of the garbage collector (serverGC) can cause problems and reverting to the standard workstation garbage collector can often fix this. Please see http://support.microsoft.com/kb/911716 for the instructions on how to change the garbage collector while running the profiling.
As most of the ASP.NET settings can be set in lots of different ".config" files you may also need to check and set the serverGC tag in the "global" web.config in the CONFIG folder of the .NET installation, in Machine.config and the local web.config.
There definitely should be an update available, as the latest version of ANTS Memory Profiler is 5.2.0.49. Quite why it should not find any updates I am not sure, and I apologise for that.
To manually update the program you can download and install the trial edition from our website, this will update your edition to the latest version. / comments
What type of application are you trying to debug (a web app / desktop / windows service)?
We have come across this problem on web applications where the multi-threaded version of the garbage collec...
The two really useful graphs in ANTS when you are searching for this type of problem is the "Clas Reference Explorer" and the "Object Retention Graph".
If you select either the EventHandlerList+ListEntry or the PropertyStore in the "Class List" and then click on "Class Reference Explorer" analysis. This will show you the classes that are referenced or which it is referenced by - so for EventHandlerList+ListEntry you will get the type of EventHandlers that are contained in the EventHandlerLists - this will give you some clues.
If you then select an instance of either the EventHandlerList+ListEntry or the PropertyStore classes in the "Instance List" and then go to the "Object Retention Graph" this will should exactly what is keeping that instance in memory.
There are lots of likely causes and the best way to be sure is to look at the graphs and just gradually work through them.
Glad you are enjoying using our software. / comments
The two really useful graphs in ANTS when you are searching for this type of problem is the "Clas Reference Explorer" and the "Object Retention Graph".
If you select either the EventHandlerList+Lis...
Sorry the forums seem to have cut off the bottom of your logs.
The usual cause of a MSI Error 1603 is actually an error code 2738.
Hopefully if you look down your full logs it will have a line with this error code in, if not could you post the error code. The line you will be looking for will look like:
<date and time>: Product: <name of product> -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is <error code>. The arguments are: <some arguements>
If it is an error code 2738 then it is a problem with a partially disabled VBScript dll.
The solution is to perform the following operation, at the command-prompt, running as adminstrator, type:
cd C:\WINDOWS\system32
REGSVR32.EXE VBSCRIPT.DLL
Once that is done you should get a dialog saying that the DLL was registered successfully.
As you are running a 64-bit version of Windows, you then have to do the virtually the same thing again only this time
cd C:\WINDOWS\SysWOW64
REGSVR32.EXE VBSCRIPT.DLL
In some cases, this is not sufficient, as there is a special case in which the VBScript components are registered in a way that does not allow VBScripts to run from inside a Windows Installer package with elevated privileges. To fix this, look for the following registry keys and delete them if they exists:
HKEY_CURRENT_USER\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}
and (as you are on a 64-bit Windows)
HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{B54F3741-5B07-11cf-A4B0-00AA004A55E8}
Then you will need to re-register the dll (re-run the first above commands)
Hope this helps / comments
Sorry the forums seem to have cut off the bottom of your logs.
The usual cause of a MSI Error 1603 is actually an error code 2738.
Hopefully if you look down your full logs it will have a line with...
Thanks for the posts. We are listening and we are sorry - the next version of Reflector currently in EAP asks the user before adding the Visual Studio add-in.
It is nice and easy to remove the add-in:
- Run .NET Reflector V6.1 and go to "Tools" > "Integration options" and then uncheck the Visual Studio integration
Yes we should have made it so that it took 5 clicks to add the add-in, rather than 5 clicks to remove the add-in, but we didn't. / comments
Thanks for the posts. We are listening and we are sorry - the next version of Reflector currently in EAP asks the user before adding the Visual Studio add-in.
It is nice and easy to remove the add-...