cilcktobuild will make the AssemblyInfos appear. then on VS you can choose debug or release to your liking.
On Mon, Jun 22, 2009 at 11:58 AM, John Simons <johnsimons...@yahoo.com.au>wrote: > > I think ClickToBuild.cmd builds in release mode? > And if Uri wants to open the solution in VS I think is going to need > the Debug build > > On Jun 22, 6:44 pm, Roelof Blom <roelof.b...@gmail.com> wrote: > > Or even simpler: click on the ClickToBuild.cmd file :-) > > > > On Mon, Jun 22, 2009 at 9:22 AM, John Simons <johnsimons...@yahoo.com.au > >wrote: > > > > > > > > > 1 - Get the source from svn (http://svn.castleproject.org:8080/svn/ > > > castle/trunk <http://svn.castleproject.org:8080/svn/%0Acastle/trunk>) > (I'm > > > assuming you got the source and put it in C: > > > \Castle) > > > 2 - Open a command line window and go to C:\Castle (or the folder that > > > you have d/l the source to) > > > 3 - Type "build quick build" -> this should build the whole castle > > > components in debug mode > > > 4 - You should now be able to open the relevant solution and compile > > > it in VS. > > > > > If the "How to build.txt" is not making sense, can you please send us > > > a patch to it? > > > > > Cheers > > > John > > > > > On Jun 22, 4:57 pm, Uri Goldstein <uri.goldst...@gmail.com> wrote: > > > > I actually did go over "How to Build.txt". It was a bit too cryptic > > > > for me. > > > > > > Remember I'm a newbie - I've never used NAnt in my life. I go Right- > > > > Click > Build in my Visual Studio. So can we start from the > beginning, > > > > slowly? :D > > > > > > On Jun 22, 3:57 am, John Simons <johnsimons...@yahoo.com.au> wrote: > > > > > > > And since no one mention it yet! > > > > > Read "How to Build.txt", that's why it's there for ;) > > > > > > > On Jun 22, 2:06 am, Uri Goldstein <uri.goldst...@gmail.com> wrote: > > > > > > > > Hi, > > > > > > > > I'm trying to get Windosr's WCF Integration and Logging > Facilities > > > > > > from SVN and compile them on my machine. I'm experiencing some > > > strange > > > > > > things: > > > > > > > > 1. AssemblyInfo files are included in the projects but missing > from > > > > > > disk (and SVN tree). > > > > > > 2. Some DLL references reference a relative path: "..\..\..\build > > > > > > \net-3.5\debug\" which is not available in the SVN tree. > > > > > > > > How can I overcome these technicalities? I'd hate to change the > > > csproj > > > > > > files to suit my environment and then have them run over by trunk > > > > > > updates. Is there a recommended way to map the trunk to my local > > > > > > disk? > > > > > > > > Thanks, > > > > > > Uri Goldstein > > > -- Ken Egozi. http://www.kenegozi.com/blog http://www.delver.com http://www.musicglue.com http://www.castleproject.org http://www.gotfriends.co.il --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to castle-project-users@googlegroups.com To unsubscribe from this group, send email to castle-project-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
