Bootstrap image slider in MVC breaks when I try to pass all files from folder in it

Question

1.00/5 (1 vote)

See more:

Razor

@{
    ViewBag.Title = "GalerijaIndex";
    Layout = "~/Views/Shared/_GalerijaLayout.cshtml";
}

<div id="mycarousel" class="carousel slide" data-ride="carousel" style="margin-top: -15px">

    <ol class="carousel-indicators">
        <li data-target="#mycarousel" data-slide-to="0" class="active"></li>
        <li data-target="#mycarousel" data-slide-to="1"></li>
        <li data-target="#mycarousel" data-slide-to="2"></li>
    </ol>
    <div class="carousel-inner" role="listbox">
        <div class="item active">
            <img src="~/Content/First/Music1.jpg" />
        </div>
        @{
            string source = "~/Content/Images/";
            string[] fileEntries = Directory.GetFiles(source);
            foreach (var i in fileEntries)
            {
                <div class="item">
                    <img src="~/Content/Images/@{Path.GetFileName(i)}" />
                </div>
             }
        }
             }


    <a class="left carousel-control" href="#mycarousel" role="button" data-slide="prev">
        <span class="glyphicon glyphicon-chevron-left" aria-hidden="true"></span>
        <span class="sr-only">Prethodna</span>
    </a>

    <a class="right carousel-control" href="#mycarousel" role="button" data-slide="next">
        <span class="glyphicon glyphicon-chevron-right" aria-hidden="true"></span>
        <span class="sr-only">Slijedeća</span>
    </a>
</div>

The goal is to populate slider dynamically with all images in "~Content/Images/" folder, so that it can display them. All the logic is here on View, yet I can't figure out why I'm getting 500 error.

What I have tried:

I've tried what I known, but I have no idea what is wrong. Everything else works fine. I have tried pass value to it via ViewBag from controller, same thing;

Posted 3-Nov-16 20:46pm

1suli0

Updated 4-Nov-16 4:40am

v4

Add a Solution

Comments

Richard Deeming 4-Nov-16 10:03am

Neither do we, because you haven't told us what the problem is.

Click "Improve question" and update your question with a proper description of the problem. Include the full details of any errors.

1suli0 4-Nov-16 10:41am

I'm sorry sir, won't happen again.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Richard Deeming · Answer 1 · 2016-11-04T04:34:00

You still haven't told us what the error is, but at a guess, it probably comes from these two lines:

Quote:
string source = "~/Content/Images/";
string[] fileEntries = Directory.GetFiles(source);

The Directory.GetFiles method expects the physical path to the folder. You are passing in an app-relative virtual path. Since the GetFiles method knows nothing about ASP.NET applications, you will most likely get a DirectoryNotFoundException.

To fix that, you need to map the virtual path to a physical path:

C#

string source = "~/Content/Images/";
string physicalPath = System.Web.Hosting.HostingEnvironment.MapPath(source);
string[] fileEntries = Directory.GetFiles(physicalPath);

NB: This sort of code really belongs in the controller, not the view.