G
Guest
Hi there
Was hopeing someone could point me in the direction of some info for the
following.
Our company runs seperate dev and build environments. In .NET 1.1 we simply
sucked the projects (ASP and components) out of source control ran the build
and pushed to the relvent environment. The build system needed neither IIS or
VS and the whole exercise was heavily scripted to run with out intervention.
In F.W2 this seems to have gone to pot.
Running MSBuild against the projects gives us DLL's but get us no where near
a deployable app.
aspnet_complier would probably do it but requires the the web site to be
referenced in IIS, which isn't really practicle give the number of projects
we work on and the the release cycles we work to.
V.S could do the Publish, but I would prefer not to have to install(license)
it on our build server.
Am I missing something?
This used to be very simple.
Sorry to sound like a whinge bag.
AM
Was hopeing someone could point me in the direction of some info for the
following.
Our company runs seperate dev and build environments. In .NET 1.1 we simply
sucked the projects (ASP and components) out of source control ran the build
and pushed to the relvent environment. The build system needed neither IIS or
VS and the whole exercise was heavily scripted to run with out intervention.
In F.W2 this seems to have gone to pot.
Running MSBuild against the projects gives us DLL's but get us no where near
a deployable app.
aspnet_complier would probably do it but requires the the web site to be
referenced in IIS, which isn't really practicle give the number of projects
we work on and the the release cycles we work to.
V.S could do the Publish, but I would prefer not to have to install(license)
it on our build server.
Am I missing something?
This used to be very simple.
Sorry to sound like a whinge bag.
AM