Hi Matthew, I've already downloaded your task and I admire the great work you did. As you could see from my last postings I have already discovered that SLiNgshot is not the best tool to do the conversion. The most annoying thing is that it compiles all projects into one single folder. I believe that project based builds that closely reflect what VS.NET does are more appropriate.
Nevertheless SLiNgshoT still has some nice features. First of all it generates the build instructions for the whole solution so you don't have to manually call builds for each project. This is important for me because most of my solutions have more than 30 projects and I don't want to waste time coding the build instructions by hand. The second thing is that it can be used apart from NAnt because it can also generate NMake files. I'm impressed by the effort you put to create the task that will work directly on .csproj filed, properly handle resource files and other features. In my opinion now we should join efforts to either integrate this routines with existing SLiNgshoT or create new top level task that will generate build files that will automatically call the <vsproj> task for each project in the solution. In either case I will be happy to help. Szymon Kobalczyk > -----Original Message----- > From: Matthew Mastracci [mailto:matt@;aclaro.com] > Sent: Friday, November 15, 2002 3:13 AM > To: Szymon Kobalczyk > Cc: '[EMAIL PROTECTED]' > Subject: Re: [nant-dev] Error on relative path in AssemblyKeyFile > > I have a task for NAnt that will compile projects exactly as VS.NET > does. Please see my earlier messages for more information, and let me > know if you are interested in trying out the custom NAnt task. > > Szymon Kobalczyk wrote: > > >Ok, here is the last problem I had to face today. Some of our projects > are > >strongly named and signed. All of them use the same key that is located > in > >the top folder of the project tree that is referenced by relative path. > So > >the adequate line of AssemblyInfo.cs file in such projects may look like: > > > >[assembly: AssemblyKeyFile("..\\..\\..\\..\\MyProduct.snk")] > > > >But for some reasons SLiNgshoT creators have chosen to produce build file > >that compiles all projects into a single folder and uses fully qualified > >paths. As a result of this the working folder during compilation is > >different then it would be when building the same project with VS.NET. > Thus > >the above line will produce a compile error. > > > >In my opinion the goal of SLiNgshoT should be to reproduce the > compilation > >procedure that is implemented in VS.NET as closely as possible i.e. to > >compile each project into its own bin folder. I understand that some of > us > >may dislike the approach chosen by MS but if this stuff is going to be > >working properly we have to do this their way. > > > >Personally I would be very happy to help whoever currently maintains > >SLiNgshoT to implement all necessary changes. I also encourage others to > >discuss how to properly handle this conversion. > > > >Best Regards, > >Szymon Kobalczyk. > > > > > >------------------------------------------------------- > >This sf.net email is sponsored by: To learn the basics of securing > >your web site with SSL, click here to get a FREE TRIAL of a Thawte > >Server Certificate: http://www.gothawte.com/rd524.html > >_______________________________________________ > >Nant-developers mailing list > >[EMAIL PROTECTED] > >https://lists.sourceforge.net/lists/listinfo/nant-developers > > > >. > > > > > > ------------------------------------------------------- This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
