# Profiling BL code

**URL:** <https://community.miniprofiler.com/t/profiling-bl-code/126>\
**Category:** uncategorized\
**Created:** [May 28, 2012, 3:41am UTC](https://community.miniprofiler.com/t/profiling-bl-code/126 "2012-05-28T03:41:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Stu\_Sklinar](https://avatars.discourse-cdn.com/v4/letter/s/46a35a/32.png) [@Stu\_Sklinar](https://community.miniprofiler.com/u/Stu_Sklinar)\
**Post date:** [May 28, 2012, 3:41am UTC](https://community.miniprofiler.com/t/profiling-bl-code/126/1 "2012-05-28T03:41:14Z")

</div>

Hi guys,

We’re wanting to use MiniProfiler throughout our app - but after checking the references of the MiniProfiler.DLL I notice it references MVC & [System.Web](http://System.Web) - which we obviously would prefer to not reference further down our chain - where it isn’t required…

Most of our code is implemented past our MVC layer, of which our MVC layer is very light-weight

I guess the question is, down the line are they to be split out to separate the logic and Web References?

Or can other suggestions be made on how we can profile performance at our business level?

Thanks

---

<div class="post-metadata">

**Author:** ![sam](https://sea2.discourse-cdn.com/flex016/user_avatar/community.miniprofiler.com/sam/32/377_2.png) [@sam](https://community.miniprofiler.com/u/sam)\
**Post date:** [May 28, 2012, 1:49pm UTC](https://community.miniprofiler.com/t/profiling-bl-code/126/2 "2012-05-28T13:49:46Z")

</div>

MiniProfiler has a very light dependency on MVC, in particular the WCF profiling bits hook up a different `BaseProfilerProvider`, all you need to do is implement a class that takes care of that and an `IStorage` provider and you have stripped the web dependency.
