And as a followup, I would like to draw everyones attention to a new article from the 'MSDN architectural samples team', which is 11 pages worth of details on how to automate building a win32/soap web service using VB script, a script that does nothing but increment a build counter, set up the properties (env variables), get the latest source from VSS then call build.bat files in subprojects in a manually coded dependency order
Should we point to this in the 'how people used to build projects' section of the resources page :-) -Steve ----- Original Message ----- From: "Steve Loughran" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, June 01, 2001 10:11 AM Subject: Re: Bad taste but... > > ----- Original Message ----- > From: "Morrison, John" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, June 01, 2001 06:46 > Subject: RE: Bad taste but... > > > > I'd assumed that it was a local thing. Speaking personally, I'd consign > VB > > to the same place as the empties. Unfortunately, the PTBs are dictating > > otherwise :( > > > > I've managed to fudge this using exec, but a task would have been better! > > > > J. > > > > I was debating adding a vbc task to go with csc in the .net tools; .net does > provide a command line invocation of the compiler, whereas for VB6 and below > you need to invoke the IDE with various parameters. > > But I decided against it on ethical grounds: anything that made VB easier to > work with would only encourage people to use it. > > -steve > >
