User profile for sf

@Russell D I don't know why you didn't find a ticket, I had numerous exchanges on the subject, spanning month. Anyway, I did post the workaround is my previous message, it is: "change one default option in VS Project Properties, Build, Advanced and select "Full" for Debugging Information" For the rest: I just gave you my opinion, as a recurring paying user for something like 10 years or so now, you do what you want with it, no problem, it's you business, I guess you're not up to +/- 1 customer. I just notice that you didn't address the issue described here since May, 2019. The "new csproj format" is no longer that new, and other .Net profilers around have no issue with it. Release note says: "Portable PDB support" as a new Major Feature of Version 10.0, back June 6, 2018. From the experiences reported here, it doesn't work. And this was the last significant feature you added, the highlight of Version 10.0 Now, it's up to you to consider whether my input on your product worth paying attention or not. On my side I'll judge whether I wish to continue paying for it or not. Regards. / comments

@Russell D I don't know why you didn't find a ticket, I had numerous exchanges on the subject, spanning month. Anyway, I did post the workaround is my previous message, it is:"change one default o...

0 votes

Thanks for having looked into this, I didn't realize I used 2 different emails... Indeed: creating a shareable, stripped down version of my solution that still exhibits the problem was too much time consuming, I was not able to fit this into my work days within a reasonable time frame. Maybe @SmithJunior82 could help here. / comments

Thanks for having looked into this, I didn't realize I used 2 different emails...Indeed: creating a shareable, stripped down version of my solution that still exhibits the problem was too much time...

0 votes

Yes, quite disappointing indeed. I have been in contact with the support team, and one possible options seems to be to change one default option in VS Project Properties, Build, Advanced and select "Full" for Debugging Information. This is supposed to create more complete .pdb files that ANTS is happy with... I have been able to validate that this "solves" the issue, but it may not be practical for other reasons (like: you have 1000 projects, or you cannot use "full" for a good reason). I am also not aware of any potential drawback of using "Full", so use it at your own risk. I did not test it with Core 3.0 specifically, only .Net framework. I don't know why the support team did not post this workaround here, or just.. replied. Basically, I am more or less not using ANTS anymore because of this, which is quite irritating since I paid for a 3 years license not so long ago. My feeling is that ANTS did not receive any significant update for years now, nor feature nor simple updates for supporting new technologies. It was once the best, way above the others, but now it looks more like a frozen old piece of software, when others are still improving their stuff at a high pace. / comments

Yes, quite disappointing indeed. I have been in contact with the support team, and one possible options seems to be to change one default option in VS Project Properties, Build, Advanced and select...

0 votes

Hi James, Thank you, your latest build seems to be robust against this issue, this is good! Thanks a lot. / comments

Hi James, Thank you, your latest build seems to be robust against this issue, this is good! Thanks a lot.

0 votes

Hi James, I spent some time evaluating your latest release (8.2). While it doesn't crash anymore with our code and all latest .Net updates, we are unfortunately not going to upgrade from 4/5 to 8.2. The reason is that is it incredibly slow to operate: while the performance decrease of the application under test seems to be slightly better than with 4/5, the 8.2 release is almost unusable: it takes ages to expand one line, or even to get the first method tree after a range has been selected. And overall the Method Tree UI seems to be so "asynchronous" that its hard to understand what's happening: for instance: I select a range and wait for the tree to display. Then I select another range: I can see that something is happening since CPU usage goes up, but there is no visual feedback on the tree. So I am confused about which range this current tree corresponds to. After some time, the tree is suddenly refreshed. Needless to say that if I am not patient enough and select another range before refreshing, or try to expand a line, or select another thread, things get worse and worse. Our computers are not super fast, ok, but we never had these kind of issues with 4 or 5: the UI is responsive and the time for getting the whole tree after selecting a range is reasonable. I have to say I am disappointed by this: I was expecting some great improvements when comparing 8 to 4, but it's not the case: the usability is so bad that I don't want to spend more time exploring potentially new great features. I am sorry for this bad comment. But we are not going to upgrade our versions as long as global performances of the UI are not improved. This means that in order to solve the crash issue, I spent some time rewriting all code parts that are crashing version 4/5, based on your May 16 comment, so thanks a lot for providing these insight. Again, sorry for this bad comment. We all love ANTS Profiler concept and reliability but I don't know what happened in between version 5 and 8 to render it unusable on our machines... Hopefully you are aware of this issue and will fix it at some points. Best regards. / comments

Hi James, I spent some time evaluating your latest release (8.2). While it doesn't crash anymore with our code and all latest .Net updates, we are unfortunately not going to upgrade from 4/5 to 8.2...

0 votes

How can we help you today?

sf

Comments