1

I've got a weird issue that seems to be slowing down my project. I installed the Ninject NamedScope extension into my project, but later found out I didn't need it and removed it. However, when I run the project at the bottom of visual studio it tells me loading symbols for Ninject.Extensions.NamedScope, and then it tries to look for them quickly in various places which seems to be make my site pretty slow.

I've searched my entire solution for any references to NamedScope, nothing. I've checked my packages.config, nothing. I've checked the references, not there. I've even checked the .dlls in the bin folder, not there either.

So why is it trying to load symbols from something I removed and how can I get it to stop? It's noticeably slowed down my page load times.

Here are some pictures to show what occurs every page request in visual studio when debugging:

enter image description here

enter image description here

So why the heck is it trying to look in Windows\dll for this extension? When I search for any reference to NamedScope in the entire solution I get this:

enter image description here

Anyone have any idea??

SventoryMang
  • 10,275
  • 15
  • 70
  • 113

1 Answers1

3

I had a similar issue. It was caused by a stale .dll and .config in my bin folder . (I had renamed the Output assembly earlier ) Deleting the files resolved this issue.

Might help.

Steven
  • 98
  • 1
  • 8
  • Deleted the entire bin folder and this fixed it. The weird thing is, the modify date on the .dll.config file didn't change (3 months ago, before I added/removed the extension), but it still fixed it. – SventoryMang Sep 05 '13 at 16:19
  • Not quite related but worth mentioning, perhaps: In one case, removing references from my main project (to other projects in the solution) within Visual Studio *didn't actually remove the references from the `.csproj` file itself.* So when I would delete the `bin` directory and rebuild the solution the DLLs would simply be copied back in. That's something to check if you've already deleted the `bin`folder, and your old DLLs keep coming back. – Brian Lacy May 04 '16 at 21:29