2
0

CustomAction.config 1.4 KB

1234567891011121314151617181920212223242526272829303132
  1. <?xml version="1.0" encoding="utf-8" ?>
  2. <configuration>
  3. <startup useLegacyV2RuntimeActivationPolicy="true">
  4. <!--
  5. Use supportedRuntime tags to explicitly specify the version(s) of the .NET Framework runtime that
  6. the custom action should run on. If no versions are specified, the chosen version of the runtime
  7. will be the "best" match to what Microsoft.Deployment.WindowsInstaller.dll was built against.
  8. WARNING: leaving the version unspecified is dangerous as it introduces a risk of compatibility
  9. problems with future versions of the .NET Framework runtime. It is highly recommended that you specify
  10. only the version(s) of the .NET Framework runtime that you have tested against.
  11. Note for .NET Framework v3.0 and v3.5, the runtime version is still v2.0.
  12. In order to enable .NET Framework version 2.0 runtime activation policy, which is to load all assemblies
  13. by using the latest supported runtime, @useLegacyV2RuntimeActivationPolicy="true".
  14. For more information, see http://msdn.microsoft.com/en-us/library/bbx34a2h.aspx
  15. -->
  16. <supportedRuntime version="v4.0" />
  17. <supportedRuntime version="v2.0.50727"/>
  18. </startup>
  19. <!--
  20. Add additional configuration settings here. For more information on application config files,
  21. see http://msdn.microsoft.com/en-us/library/kza1yk3a.aspx
  22. -->
  23. </configuration>