Microsoft KB Archive/936597

= The application or control does not run when you try to run .NET Framework 1.0 HREF tags to point to a managed executable application or to a control =

Article ID: 936597

Article Last Modified on 12/3/2007

-

APPLIES TO


 * Microsoft .NET Framework 2.0
 * Microsoft .NET Framework 1.1
 * Microsoft .NET Framework 1.0

-



Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



SYMPTOMS
Consider the following scenario. You try to run Microsoft .NET Framework 1.0 HREF tags to point to a managed executable application (.exe) or to a control. You try to run the HREF tags from the Internet or from Intranet zones. In this scenario, the application or control does not run.

Note If you have a later version of the .NET Framework installed on the computer, the managed executable application or the control may run. Controls always run on the latest compatible version of the .NET Framework that is installed on the computer. (For example, controls that were built on the .NET Framework 1.0 always run on the .NET Framework 1.1 and on the .NET Framework 2.0.) Managed executable applications run on a later compatible version of the .NET Framework if the .NET Framework on which they were built is not available on the computer. (For example, applications that were built on the .NET Framework 1.0 run on the .NET Framework 1.1 and on the .NET Framework 2.0.)

Note Managed executable applications are also known as no-touch deployment applications or as zero-impact deployment applications.



CAUSE
This issue occurs because the managed executable applications or the controls may contain non-trusted code. By default, the .NET Framework 1.0 does not let you run managed executable applications or controls.



WORKAROUND
Warning This workaround may make the computer or the network more vulnerable to attack by malicious users or by malicious software such as viruses. We do not recommend this workaround. We provide this information so that you can implement the workaround at your own discretion. Use this workaround at your own risk.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To work around this issue, use one of the following methods:

Method 1 Add the Web site that contains the managed executable application or the control to the &quot;Trusted sites&quot; zone.

Method 2 For managed executable applications, upgrade the application to use the ClickOnce deployment technology of the .NET Framework 2.0, and then install the .NET Framework 2.0 or a later version of the .NET Framework on the computer. For more information about ClickOnce deployment, visit the following Microsoft Developer Network (MSDN) Web site:

http://msdn2.microsoft.com/en-us/library/t71a733d(en-US,VS.80).aspx

Method 3 For controls, install the .NET Framework 2.0 or a later version of the .NET Framework on the computer. Controls will run on the .NET Framework 2.0 and on later versions of the .NET Framework.

Method 4 Configure the computer to let Internet applications run on version 1.0 of the .NET Framework. To do this, follow these steps:  Click Start, click Run, type regedit, and then click OK. Locate and then click the following registry subkey: 

 On the Edit menu, point to New, and then click DWORD Value. Type EnableIEAssembliesV1.0, and then press ENTER. On the Edit menu, click Modify. Type 1, and then click OK.</li> Exit Registry Editor.</li></ol>

Note By default, the Internet zone is already disabled in Code Access Security (CAS) policy for the .NET Framework 1.0. Therefore, you may have to enable the Internet zone in CAS policy. Additionally, you may have to use one of the workaround methods that are mentioned earlier in this section for applications or controls to run successfully from the Internet zone on the computer.

Keywords: kbtshoot kbbug kbsecurity kbpubtypekc kbexpertiseadvanced kbexpertiseinter kbexpertisebeginner KB936597

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.