Wayport's high-speed Internet access(WiFi)[^] "Whidbey"..."Orcas"...Roadmap This signature was created by "Code Project Quoter".

These are actually called environment variables, not pointers. Windows 98 and ME don't always support the same environment variables as Windows NT. It is better to use Environment.GetFolderPath, since this is supported by all operating systems that currently support the CLR. The functions that this method use are actually used by Windows Explorer, Windows Installer, various Microsoft and non-Microsoft applications, and the .NET Framework, of course. It is far more reliable and more robust to use this like so: string system = Environment.GetFolderPath(Environment.SpecialFolder.System); string windir = Directory.GetParent(system).FullName; string framework = Path.Combine(windir, "Microsoft.NET\\Framework"); A little long-winded, but - as I said - is supported on any OS supporting the CLR and uses the paths that administrators might set up in a roaming profile or for home directories and what not (overriding the defaults). -----BEGIN GEEK CODE BLOCK----- Version: 3.21 GCS/G/MU d- s: a- C++++ UL@ P++(+++) L+(--) E--- W+++ N++ o+ K? w++++ O- M(+) V? PS-- PE Y++ PGP++ t++@ 5 X+++ R+@ tv+ b(-)>b++ DI++++ D+ G e++>+++ h---* r+++ y+++ -----END GEEK CODE BLOCK-----

I'm glad to hear the problem is solved. On the merits of TcpListener as a wrapper: If you look through the source for it (isn't Reflector a wonderful tool) you'll see it's all of about 40 lines of code. Really all it does is wrap Bind/Listen in one method and, create TcpClients around accepted sockets, and translate from one set of exceptions to a different set if you try to accept on a closed socket. What does this actually really buy, except hiding the real Socket's based programming model? Perhaps the thought is it buy's having TcpClients rather than sockets after the connect, but they don't add any value in a server scenario at all. The only real abstraction they provide is in the Connect process, which isn't used there. Perhaps what you want is the NetworkStream model for the actual IO. I might argue that too on different grounds, but I won't today. If that's what you want, then then just do a new NetworkStream(listeningSocket.Accept(), true). Of course, better yet is to use the async Socket.BeginAccept/BeginRead/BeginWrite methods. This is where you'll get scalability. regards, -Blake

Ok, I thought you only had to include it in the config to get an instance, then from there on it just got whatever objects it needed. Thanks for your help... Most appreciated - it works now! :-D Tatham Oddie (VB.NET/C#/ASP.NET/VB6/ASP/JavaScript) tatham@e-oddie.com +61 414 275 989

I ended up finding the problem. After removing the performance counter object from the installer it worked - of course the counter doesn't work but at least it deployed. Does anyone have any ideas on why this would crash the installer - do i need to ship some form of basic install state file - if so what is the format? BTW leppie - i did deploy it in time. ;P

Well, they just need a default constructor :) I rated this article 2 by mistake. It deserves more. I wanted to get to the second page... - vjedlicka 3:33 25 Nov '02