Hi,
If IronWASP works properly on
demo.testfire.net then .NET framework and other dependencies are properly installed.
The effectiveness of the crawler depends on a number of factors. If the site has a lot of Ajax content then the crawler generally does a poor job.
Another common issue is when the home page performs a redirect.
For example if I enter
google.com in my browser it will eventually get redirected to
https://www.google.co.in. This domain is different than the one I entered earlier so the crawler consider it to be out of scope and does not proceed further. The solution in cases like this is to enter the final url in IronWASP (eg:
https://www.google.co.in) rather than the initial one.
Good news is that I am currently working on a new crawler that handles Ajax heavy sites extremely well. Also the next version will have a login recording mechanism so you won't have to create session plugins in most cases. Hopefully these features should be made public within a week's time if development goes as per plan.
I will drop you a line when the new version is released.
Thanks,
Lava