Ajax POST请求浮点值传递异常求助：无法正常显示浮点值

Hey there, let's work through why you're struggling to get float values properly passed from your frontend Ajax to the backend controller. Looking at your code, I spot a couple of key issues that are causing this problem—let's break them down and fix them step by step.

问题根源分析 #

Your current Ajax request sends data in the default form-urlencoded format, not JSON, even if you tried JSON.stringify() (it looks like you didn't apply it correctly in the code you shared). When passing float values as plain strings this way, the backend's Convert.ToDouble() can fail if there's a mismatch between the frontend's decimal separator (like .) and the server's regional settings (e.g., some regions use ,). Additionally, manually reading values from Request is error-prone compared to using ASP.NET's built-in model binding.

解决方案 #

1. 修正前端Ajax请求，正确序列化JSON #

Update your Ajax code to properly send JSON data, which ensures float values are serialized correctly and the backend can parse them reliably:

$.ajax({
    url: "/Home/GetItemsByFilter",
    method: "POST",
    contentType: "application/json; charset=utf-8", // 关键：指定JSON内容类型
    data: JSON.stringify({ // 用JSON.stringify序列化数据
        CategoryId: '',
        SubCategoryId: '',
        SubSubCategoryId: $("#sub_sub_category_id").val(),
        MinPrice: parseFloat($("#min_price").val()), // 先转成浮点型再序列化
        MaxPrice: parseFloat($("#max_price").val()),
        BrandId: $("#brand").val(),
        OrderBy: $("#price_direction").val(),
        PageNumber: currentPage,
        PageSize: 18
    }),
    error: function (response) {
        alert("There is something wrong!!!");
    }
});

Note: Using parseFloat() on the price inputs ensures we're sending actual numeric values instead of strings, which avoids unnecessary parsing issues on the backend.

2. 使用模型绑定替代直接读取Request #

Instead of manually pulling values from Request, create a view model class and let ASP.NET's model binding handle the conversion automatically. This is more maintainable and less error-prone:

创建ViewModel类

public class ItemFilterViewModel
{
    public string CategoryId { get; set; }
    public string SubCategoryId { get; set; }
    public string SubSubCategoryId { get; set; }
    public double MinPrice { get; set; }
    public double MaxPrice { get; set; }
    public double ActualMaxPrice { get; set; } // 确保前端也传递这个值
    public string BrandId { get; set; }
    public string OrderBy { get; set; }
    public int PageNumber { get; set; }
    public int PageSize { get; set; }
}

更新控制器方法

[HttpPost]
public ActionResult GetItemsByFilter(ItemFilterViewModel filter)
{
    // 现在可以直接使用filter.MinPrice、filter.MaxPrice等，它们已经是double类型了
    // 你的业务逻辑代码...

    // 示例：设置ViewBag的代码可以简化
    var ItemList = // 你的数据查询逻辑
    ViewBag.MinPrice = ItemList.Min(m => m.PriceAfterDiscount); // 若PriceAfterDiscount已是数值类型，无需Convert.ToDouble
    ViewBag.MaxPrice = ItemList.Max(m => m.PriceAfterDiscount);

    return View(); // 或者返回JSON等结果
}

Side note: If PriceAfterDiscount is already a numeric type (like decimal or double), you don't need Convert.ToDouble() here—just use the value directly.

3. 处理区域设置问题（可选） #

If your application needs to support different decimal separators (e.g., users entering 123,45 instead of 123.45), you can specify the culture when parsing, or configure your app to use a specific culture globally. For example, enforcing en-US format for manual conversion:

// 仅在必须手动读取Request值时使用（优先推荐模型绑定）
double MinPrice = Convert.ToDouble(Request["MinPrice"], System.Globalization.CultureInfo.InvariantCulture);

为什么之前的JSON.stringify()没用？ #

In your original code, you didn't set the contentType header to application/json, so even if you had used JSON.stringify(), the backend wouldn't parse it as JSON—it would still treat it as form data. By adding both contentType and JSON.stringify(), we ensure the data is sent and parsed correctly.

内容的提问来源于stack exchange，提问作者anik saha