|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
Problems building strangely named VS.NET solution configuration
My latest VBP Project includes a step to build a VS.NET solution. The solution has the following 8 language-specific configurations:
[en-us]|Win32 [zh-cn]|Win32 [fr]|Win32 [de]|Win32 [it]|Win32 [ja]|Win32 [pt-br]|Win32 [es-mx]|Win32 Only the English configuration currently works, so I need to make sure it's the only one that gets built. I am selecting [en-us]|Win32 from the Configuration(s) list box on the Project/Solution tab. Unfortunately, because the configuration name begins with the '[' character, VBP seems to be interpreting it as a regular expression and giving the following error: Solution configuration '0|Win32' not found. Does anyone know if there's a way to force a literal string as a solution configuration? |
#2
|
|||
|
|||
Actually, VBP is interpreting the part between brackets as a script expression. Double the bracket chars to specify literals:
[[en-us]]|Win32 |
#3
|
|||
|
|||
That did the trick. Thanks!
|
Thread Tools | |
Display Modes | Rate This Thread |
|
|