Latest version 2.5.1 return 0 for DapperParameters output

[vyvo2412]

Hello, we recently updated our nuget packages and we noticed some issue with InterpolatedSql's latest version. When I tried to run a stored procedure to insert data, the output id kept returning 0. When I run the stored procedure manually, I get the proper output id returned. I ended up downgrading back to 2.5.0 version to fix the issue.

[Drizin]

@vyvo2412 Can you send an example of what you're doing?

This seems to be working fine with latest package:
https://github.com/Drizin/InterpolatedSql/blob/main/src/InterpolatedSql.Dapper.Tests/SqlBuilderTests.cs#L219-L227

This is the procedure:

CREATE PROCEDURE [sp_TestOutput]
    @Input1 [int], 
    @Output1 [int] OUTPUT
AS
BEGIN
	SET @Output1 = 2
END;

[vyvo2412]

I have an extension method to get the output parameter

public static T GetOutputParameter<T>(this SqlBuilder commandBuilder, string parameterName)
{
    return commandBuilder.Build().DapperParameters.Get<T>(parameterName);
}

This is my stored procedure

ALTER PROC dbo.sp_TestInsert
    @Test_Id INT OUTPUT,
    @Test_Text VARCHAR(MAX)
AS
BEGIN
    SET NOCOUNT ON;

    DECLARE @Id TABLE
    (
        Id INT NOT NULL
    );

    INSERT INTO dbo.Test
    (
        Test_Text
    )
    OUTPUT
        Inserted.Test_Id
    INTO @Id
    VALUES
    (
        @Test_Text
    );

    SELECT
        @Test_Id = Id
    FROM @Id;
END;
GO

When I ran my stored procedure manually it returned the @Test_Id properly. Not sure how the id returning on DapperParameters was 0

[celluj34]

Could this be related to us calling .Build() after executing the procedure?

[Drizin]

Could this be related to us calling .Build() after executing the procedure?

Yes, if you're calling Build() more than once then probably it's not what you're supposed to be doing