Comments
Sort by recent activity
Hi Jon,
Those files are auto-generated by the VB compiler, and then deleted again after compilation, I believe. Apparently they contain the form initialisation code, so if you're running a Winforms application with a relatively complex UI, that could explain it.
Sorry not to help you out with that more - it's not something we can easily get at, but as you say, can take time to execute.
Robert / comments
Hi Jon,
Those files are auto-generated by the VB compiler, and then deleted again after compilation, I believe. Apparently they contain the form initialisation code, so if you're running a Winforms...
Hi,
Yes, this is the case - or, more specifically, you will only see source code if there is a PDB file associated with the module you're looking at. By default these are generated for debug builds, but not for release builds.
Thanks,
Rob / comments
Hi,
Yes, this is the case - or, more specifically, you will only see source code if there is a PDB file associated with the module you're looking at. By default these are generated for debug builds...
Hi,
Just to clarify, if you're running IIS6 on WinXP, does this mean you're running WinXP 64bit edition? (I don't think IIS6 is available for XP 32bit)
If so, I'm afraid we don't support applications running in 64-bit mode at the moment - this is on the cards for the next release of ANTS.
If you're trying to profile a normal desktop application on a 64-bit machine, it is possible to target it for a 32-bit processor, at which point even if you run it on a 64-bit OS, you will be able to profile it. However, it doesn't appear to be possible to set this CPU target for web applications.
Rob / comments
Hi,
Just to clarify, if you're running IIS6 on WinXP, does this mean you're running WinXP 64bit edition? (I don't think IIS6 is available for XP 32bit)
If so, I'm afraid we don't support applicatio...
OK, no problem. I think in this case you seem to be having a very similar problem to the one being discussed on this thread. It might be worth keeping an eye on that one, and possibly even having a look using Process Explorer if you have the time.
Have you ever managed to successfully profile an ASP.NET application, or has it just stopped working with recent updates or changes?
Rob / comments
OK, no problem. I think in this case you seem to be having a very similar problem to the one being discussed on this thread. It might be worth keeping an eye on that one, and possibly even having a...
Hi Joe,
I'd just like to confirm one thing with you, if possible. Assuming you're running IIS6 in normal mode (rather than IIS5 Isolation Mode), when you start profiling it should pop up a copy of Internet Explorer directed at the site you are profiling.
You might have noticed that this is actually on a different port - I think 8013 by default. Could you confirm that when browsing through your web application, you remain on that port, rather than somehow reverting back to port 80?
Many thanks,
Rob / comments
Hi Joe,
I'd just like to confirm one thing with you, if possible. Assuming you're running IIS6 in normal mode (rather than IIS5 Isolation Mode), when you start profiling it should pop up a copy of ...
Hi Stuart,
Are you seeing this on version 2 or version 3 of ANTS Profiler? If you're on V2, I suggest upgrading, as this will probably fix it.
Regards,
Robert / comments
Hi Stuart,
Are you seeing this on version 2 or version 3 of ANTS Profiler? If you're on V2, I suggest upgrading, as this will probably fix it.
Regards,
Robert
Hi Will,
Thanks for investigating some more.
With the current version of the class library (that which gives you the error), can you try profiling without VS / VWD open, and confirm that you still have problems?
In case you're wondering, the reason I asked you to try in fast mode is that when running in fast mode, we don't add instrumentation to the code. This removes one possible cause of errors, so it's usually a good first check for us.
Rob / comments
Hi Will,
Thanks for investigating some more.
With the current version of the class library (that which gives you the error), can you try profiling without VS / VWD open, and confirm that you still ...
Hi Will,
Are you seeing this on ANTS Profiler 3 or 2.7?
If 2.7, I'd highly recommend upgrading to version 3 - we fixed a few things that may have lead to this previously.
If you're on 3 already, then I'm surprised you're seeing it. Have you tried profiling in Fast Mode, and if so, do you still get the error?
Thanks,
Robert / comments
Hi Will,
Are you seeing this on ANTS Profiler 3 or 2.7?
If 2.7, I'd highly recommend upgrading to version 3 - we fixed a few things that may have lead to this previously.
If you're on 3 already, th...
As a largely off-topic reply (nothing to do with SA - I've leave you in Brian's capable hands there!), we used to use Vault at Red Gate, and CruiseControl.NET seemed to talk to it nicely. There's a CC.NET plug-in on the SourceGear site: <http://www.sourcegear.com/downloads.html>
I'm not sure CC.NET is particularly actively maintained nowadays, but it's served us relatively well in the past, with a few tweaks here and there!
Hope that helps!
Rob / comments
As a largely off-topic reply (nothing to do with SA - I've leave you in Brian's capable hands there!), we used to use Vault at Red Gate, and CruiseControl.NET seemed to talk to it nicely. There's a...
Just to follow up on that a bit further: the reason SQL Search doesn't support SQL Server 2000 is that the way metadata is stored changed significantly between 2000 and 2005.
SQL Server 2000 used real tables dbo.sysobjects, dbo.syscolumns and friends, whereas 2005 and later uses the views sys.objects, sys.columns (and many others) which have a rather different schema.
It'd therefore be a significant amount of work to populate SQL Search's internal object model from the 2000-style tables.
Many thanks,
Rob / comments
Just to follow up on that a bit further: the reason SQL Search doesn't support SQL Server 2000 is that the way metadata is stored changed significantly between 2000 and 2005.
SQL Server 2000 used r...