On Fri, Dec 18, 2009 at 12:11 PM, Tillie Ariantho <til...@xp2.de> wrote: > On 10.12.2009 22:26, Laurence Brickner wrote:
> Compile is only working from within the UI, though, because whoever wrote > develop.py didn't try with the Express version, so it chokes two times, first > on a missing registry entry, that's just not > available for the Express version, and then on a not existing EXE file, that > is not part of Express either. This is a known issue, develop.py was written for linden lab, where they use visual studio 2005 professional > > Just use the UI and all is well (or go fix the develop.py and submit a patch > :D). The basic issue here is not fixable, it is not possible to modify visual studio solutions in the way that are required with an express edition of visual studio. This is by design from Microsoft, the specific automation API that is missing is only available to paid customers of visual studio. Setting the statup project, selecting the build configuration and modifying the working folder are the 3 tasks we need to do but cannot as this data is within the user options file of the solution which is a binary file, with no published format that is only designed to be accessed via the API described in the previous paragraph. Its possible to *improve* develop.py so it handles the entire situation with some grace, and there is a patch of mine on jira (i forget the number) which at least detects visual studio express and then makes no attempt to run the vstool.exe program but instead prints some advice for the user on how to proceed. I guess we should revive this and get it into snowglobe to avoid people having to repeat the same problems over and over. Robin _______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/SLDev Please read the policies before posting to keep unmoderated posting privileges