Hello WiX Community, I'm just wondering what the reason is for restricting ManagedPipelineMode and ManagedRuntimeVersion to be a limited set of predefined values? I understand the ManagedPipelineMode evaluates into a single bit to be ON or OFF, and it's easier in terms of implementation of IIsExtension. But what about ManagedRuntimeVersion?
In my installation project the user chooses the pipeline mode and runtime version via UI controls and I would prefer to pass this choice as properties to the MSI package, something like this (the same I can do for the name): <iis:WebAppPool Id="IISSiteAppPool" Name="[IISAPPPOOL_NAME]" MaxWorkerProcesses="1" Identity="networkService" ManagedPipelineMode="[MANAGED_PIPELINE_MODE]" ManagedRuntimeVersion="[MANAGED_RUNTIME_VERSION]" /> However, the only option I have now is probably to author a custom action to patch IIsAppPool table based on passed property values. It seems this is the case where build-time error is preferred against install-time error. This is fully understandable, but [probably, a question to the authors] isn't it better to replace an error with warning and leave it to developer's responsibility? P.S. The question turns out to be thinking aloud, but I would appreciate to know what others think. :-) -- Yan ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
