Hi I try to use msbuild, because the error messages there are more consistent. Devenv seems to cache dll locations once it has found a valid one.
That's why I suggested to delete that .suo file. with kind regards Ruben Willems On Wed, Nov 12, 2008 at 1:20 PM, Giovanni Idili <[EMAIL PROTECTED]>wrote: > @Ruben > it is an import on a C++ project so there are not (.NET style) references: > > #import "myDLLName.dll" raw_interfaces_only, raw_native_types, > no_namespace, named_guids, auto_search > > with the msbuild I am getting a bunch of new errors - I'll try to gather > information about those but I am not to confident it's the right way to > solve it. > > I'd rather focus on getting it working with devenv. this was working for a > long time then we changed build machine and it fell apart. > > Thanks for your support > > > On Wed, Nov 12, 2008 at 12:09 PM, Ruben Willems <[EMAIL PROTECTED]>wrote: > >> Hi >> >> What you can try to solve this : >> delete the <solutionname>.suo file, and open the solution again >> >> maybe now you see the wrong references, they can be marked with an >> exclamation mark. >> >> also when you build with msbuild, >> the warnings should give a rather clear reason why it is failing >> >> >> with kind regards >> Ruben Willems >> >> >> >> On Wed, Nov 12, 2008 at 1:04 PM, John_Idol <[EMAIL PROTECTED]>wrote: >> >>> >>> I am trying to runthis: >>> >>> devenv "MySolution.sln" /Rebuild "Release MinDependency" >>> >>> It is failing with same error as cruise control so that should be why >>> it is failing - looks like it is building the project in the wrong >>> order (when building manually it runs just fine). >>> >>> I tried with MSBUILD but it's failing on a bunch of different >>> things ... >>> >>> is there a way to find out what exact command line is being executed >>> by Visual Studio? >>> >>> On Nov 12, 10:39 am, "Ruben Willems" <[EMAIL PROTECTED]> wrote: >>> > Hi >>> > >>> > you can do this by a property: >>> > msbuild /p:configuration="Release MinDependency" >>> > >>> > but I doubt that another configuration will produce another result with >>> this >>> > problem : >>> > dll not found >>> > >>> > be sure to also use the tasks /t:clean /t:build >>> > >>> > with kind regards >>> > Ruben Willems >>> > >>> > On Wed, Nov 12, 2008 at 11:18 AM, John_Idol <[EMAIL PROTECTED] >>> >wrote: >>> > >>> > >>> > >>> > > @Ruben: >>> > >>> > > I do I specify release mode with MSBuild? I need to build in release >>> > > minDependency mode >>> > >>> > > On Nov 12, 9:31 am, "Ruben Willems" <[EMAIL PROTECTED]> wrote: >>> > > > Hi >>> > >>> > > > you're building 1 VS solution right? >>> > > > try building it with msbuild, does this work? >>> > >>> > > > msbuild solutionname /t:clean /t:build >>> > >>> > > > this cleans and rebuilds the solution >>> > >>> > > > with kind regards >>> > > > Ruben Willems >>> > >>> > > > On Wed, Nov 12, 2008 at 10:16 AM, John_Idol < >>> [EMAIL PROTECTED] >>> > > >wrote: >>> > >>> > > > > @Ruben: >>> > >>> > > > > sorry I gace wrong info - the dll is sent to the output >>> automatically >>> > > > > in Linker->general: $(OutDir)/myDLLName.dll >>> > > > > OutDir is the same for all the projects - I suspect the proj is >>> not >>> > > > > being built at all thourgh CC.NET (build order is wrong - but >>> manually >>> > > > > is fine, see previous answer) >>> > >>> > > > > On Nov 12, 8:56 am, "Ruben Willems" <[EMAIL PROTECTED]> >>> wrote: >>> > > > > > Hi >>> > >>> > > > > > Yep I meant that. >>> > >>> > > > > > since you're using a postscript to copy the dll, >>> > > > > > check how the paths are definded. >>> > > > > > suppose you use X:\\bla bla >>> > >>> > > > > > and X is a mapped network drive, it will not work under the >>> service >>> > > > > > better is to use UNC : \\servername\sharename\... >>> > >>> > > > > > I use msbuild in my scripts, and this makes it easier to spot >>> the >>> > > problem >>> > > > > > just run msbuild from the command line where your solution is >>> in. >>> > >>> > > > > > with kind regards >>> > > > > > Ruben Willems >>> > >>> > > > > > On Wed, Nov 12, 2008 at 9:48 AM, John_Idol < >>> [EMAIL PROTECTED] >>> > >>> > > > > wrote: >>> > >>> > > > > > > HI Ruben - thanks for helping. >>> > >>> > > > > > > What do you mean with "reference path", do you mean the >>> reference >>> > > for >>> > > > > > > the not found dll on the proejct that looks for it? >>> > > > > > > It is pointing with an import to an output folder where the >>> other >>> > > > > > > project is supposed to copy on post build the dll. If running >>> with >>> > > > > > > CC.NET service dll is not in this output folder - if >>> manually It >>> > > is >>> > > > > > > there (so it doesn't fail). >>> > >>> > > > > > > I will try to debug the problem using the console app instead >>> of >>> > > the >>> > > > > > > service. >>> > >>> > > > > > > Any other idea? >>> > >>> > > > > > > On Nov 12, 7:17 am, "Ruben Willems" <[EMAIL PROTECTED] >>> > >>> > > wrote: >>> > > > > > > > Hi >>> > >>> > > > > > > > can you check the project file manually? >>> > > > > > > > --> open it in notepad or so, and check the reference path >>> > >>> > > > > > > > I've seen in many cases that VS can compile a solution, but >>> > > msbuild >>> > > > > does >>> > > > > > > > not. >>> > > > > > > > and in all these cases, there was a wrong path in the >>> project >>> > > file. >>> > >>> > > > > > > > with kind regards >>> > > > > > > > Ruben Willems >>> > >>> > > > > > > > On Tue, Nov 11, 2008 at 10:23 PM, John_Idol < >>> > > > > [EMAIL PROTECTED] >>> > > > > > > >wrote: >>> > >>> > > > > > > > > I have a project that builds fine If I build it manually >>> but it >>> > > > > fails >>> > > > > > > > > with CC.NET. >>> > >>> > > > > > > > > This project is composed by a number of .NET projects and >>> a few >>> > > C++ >>> > > > > > > > > dlls. >>> > >>> > > > > > > > > The error that shows up on CC.NET is basically related >>> to an >>> > > > > import >>> > > > > > > > > that's failing because file was not found; one of the >>> projects >>> > > (C++ >>> > > > > > > > > dll) tries to import a dll built by another project. Dll >>> should >>> > > be >>> > > > > in >>> > > > > > > > > the right place since there's a dependency between the >>> projects >>> > > - >>> > > > > > > > > indeed when I build manually everything works fine (Note >>> that >>> > > when >>> > > > > I >>> > > > > > > > > say manually I am getting everything fresh from source >>> code >>> > > > > repository >>> > > > > > > > > then invoking a Rebuild from VS2005 to simulate >>> > > CC.NETautomation). >>> > > > > > > > > When I run through CC.NET though the dll is not in the >>> right >>> > > place >>> > > > > (I >>> > > > > > > > > checked after the build failed and it was not physically >>> in the >>> > > > > > > > > folder). >>> > >>> > > > > > > > > Looks like dependencies are ignored when the build is >>> automated >>> > > > > > > > > through CC.NET. >>> > >>> > > > > > > > > I am building in Release MinDependency mode. >>> > >>> > > > > > > > > Any help would be highly appreciated! >>> >> >> > > > -- > Giovanni Idili - http://www.linkedin.com/in/giovanniidili >
