c# - asp.net mvc read file open



Path To Files Inside Content Folder(ASP.NET MVC) (2)

There something I still do not understand about how the Content folder works in ASP.NET MVC. To make things clearer I have a few questions:

  1. Is the Content folder the root folder? I mean does http://localhost/ point to Content or is it something else?
  2. I have a file named dummyIcon.png inside Content/images/temp folder. How do I locate it from my domain layer (which is a Code Library project)?
  3. What is the best practice of displaying images in ASP.NET MVC? Should I store a path to the image in the database (which I personally prefer), or do I save a byte array and return it to the view?

I found the following links to be helpful within the context of the MVC web application, but I'd still appreciate some answers to the questions posted above. Thank you.

Can an ASP.NET MVC controller return an Image?

how to display image using view and controller by ASP.NET MVC

https://ffff65535.com


1.Is the Content folder the root folder? I mean does http://localhost/ point to Content or is it something else?

No, http://localhost:port/ does not point to content folder. You can access files in content folder through http://localhost:port/content/...

2.I have a file named dummyIcon.png inside Content/images/temp folder. How do I locate it from my domain layer (which is a Code Library project)?

You should be able to access it as http://localhost:port/Content/images/temp/dummyIcon.png

3.What is the best practice of displaying images in ASP.NET MVC? Should I store a path to the image in the database (which I personally prefer), or do I save a byte array and return it to the view?

Where you store the images depends on your application needs. Are these generic images that is used to display application images (icons, company logo, etc).. Then it is best to store them in file system.

If your application deals with images and you work on storing images, manipulation etc, then you may need DB. I think, storing images used on the web application is a overhead.


  1. Anything in the root will point to the root if it is ignored by your routes:

    If you have an image placed on the on the root of your project. Then, say http:://localhost/dummy.ico" will give you a 404, no controller found. Until you do this in your global.asax.cs:

    routes.IgnoreRoute("dummy.ico");
    //you could add wildcards here to match different things
    
  2. From Code if you use says File.Open(); you need the physical path to the file. You get it like this:

    string filePath = Server.MapPath(Url.Content("~/Content/Images/Image.jpg"));
    
  3. It is upto you here, although I would say, putting files into the database makes a lot of sense if you want everything in one place. If you need to move your app around you would just move the data base.

When it comes to file paths, please remember you don't want duplicate file names, so you will have to give each file a GUID and then link it up. It could make sense if you have a large number of files (or large files itself) so you're database won't grow like crazy.

HTH





localhost