Hi Julian,
You might also want to evaluate NVelocity (a .NET port of the original Java tool).
It's free.
It comes with it's own template language called VTL. I've used it before and it is
very good.
Personally I'd prefer to do the sort of templating substitution you're talking about
using
NVelo
You can call ANY method you wan using delegates:
public delegate int ExecuteNonQueryDelegate();
private void Foo()
{
SqlConnection conn = new SqlConnection("some connection string");
SqlCommand command = new SqlCommand("some stored procedure call");
ExecuteNonQueryDelegat
Use async delegates. Declare a delegate that matches
SqlCommand.ExecuteNonQuery, create an instance of the delegate, and call
BeginInvoke on it. Provide a completion delegate. In your completion
delegate, call the delegate's EndInvoke method. Badda-bing.
-- arlie
-Original Message-
F
- Original Message -
From: "Brian Gaer" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, October 07, 2003 6:08 PM
Subject: [ADVANCED-DOTNET] Async Data Commands with ADO.Net
> Is anyone familiar with a method to have an ADO.Net command object
> perform a command.ExecuteNonQuery(
Yes, you'll need to do the following:
1. Run TlbImp.exe (.net Framework tool) to generate a managed runtime
rapper for the comadmin.dll library (which gives you programmatic access to
the COM+ catalog. I think the syntax is:
tlbimp comadmin.dll /out:comadminLIB.dll
You can also get this library
Hi Paul,
Thanks for the info, I'll check it out.
On Tue, 7 Oct 2003 22:18:45 -0700, Paul Gale wrote:
> You might also want to evaluate NVelocity (a .NET port of the original Java tool).
> It's free.
> It comes with it's own template language called VTL. I've used it before and it is
> very good
Jade Burton wrote:
>
> But what's wrong with creating a thread? If you use the
> threadpool it's almost a one-liner!
Although if you use the threadpool you almost certainly won't be
creating a thread - you'll just be using a thread that was already in
the thread pool most of the time.
And that'
In keeping with Ian's comment, look at Bob Beauchemin's Essential ADO.NET,
Chapter 3. He has a section on cancellation where he says that *if* you do
wish the command to be cancelable, you need to both:
1. start the command on a separate thread, and
2. issue the cancel command on an additional sep
