Extra more smart web.config transforms with replacements?

Jun 15, 2011 at 7:17 PM

I have a nuget package that I've been able to automate the majority of all the configuration for it. However I'm left with a couple situations where my config transform ends up like

   <add key="myApp/AudienceHost" value="localhost" />
    <add key="myApp/AudiencePath" value="#CONFIGURE#" />

Where as if I could do something like

    <add key="myApp/AudiencePath" value="$$projectName$$" />

Where $$projectName would resolve to the project name that the nuget package is being installed into I'd be able to infer my usage 90% of the time instead of 0% of the time for project specific parts.

It'd also be great if I could choose between the actual Project name OR the value of the project Assembly name setting, perhaps projectName vs projectAssemblyName etc.

Jun 16, 2011 at 5:07 PM

please open a bug for this. We need to support more tokens than the current set that we do.

Developer
Jun 16, 2011 at 5:09 PM

We already have a bug to support more tokens, that's not what the issue is. I think @dotnetchris wants support for expressions like $projectName ?? assemblyName$ (something along those lines).