Ok, maybe I'm skipping a step here, but I swear I had Eqatec profiling things just fine in ASP.NET 2.0.
We upgraded our solution to ASP.NET 4, it works fine. Then I went through the typical steps:
- Built the solution in VS 2010
- Ran Eqatec and pointed it at the apps bin folder
- pick my 3 DLLs
- Click build, I have the output dir set to $(AppData) so it just adds the files to apps bin dir
- ran webdev.webserver40.exe with the port and the path
- navigate firefox to the website on my local machine
But now it's throwing weird errors saying that things in the machine level web.config can't be found. I dropped a copy of the web.config into the bin directory, and then it just complains about some of the tags in that file.
Is there an extra step I need to take here to make this work?
EDIT: A guy suggested that it may be a 64-bit issue. We run our app in 64 but, Equatec runs in 32 bit. Could that be a factor?