Apparently, VS2005 has a new attribute [VisibleFromAssembly="ASSEMBLY_NAME"] which I'll be able to use. I'm not sure that's the exact attribute name, but it's something similar that can be applied at the class level, for instance, to an internal class.

Quimbly wrote: I'm using goto, which is never a good idea. A well placed goto is worth 1000 whiles :p In your case I see nothing wrong. In fact using goto's within try/catch/finally and switches makes alot of sense if well placed :) I for one is not gonna try figure out how to loop thru something complex. Sure you can perhaps 'refactor' the metohd, but that isnt allways the better idea either. If you want some reassurance of got usage, read a bit of Linux kernel code before bed tonite :laugh: top secret Download xacc-ide 0.0.3 now! See some screenshots

Dynamically compile C# code? Bwah?! Where?! That sounds like fun.

I think the following on an ASP.NET or its associated codebehind page should solve your problem: string userip = Request.ServerVariables["REMOTE_ADDR"].ToString(); string workstationname = System.Net.Dns.Resolve(userip).HostName.ToString(); The name of the machine accessing the webserver should be contained in the workstationname. However the firewall might put its name over there. We are currently using a proxy called 'Squid Cache' and I observed the following type of header contains the IP Address of the client machine (that is mine), which is behind the proxy/firewall. HTTP_X_FORWARDED_FOR But the name of the machine behind the proxy might need a workaround though. Deepak Kumar Vasudevan

If it's "across the wire" all you're going to get is the DNS reverse lookup. Machine names are not necessarily the same as the DNS name, and all TCP/IP w/DNS will give you is just that: The DNS name, which may or not be the machine name. NetWkstaGetInfo() will only work on Windows machines (Pre Windows 2000 or Pre Windows 2000 compatible) where Anonymous access is allowed (a reeeeely reeeeeely reeely bad practice!) Why do you need to know the actual machine name anyway? If there's suspicious behavior, you can trace the IP back. If it's illegal behavior, you can go deeper and give the authorities your firewall logs for the offense.