Comments
Sort by recent activity
Hi again,
Is Red Gate planning to address this issue? / comments
Hi again,
Is Red Gate planning to address this issue?
Thank you.
I am trying to narrow down the code that actually trigger the issue, but I did not succeed so far.
It is related to constructing an object that has a generic parameters, but I guess that the type actually used is relevant...
I'll keep you up to date. / comments
Thank you.
I am trying to narrow down the code that actually trigger the issue, but I did not succeed so far.
It is related to constructing an object that has a generic parameters, but I guess that...
Hi James,
Thanks for the quick reply. We don't use AllowPartiallyTrustedCallers attribute at all.
Well, I did one additional test: I restored an old project from an archive, dated September 24, 2012.
At that time we were still using VS2005, and for sure I was then able to profile this project.
I recompiled it (with VS2005) and tried to profile it with my good old ANTS v5 and guess what: I got the very same exception at the exact same place in the code (which indeed hasn't change)!
So: same code, same ANTS, VS version ruled out.. I think a windows update might be the root cause. I am now at .NET: 2.0.50727.3643
What should I do? Give you my project is of course not possible and creating a test project I can share may take some time...
Any idea? / comments
Hi James,
Thanks for the quick reply. We don't use AllowPartiallyTrustedCallers attribute at all.
Well, I did one additional test: I restored an old project from an archive, dated September 24, 201...
Well, of course that's the thing to do... I just hoped you'll have some good idea to save me from this time consuming task ;-)
Anyway, I found the nasty update: it is named: KB2742596 and it's the before last .NET Framework 2.0 Service Pack 2 critical update. I installed it around January 18, 2013.
To figure this out I first removed the 2 last updates of this kind (the last one was installed this week): everything went right (not even had to rebuild my solution): no exception during profiling. I reinstalled KB2742596: crash.
So, now at least I can work, but I have the feeling that this situation is not very stable: should I refuse any critical update from now on? Doesn't sound good.
Do you have any comment? / comments
Well, of course that's the thing to do... I just hoped you'll have some good idea to save me from this time consuming task ;-)
Anyway, I found the nasty update: it is named: KB2742596 and it's the ...
Hi,
I am experiencing the exact same issue. I tested with ANTS Profiler v4.last v5.last et v7.last, on two different machines, behavior is exactly the same.
My project is WinForm based, .Net 2.0, built using VS 20102, I am under Win XP.
What is really strange is that last time I profiled the same application (a few weeks ago on the same installation) I had no issue at all with my v5.last (which is my regular version). The source code was modified since then, of course, but we didn't add new library or made serious architecture modifications.
More precisely, the code where the exception now happen every time has not been changed for ages, and apart from using generics, I don't see anything particular here. I am pretty sure the call stack was the same last time I successfully profiled.
I tried to thing of what may have changed in my configuration, but I would tend to say nothing but automatic Windows Update stuff.
Could it be that an update to .Net, for instance, causes this issue?
Thanks in advance for your help, I need a way to profile my application with line details... / comments
Hi,
I am experiencing the exact same issue. I tested with ANTS Profiler v4.last v5.last et v7.last, on two different machines, behavior is exactly the same.
My project is WinForm based, .Net 2.0, b...