Hi
was a bit to quick : VS2003 does not have msbuild :-( so how do you compile with ccnet? nant or devenv or ... --> what task do you use? with kind regards Ruben Willems On Mon, Dec 28, 2009 at 9:49 PM, Ruben Willems <[email protected]>wrote: > Hi > > > how do you compile with CCNet ? > with the msbuild task > or with the devenv > > MSbuild is way more precise than DevEnv > something MS is finally learning, since TFS is also using MSBuild and not > devenv to compile. > > > > with kind regards > Ruben Willems > > > On Sun, Dec 27, 2009 at 1:21 AM, E K <[email protected]> wrote: > >> I tried to post this the other day but I've yet to see it show up in >> the feed. So if this seems like a duplicate please ignore. >> >> I am pretty new to CC.net but an old hat to visual studio. I spotted >> CC.net and realized it was exactly what I needed. I am using .net >> 2003, with Subversion and a devenv task. Everything builds properly in >> in th IDE. But using CruiseControl.net, Debug configuration works >> fine. But in Release configuration, compilation of the project the >> compilation fails giving an error stating that unsafe code may only be >> compiled with the /unsafe flag enabled. >> >> This started when I moved some 'unsafe' code into my project from >> another .DLL, neither project was originally being compiled by CC.Net. >> I have a small block of code that was unsafe because it dealt with >> pointers. However I have since both re-written (to be no longer use >> pointers and removed the unsafe block) and commented out said code and >> tried both /unsafe TRUE and FALSE on the project. But it still fails >> to build in Release configuration using CruiseControl. >> >> The project itself builds just fine in the IDE but as soon as I build >> it with CC.net it fails. The really strange thing is that this happens >> even when the unsafe code is commented out. I can verify that the SVN >> task is actually getting the most current code and that the code is >> checked in. I can see where all the options are set properly and I can >> see where the block of code is when the build event runs. >> Unfortunately the project that is failing is referenced by something >> like 18 other projects in the solution so once it fails the build is >> toast. >> >> Converting to a more recent CLR version is not an option at this point >> but is 'on the calendar'. So for right now I need to stick with .Net >> 2003. >> >> Anyone know what is going on or have an idea how to fix it? >> >> EK >> > >
