mikefourie-zz / MSBuildExtensionPack

MIT License
366 stars 104 forks source link

Updated Adaptor to include Constraints property for setting Adaptor Constraints #29

Closed JeanPierreDeTiege closed 9 years ago

JeanPierreDeTiege commented 9 years ago

Updated Adaptor code by adding in Constraints property so Constraints can be set on the MSBTS_AdapterSetting WMI object. Chose to use int and convert to UInt32 to keep the code CLS compliant. Additionally chose to swallow any usage of int values of 0 or lower as opposed to trying to throw additional diagnostic error messages for sake of simplicity.

mikefourie-zz commented 9 years ago

Thanks JP

JeanPierreDeTiege commented 9 years ago

no problem, thanks for including it! Since looking at that adapter task for BizTalk I've gone back to the 2.13 deployment scripts and recognized that one other part of deployment where I had to step away from MSBuildExtensionPack was when I had to set site and application pool defaults. For these I had to use appcmd.exe to set values for that bare metal deployment. Do you think there's any mileage in trying to set up any code/tasks for these? They're accessible through Microsoft.web.administration.servermanager.applicationpooldefaults and sitedefaults so it could follow the general pattern the other IIS7 class follow (creating a server manager to connect local or remote then perform task action although in this case that'd only be modify and get info) and then define the multitude of properties available for app pools and sites and set these to the initial default values or modify them. Obviously I'd need to find time to actually do it if it makes sense and my track record on that isn't great but let me know if it makes sense to contemplate tasks for these in the first place.

JP

Date: Mon, 20 Apr 2015 13:45:10 -0700 From: notifications@github.com To: MSBuildExtensionPack@noreply.github.com CC: jpdetiege@outlook.com Subject: Re: [MSBuildExtensionPack] Updated Adaptor to include Constraints property for setting Adaptor Constraints (#29)

Thanks JP

— Reply to this email directly or view it on GitHub.