# Profile front-end to back-end for dotnet core webapi (not razor)

**URL:** <https://community.miniprofiler.com/t/profile-front-end-to-back-end-for-dotnet-core-webapi-not-razor/631>\
**Category:** .NET\
**Created:** [December 23, 2020, 8:03pm UTC](https://community.miniprofiler.com/t/profile-front-end-to-back-end-for-dotnet-core-webapi-not-razor/631 "2020-12-23T20:03:05Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jcolebrand](https://sea2.discourse-cdn.com/flex016/user_avatar/community.miniprofiler.com/jcolebrand/32/1059_2.png) [@jcolebrand](https://community.miniprofiler.com/u/jcolebrand)\
**Post date:** [December 23, 2020, 8:03pm UTC](https://community.miniprofiler.com/t/profile-front-end-to-back-end-for-dotnet-core-webapi-not-razor/631/1 "2020-12-23T20:03:05Z")

</div>

I wanted to see if there was any community guidance already on how to profile from a dotnet core mvc front-end to back-end for dotnet core webapi (not razor)?

Am I just supposed to put the profiler on the backend and it magically just shows up?

When I do that I don’t see anything carrying across. I’m missing where in the documentation it might give guidance on that.

I know once upon a time there was a way to connect WCF to front-end, wasn’t there?