1

Closed

App Pool Name Cannot Be Specified with a Variable?

description

This is probably just a case of a user who doesn't know what he's doing...
 
For some reason, when using the Web.Iis7AppPool activity, I can use a variable to specify the MachineName, for instance; but I cannot do so for Name (cf. attached image; note that the ellipsis doesn't appear).
 
I tried to edit the xaml and put brackets around the variable name (e.g. [AppPoolName]), but it generates an error ("Invalid application pool name") when the build is run.
 
I also tried looking at the source (Iis7AppPool.cs and BaseRemoteCodeActivity.cs), to see why this would be so, but nothing is jumping out at me; I don't even have a plausible hypothesis.

file attachments

Closed Aug 12, 2012 at 2:10 PM by GuillaumeRouchon

comments

mikeFourie wrote Aug 5, 2012 at 5:31 PM

Most of the properties on the iis7 activities are properties and not inarguments, hence you can't use a variable. When the move to workflow was done in 2010, this was the biggest area of concern, do we we use properties or activities? One school of thought says we should always use arguments, another says you shouldn't. We found a middle ground, though I see us generally moving towards providing arguments.

I'll add this to the August release and see if we can get it actioned.

Mike

wrote Aug 12, 2012 at 2:10 PM

Resolved with changeset 78779.

Sign in to add a comment