Web Development

@Html.CheckBox("IncludeClosed", false, new { onChange = "this.IncludeClosed.submit()"})

@using (Html.BeginForm("Index","Chargeback",FormMethod.Get,new { id = "IncludeClosed"}))

@Html.CheckBox("IncludeClosed", false, new { onChange = "document.getElementById('IncludeClosed').submit()"})

@using (Html.BeginForm("Index", "Chargeback"))
{
    @Html.CheckBox("IncludeClosed", false, new { onChange = "this.form.submit()" })

Quote:

specify that I want unit tests,

Quote:

I know I can create a new project

Afzaal Ahmad Zeeshan wrote:

And then bring the entire code base in that new project? Doesn't seem legit, but you can easily add a new project in the solution, and connect that (new testing) project with your existing web application as a reference (MVC would be a dll). Then using the content from your MVC, you can run tests on them.

Quote:

When you create a MVC project with unit test turned on

Quote:

nuget threw errors at me.

Afzaal Ahmad Zeeshan wrote:

But you are not going to be using a new project, right? I might have misunderstood, but I thought your boss wanted you to integrate this in an existing project.

1. Enable FRT:
   
   1. Open IIS Manager and select your site;
   2. On the right-hand side, click on "Failed request tracing..." under "Configure";
   3. Tick the "Enabled" box;
   4. Click "OK";
2. Configure a tracing rule for 404 errors:
   
   1. In the main pane, double-click "Failed request tracing rules";
   2. On the RHS, click "Add...", and set up the rule:
      
      • All content - Next
      • Status codes: 404 - Next
      • Leave all providers ticked - Finish
3. Generate an error and view the log file:
   
   1. Open the URL which isn't working in a browser;
   2. Open the %systemdrive%\inetpub\logs\FailedReqLogFiles\... folder in Windows Explorer;
   3. Open the XML file in Internet Explorer;

Richard Deeming wrote:

and you're not using .NET Core.

Mycroft Holmes wrote:

why the caveat