"Ravi Ambros Wallau" wrote:

> Hi,
>     I am using Enterprise Library (June 2005) and, in the older version, we
> could discover a stored procedure parameters set without calling it. It
> seems to me that it's not possible to discover a stored procedure parameters
> in this new version. I didn't want to use the ADO.NET DeriveParameters
> method, because it's not cached.
>     Is there any way to that (for reference, the old method was
> SqlHelperParameterCache.GetSpParameterSet)? I really need to do that,
> because the parameters are bind using reflection....
>     Good luck for me,
>
> --
> Ravi Wallau
> nospam@nospam.org
>
>
>

"Cowboy (Gregory A. Beamer) - MVP" <NoSpamMgbworld@comcast.netNoSpamM> wrote
in message news:55520B1D-2C3E-4903-953D-0945DD606160@microsoft.com...
> Discovery methods
> Database.cs - DiscoverParameters()
> Database.cs - DeriveParameters()
>
> You will also find database specific implementations. This does not cache
> the implementation, but you can create your own cache class and call it
> for
> params, if that is your goal.
>
> --
> Gregory A. Beamer
> MVP; MCP: +I, SE, SD, DBA
>
> ***************************
> Think Outside the Box!
> ***************************
>
>
> "Ravi Ambros Wallau" wrote:
>
>> Hi,
>>     I am using Enterprise Library (June 2005) and, in the older version,
>> we
>> could discover a stored procedure parameters set without calling it. It
>> seems to me that it's not possible to discover a stored procedure
>> parameters
>> in this new version. I didn't want to use the ADO.NET DeriveParameters
>> method, because it's not cached.
>>     Is there any way to that (for reference, the old method was
>> SqlHelperParameterCache.GetSpParameterSet)? I really need to do that,
>> because the parameters are bind using reflection....
>>     Good luck for me,
>>
>> --
>> Ravi Wallau
>> nospam@nospam.org
>>
>>
>>