Web Project only build for 'release' or 'debug' configuration, and not custom config.
i have visual studio 2005 solution contains web project.
i have tsfbuild project called 'fullbuild' builds solution configuration of 'release' , solution platform of 'mixed platform'
as part of configuration the web project has the following settings:
configuration: debug platform: .net build: checked
when tfsbuild project runs web project gets compiled (aspnetcompiler called) correctly.
i create new solution configuration called 'serveronly' include server components in build. configuration still includes web project settings same release configuration
the new tfs build project called 'serverbuild' builds solution configuration of 'serveronly' , solution platform of 'mixed platform', web project not build. instead following messages in tfs build log.
task "aspnetcompiler" skipped, due false condition; ((false) or ('$(aspnetconfiguration)' == 'debug') or ('$(aspnetconfiguration)' == 'release')) evaluated ((false) or ('serveronly' == 'debug') or ('serveronly' == 'release')).
task "message"
skipping because "$(aspnetconfiguration)" configuration not supported web project. can use aspnetconfiguration property override configuration used building web projects, adding /p:aspnetconfiguration=<value> command line. web projects support debug , release configurations.
1. mean aspnetcompiler looks @ solution configuration rather project configuration when trying build web project? seems inconsistent other c# projects use project configurations when building.
2. how can web project build in situation? if create , set 'aspnetconfiguration' property in tfsbuild project 'release' want?
thanks
this looks bug in msbuild project generated solutions include web projects me (you can see in-memory project msbuild generates setting environment variabled called "msbuildemitsolution" 1 prior invoking msbuild on solution). is, should map solution configuration project configuration specified in configuration manager, rather attempting use solution configuration directly aspnetconfiguration property value.
you correct work around issue need to set aspnetconfiguration property manually. can try setting declaratively in tfsbuild.proj, suspect have set in tfsbuild.rsp instead - like:
/p:aspnetconfiguration=release
-aaron
Archived Forums V > Team Foundation Server - Build and release management
Comments
Post a Comment