On Thu, Sep 1, 2011 at 11:28 AM, Ruben Willems <[email protected]>wrote:
> Hi > > Good that you found a solution, but it's a pitty that this has to be done. True, but really how ever it needs to be done, that's what we need to do. I think this is an issue that's been addressed with VS2010 notwithstanding code completion Intellisense having been removed from the VC++ part. Not insurmountable, but for now we're focused with VS2008. with kind regards > Ruben Willems > > On 1 September 2011 16:04, Michael Powell <[email protected]> wrote: > >> >> On Thu, Sep 1, 2011 at 1:25 AM, Ruben Willems <[email protected]>wrote: >> >>> Hi >>> >>> does msbuild x.sln not work? >>> >> >> Nosir, it does not. At least not with a VC++ 2008 solution. >> >> >>> I always build solutions with msBuild. >>> >> >> Which we'd like to. >> >> >>> although they do not contain VC++ projects. >>> >> >> Precisely... >> >> I did a little digging and as it turns out there is some "administrative" >> cost if you will setting this up. It's required in VC++ 2008 that the IDE be >> configured before running any MSBuild and expect that the VC++ dirs be >> picked up. This must be done for the credential that the CC.NET project >> is running under. >> >> >>> with kind regards >>> Ruben Willems >>> >>> >>> On 17 August 2011 20:24, Michael Powell <[email protected]> wrote: >>> >>>> We've got some custom VC++ Directories which we must specify in our >>>> build configuration. I'm not seeing a <devenv/> option to specify custom >>>> settings like Tools \ Options \ VC++ Directories. <devenv/> is a little >>>> light for the task? Or I suppose we could to the <exec/> route once again >>>> and make the explicit request of devenv.com? That's assuming we can >>>> accommodate a "simple" solution file without going the more complex >>>> MSBuild-based route. >>>> >>>> Any suggestions? >>>> >>> >>> >> >
