How To Get WebRootPath of .Net Core Web API From .Net Core Application

Discover how to efficiently retrieve the `WebRootPath` for your .Net Core Web API from another .Net Core Web Application, ensuring smooth functionality in your image upload and retrieval process.
---

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: How To Get WebRootPath of .Net Core Web API From .Net Core Application?

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
How To Get WebRootPath of .Net Core Web API From .Net Core Application

When developing applications in .Net Core, particularly when working with a Web API and a client Web Application within the same solution, you might face challenges in managing file paths. One common scenario involves uploading and retrieving images where you need to fetch the WebRootPath of the .Net Core Web API from your application.

In this post, we will explore how to effectively get the correct path for accessing images stored in your Web API project when called from a separate .Net Core Web Application.

The Problem

Imagine you have a Web API service responsible for uploading profile photos into a specific folder called Uploads. This service works perfectly, but when you retrieve images from the API, the returned paths point to the Web Application instead of the Web API. This discrepancy results in errors because the actual images reside in the API's Uploads directory rather than in the Web Application's structure.

Example Scenario

Here is a simplified example of what the code might look like for retrieving the user’s profile information, which includes the image path:

[[See Video to Reveal this Text or Code Snippet]]

As you can see, the path construction here results in referring to the application structure, which doesn’t contain the actual uploaded files.

The Solution

To resolve this issue, we can create a helper class within your repository that statically holds the base URL of your Web API. This way, whenever you need to retrieve files from the API, you can reference this URL. Here's how you can do it:

Step 1: Create a Helper Class

In your Repository Project, create a folder named Helper.

[[See Video to Reveal this Text or Code Snippet]]

Step 2: Use the Helper Class in Your API

Now, modify the method that retrieves the contact information to utilize this helper for creating the image URL correctly:

[[See Video to Reveal this Text or Code Snippet]]

Step 3: Configure Static Files

[[See Video to Reveal this Text or Code Snippet]]

Conclusion

By following these steps, you ensure that your .Net Core Web Application can correctly retrieve images from the .Net Core Web API. Now, whenever you create or access images, you'll have the accurate context and path for your application's architecture. This approach not only simplifies path management but also enhances the overall functionality between your Web API and Web Application.

Feel free to comment below if you have any questions or further improvements regarding this implementation!