I wrote a some crypto wrappers into a dll for use in our vb6 app and
for abstraction for when we migrate to a pure .net app. In the dll I
created the following hash routine.
Original function from dll:

While experimenting with CLR stored procedure, I discovered it won't
populate the fields in the TableAdapter, like a normal stored procedure. Why
is this?
GetClientList = normal stored procedure

I'm back, and I've got a new wrinkle. In the last episode, I had to resort
to using the Async methods for invoking web services so that
ThreadAbortExceptions .Abort() the call without sticking the connection
open.

I have application which integrates into MS SMTP server and filters incoming
SMTP messages. Based on the sender address the app queries a database
angainst blacklist and whitelist. Everything was working fine, and all of a
sudden without changing the app, it logs the following ...

I have looked at the MSDN docs/google etc.. but I have not found any help,
so I thought I would throw the question/query out to the public...  so here
goes..
I have an existing library that is configured via a application

I just wanted to write a CLR function that evaluates some
data and eventually sends a message using MSMQ. So I added
a reference to System.Messaging. When creating the assembly
I get an error claiming that System.MEssageing cannot be

I am sure that some one has solved this problem before.
i am using RDA to do Data syncronisation from SQL CE to SQL2005.
It seems that if you PULL a Table with TrackingOn and then delete the Record
from the server. It does not get reflected on the PDA after next PUSH.

I had started and rambled on in another thread about this problem (AppDomain
unloads - ThreadAbortException during WebRequest.GetResponse()), but I
thought I do a fresh post with new information and fresh ramblings.
I have a pair of simple SQL CLR functions, one which does a

How do I specify an optional parameter for a Visual Basic CLR stored
procedure? I also need to include default values.
Thanks

I'm looking for some guidelines to design, develop and maintain a standard
database. I mean standard in terms of naming conventions, schema, security,
availability, maintenance and every aspect that there is standards. However
I'm not sure if there can be standard rule for all of ...

I'm getting the behavior that an AppDomain unload occurs (due to memory
pressure) and after that regular synchronous web service calls I made before
now stall and timeout, but if I do something like switch to a etc/hosts
based entry to the target, I can successfully access it.

How do I specify the schema to use when I deploy a CLR stored procedure from
the Visual Studio?