I'm sorry, Christian, but you're wrong: different 'web applications' can be run with different .NET versions. However, all web applications sharing a worker process (pool) must have the same .NET version.
A 'web application' differs from a virtual directory, and has a different icon (IIS 5.x uses an open box icon rather than a folder icon; IIS 6.0 uses a 'gear' icon rather than a folder). To convert a folder into a web application, click Create under 'Application Settings' in the folder's properties in the IIS management console.
In IIS 5.x (Windows 2000 and XP), this is automatic - the appropriate version of the ISAPI Filter is loaded depending on what the metabase has configured, which then loads the appropriate worker (aspnet_wp.exe) process. ASP.NET 2.0 adds a new ASP.NET page to the application's property sheet which permits the version to be selected. If this page isn't present, ASP.NET 2.0 is probably not installed correctly. To install it, but keep any existing web applications using ASP.NET 1.1, run aspnet_regiis -ir.
The IIS 5.x process model supports in-process, shared process or dedicated process hosting. All applications set to 'shared process' use the same dllhost.exe worker process. However, ASP.NET always creates its own worker processes - your code does not run in dllhost.exe.
In IIS 6.0, the worker process (w3wp.exe) has native support for ASP.NET hosting. Web applications can run in different 'application pools'. An application pool uses at least one process, and potentially more than one, to run the set of applications in the pool. However, the ASP.NET version required for each application is not checked. Only one version of the .NET CLR can be loaded into a process. If you configure an application pool with a set of applications that require different versions, you will have problems as the first application to load into a worker process dictates which version of the CLR is loaded. It's best to keep your .NET 2.0 applications in a separate pool from your .NET 1.1 applications to avoid problems with CLR version mismatches.
A web application can only use one version of the Framework. You would have to place the pages developed for the other version into a different folder (this could be a subfolder) and create a new Application (click Create under Application Settings in the folder's properties in the IIS management console).
You should place the appropriate version of web.config under the root that matches the version of ASP.NET you have selected for the root. The application you create for the other version should have its own web.config: settings are not inherited from the root configuration.
If running on IIS 6.0, you should place your ASP.NET 1.1 applications in a different application pool to the ASP.NET 2.0 applications to ensure that they get separate worker processes.
I don't know... Let me see... Hamster Dance song plays... ... well what do you know - It works!! Of course, it gives you the "Did you mean: ruby on rails tutorials" correction, but hey, results abound!
Basically the type of control You need to use would be an Active-X control.Basically Active-X controls are improved,sophisticated and wrapped versions of OLE controls.I have made a .ocx file available in my word document's file under the listings
"insert->object" using the "insert object type checkbox" of the "Active-X MFC wizard " of "VC++ 6.0" and "VC++2005" both .I therefore think this should also be available into the wizard of your language ,so no need to intangle with the registry.But further if I find it by any means will soon let you know.
It says right in the title of the Counter - Bytes. The scale is just there to get the counter values to fit into the range of 0-100. So 30,000,000 bytes multiplied by a scale of .000001 would give to 30, the bottom of the graph being 0 and the top 100,000,000.