Ok, so I've written the entire thing... it accesses my previously built database... if there is anyone out there who would like to see the process from beginning to end, let me know and I will post an easy to use article...

A link to CodeGuru?!! Blasphemy!!

Hi there. Here's a couple of links to CP articles showing some different approaches. http://www.codeproject.com/aspnet/PleaseWaitButton.asp[^] http://www.codeproject.com/aspnet/ClickOnce_Button_Control.asp[^]

You have to mark your ActiveX control "safe for scripting". This really isn't anything new in XP SP2, though. IE always acted this way when scripting ActiveX controls, but reacts a little different now (i.e., how it interacts with the user). I suggest reading about IE security zones and settings in MSDN Library. Most of this comes down to the user's security settings. You can't get around them (knock on wood), otherwise what's the point of security? You have to work within them and utilize what you can. If you want to use javascript to see if an object exists, there's always typeof you can use like so: if (typeof("myControl") == "object") window.alert("It exists!"); The fact that your ActiveX control is signed will 1) dictate what the user sees and how confident they should be (a nicer UI for signed components), and 2) the different security zone settings for signed and unsigned components, as well as signed and unsigned .NET Components (when the .NET Framework is installed). I also urge you to explore the security zones settings if you haven't already. Be sure to set them all to default (click the "Default" button after selecting each one) at first to get a glimpse of what you're dealing with. This posting is provided "AS IS" with no warranties, and confers no rights. Software Design Engineer Developer Division Sustained Engineering Microsoft [My Articles]

Sure, but that's easy to come by. Here's an article by Ingo Rammer[^] about the changes in .NET 1.1. One more thing, you'll have to override InitializeLifetimeService() to return null on the class being published for remoting or its lifetime lease will run out after approx. 2 minutes, meaning that you'll get an error when you start a second instance of your app after >2 minutes. I've already contacted Chris Anderson, but he doesn't plan to update his article :( Regards, mav

The other reply wouldn't work. Embedded resources are stored differently than Win32 resources (in C/C++, these would be referenced in the .rc file). There are many ways you can do this. You can use the command-line compiler (csc.exe) and specify the /win32res: switch along with the path to a .res file that contains your win32 resources. In Visual Studio 2005, you will be able to specify this in the environment, which wasn't available in Visual Studio .NET 2002 and 2003. You can also - after compiling - open the executable (.EXE or .DLL) in Visual Studio. That will show you your resource section. You can import icons and other resources types into the PE/COFF executable (the executable format on Windows). If you sign your assemblies (and there's no reason not to - it's easy), you should resign them to make sure the hash is correct (shouldn't be a problem, but follow along anyway). Use sn.exe -R MyApp.exe KeyPair.snk, where MyApp.exe is the assembly to be signed (of course) and KeyPair.snk is the path to the key pair you used to sign the assembly in the first place. Usually it's a good idea to enable delayed signing (using the AssemblyDelaySignAttribute) and sign it later anyway, and if you use Authenticode to sign the assembly (the PE/COFF executable, actually) then you'll definitely need to resign it after modifying it (or just don't sign it before modifying it anyway). Again, Visual Studio 2005 will include this functionality into the IDE, which will be nice. Alternatively, you might consider just using a native resource-only DLL with the icons you want. Create a new (unmanaged) C or C++ DLL project, add your resources (icons, bitmaps, AVIs, etc.), compile and distribute. The only problem with this approach is that Fusion (the assembly binder which can work seemlessly over the Internet) won't grab it - it only works with .NET assemblies. With installation deployments or (presumably) ClickOnce - a new touchless deployment in .NET 2.0 - this won't be a problem. Microsoft MVP, Visual C# My Articles

At least you have a decent user name :)

using System.Runtime.InteropServices; ... public class InternetConnection { [DllImport("wininet.dll")] public static extern bool InternetGetConnectedStateEx(out int lpdwFlags, byte[] szConn, int iConnSize, int dwReserved); /// /// Status da conexão /// public enum Status: int { /// /// Local system uses a modem to connect to the Internet. /// INTERNET_CONNECTION_MODEM = 1, /// /// Local system uses a local area network to connect to the Internet. /// INTERNET_CONNECTION_LAN = 2, /// /// Local system uses a proxy server to connect to the Internet. /// INTERNET_CONNECTION_PROXY = 4, /// /// Local system has RAS installed. /// INTERNET_RAS_INSTALLED = 16, /// /// Local system is in offline mode. /// INTERNET_CONNECTION_OFFLINE = 32, /// /// Local system has a valid connection to the Internet, but it might or might not be currently connected. /// INTERNET_CONNECTION_CONFIGURED = 64 } /// /// Returns true if connected /// public static bool Connected { get { bool bConn = false; int flags = 0; byte [] cName = new byte[512]; if(InternetGetConnectedStateEx(out flags, cName, 512, 0)) { bConn = true; } return bConn; } } public InternetConnection() { } } ... InternetConnection inet = new InternetConnection(); if(inet.Connected) { ... } else { // not connected } Cheers, John