The best book on the subject that I have read is: .NET and COM: The Complete Interoperability Guide, by Adam Nathan[^]. It was written for the First Version of the .NET Framework, however, so some of the information (especially, syntax in code examples) will be obsolete.

cpkilekofp wrote: Hear, hear! Can I actually set breakpoints without inserting "debugger;" into my code? Yes! The auto generated LINQ Class will create methods to call the stored proc. Each parameter is a variable in the auto generated method. Most T-SQL parameters will be the equivalent nullable type in .net. For instance @input int would be int? input. Null is translated to DBNull. String are not nullable but I think an empty string is translated to DBNull. It is certainly worth trying. It saved me a lot of time on my current project. I didn't get any requirements for the signature

In mine everyone has to badge in/out but they don't require doors to shut between. Motion detectors will set off an alarm if anyone tries pulling a runner. The current setup isn't quite fully installed, but we've been told trying to run the doors will trigger them locking. While that doesn't make sense on it's own based on other recent changes it appears the goal is to make the area just inside the security doors into a mantrap. Writing policies that put security above egress in an emergency, or getting EMS/Fire people inside will bring the wrath of OSHA, etc down on everyone involved; so even if there is a nontrivial delay in normal conditions it can't be enforced for emergency egress. Today's lesson is brought to you by the word "niggardly". Remember kids, don't attribute to racism what can be explained by Scandinavian language roots. -- Robert Royall