Hi, What step in the build workflow do you edit the assembly.info file(s), while the file may have been edited (as you indicated) it is possible it was already too late. Your activities should be located immediately after the GetWorkspace Activity (located inside the Initialize Workspace Activity).
If you modify the assembly.info as part of your .csproj definition then it would need to be running in the BeforeBuild target.... Does that help? Wes From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Sniderman Sent: April-06-12 5:46 PM To: ozTFS Subject: Build Automation Problem Editing Assembly Info for multiple Configurations I'm working automating a build for a Windows Client application. Our application has two true "configurations" (for Citrix vs. occasionally disconnected laptop users) and Prod/QA/Dev/Test/Training environments. I've written automation that color codes the application icon based on environment (by simply copying a "-red" icon file over the name icon file the EXE uses. The users will always know what environment they are in by the color (nice) Next thing we are doing is editing the assemblyinfo to not just set version - but also the assembly description to say the config/environment (I'm using build config for both). However - EVERY SINGLE EXE/DLL is getting the value of the very first one. I went on my build server and the source does show it was edited to the last config's value. The odd thing is that the icon Workflow step is just before the assembly info - so I especially don't understand why that icon automation works but the assembly info doesn't Thanks!
_______________________________________________ oztfs mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/oztfs
