Pretty funny stuff! Sad but true...

I am not sure about this one: What about rundll32.exe ? You, IMHO, should be able to associate an extension not only with an executable, but also with an executable with custom parameters. If I am right here, you could then simply associate your extension with "rundll32.exe mydll.dll MyExplorerBarStarter" or something like that. I am not sure it will work with .NET-DLLs though :( Cheers Sebs

Thanks! Turns out it was an invalid (empty) launch condition that lingered around instead of being deleted.

If you're willing to wait couple months (or use beta software) .net framework 2.0 will have those.

The big question is how the browsers are configured. Most corporate networks these days seem to use automatic configuration through a script like I mentioned before. WebProxy.GetDefaultProxy will not pick this information up automatically, so you would have to configure these settings yourself and set the instance of your WebProxy to the HttpWebRequest.Proxy property. If you read about the HttpWebRequest.Proxy property in the .NET Framework SDK, you will find more information. Microsoft MVP, Visual C# My Articles

Actually, I figured it out. I had been using the GAC, and the DLL was expecting the PDB to be in the GAC, too. I copied the PDB to the same directory in the GAC, and that worked. Later, I decided to not use the GAC for development work. Thanks for responding!

If you're using the Windows Installer project in VS.NET, add the output of your project to the installer and it is updated whenever you recompile your C# project (it becomes a dependency of the installer project). I'm not saying the GAC doesn't work, I'm just saying that it can lead to problems until you're done testing. You've already had one. If you use automatic versioning you'll have lots of assemblies (differing only by version) in your GAC. It doesn't hurt anything, but it sure clutters up the GAC. It's just a recommendation that's not uncommon when debugging applications, especially in larger teams. Microsoft MVP, Visual C# My Articles

I think that it has to do with the ShowDialog[^] form being modal, and that Show[^] is inherited from Control[^], which only makes the Form visible. When it's modal, it's usually a form in which the user has to give some input, and press Enter to accept (or Esc to cancel). - Daniël Pelsmaeker There are 10 kinds of people in the world. Those that understand binary and those that do not.

Well, it looks like I can't get access to private fields of inherited types through GetMembers(). I guess that makes sense. Using Reflector, I see that System.Runtime.Serialization also has to ascend the inheritance tree to get the list of serializable members, so I will, too. Thanks, Arun

Good to know that it's implemented smartly! I'm still not sure I can generalize across types. Perhaps I can for the types I use presently, but maybe not in the future. That is, I'd rather not store the assembly name (partial or full) in my file, especially since LoadWithPartialName isn't preferable for long-term, according to documentation. Arun

Hmm, maybe Reflection will somehow help me with the System classes.

Yeah, and I'm lazy. AutoScroll seems to mostly work, but in a tricky and incomplete way. Oh well!

Here you go, its called: Opaque If true, the control is drawn opaque and the background is not painted. leppie::AllocCPArticle("Zee blog"); Seen on my Campus BBS: Linux is free...coz no-one wants to pay for it.