Look at Shannon Pahl's piece on EnterpriseServices; she has a good section discussing static methods (in short, they run in the context of the caller, not the package):
http://www.gotdotnet.com/team/xmlentsvcs/espaper.aspx John -----Original Message----- From: Moderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Bill Bassler Sent: 6. februar 2004 21:42 To: [EMAIL PROTECTED] Subject: Enterprise Services ContextUtil and .Net static methods. I had created an Net serviced component that contained a static method. It is in development and I had no problems calling the method from the component set to Server activation (out-of-proc). So the static method calls appeared to function properly for quite some time. Recently, however a call to ContextUtil.SetComplete fails within the static method. When I removed the static call and created an instance and make the call, all appears to work well. Question I'm trying to clarify what the main issues are here. Insight would be appreciated. Can a .Net Serviced Component class contain static methods? If so/not what are the relevant issues with regard to: 1. Server/Library activation 2. Context 3. Singletons vs. instances 4. COM proxies =================================== This list is hosted by DevelopMentorR http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 26 Jan 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor� http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 26 Jan 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
