Another way would be that you simply add the possibility to add something like <assemblyfolders> known from solution task where the uplicx task should search for assemblies ..
I happy that I could help :) Christian Leh > -----Original Message----- > From: Thomas Tomiczek [mailto:[EMAIL PROTECTED] > Sent: Mittwoch, 25. Mai 2005 11:46 > To: Christian Leh > Subject: RE: [Nant-users] VS.NET & lc.exe differences in > solution task - anyone has a sane approach? > > This has two severe issues. > > First, it means we loose the ability to target lower versions. > > Second, it means the assemblies must be in GAC. > > Hate it. > > We work now on an add-in that upgrades all license,lics files > to the versions referenced - integrated in vs.net, with a > nice solution level command. > > Next step we may do is go towards changing the nant task for > lc.exe so that it copies lc.exe and all referenced assemblies > into a folder, then runs lc.exe. This allows them to be found > without being in the gac (at least it should). > > Thanks for he code, though - it is really helpful to get our > developer starting on this. > > The addin will do some more stuff (cleaning directories in > vs.net and stuff like this) and be up on the web as open source soon. > > Thomas > > > -----Original Message----- > > From: Christian Leh [mailto:[EMAIL PROTECTED] > > Sent: Mittwoch, 25. Mai 2005 11:36 > > To: Thomas Tomiczek > > Subject: RE: [Nant-users] VS.NET & lc.exe differences in > solution task > > - anyone has a sane approach? > > > > > > Have a look at http://moodwrod.com/nant/ > > > > There is an UserTask which updates a licenses file to the versions > > installed in GAC. > > > > Build file exmaple target to update all .licx files in the > > subdirectories of the buid file: > > > > <target name="uplicx"> > > <foreach item="File" property="licx"> > > <in> > > <items> > > <include name="./**/*.licx" /> > > </items> > > </in> > > <do> > > <uplicx licxfile="${licx}"/> > > </do> > > </foreach> > > </target> > > > > Have a try, its works fine for me > > > > Christian Leh > > > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] On Behalf > Of Thomas > > > Tomiczek > > > Sent: Mittwoch, 25. Mai 2005 09:41 > > > To: nant-users@lists.sourceforge.net > > > Subject: [Nant-users] VS.NET & lc.exe differences in > > solution task - > > > anyone has a sane approach? > > > > > > There is a difference in how lc.exe and vs.net handle the > > > licenses.licx file. Basically: > > > > > > * VS.NET ignrores the version information of components to be > > > licensed, and compileds against the component version that is > > > referenced in the project. > > > > > > * lc.exe compiles against the version embedded in licenses.licx. > > > > > > Sadly, while vs.net does automatically add new lines to the > > > licenses.lics, it does not upgrade them when a project is > > referencing > > > a new version of it's referenced assemblies. > > > > > > The result is that you can have builds that work prefectly > > in VS.NET, > > > but fail miserable in nant, because the assemblies we talk > > about are > > > not available to lc.exe. > > > > > > I am currently running, significantly, into this problem. > > And I mean > > > significantly. > > > > > > Has anyone an idea how to handle this? If noone has, I will > > sit one of > > > my people on writing a VS.NET add-in that goes through a > > solution (on > > > solution load) and checks all versions in the license.lics file > > > against the referenced assemblies. > > > It can create a list of all operations it has to do, pinpointing > > > upgrades and deletes (yes, components may not be refreenced > > anymore at > > > all) and make the maintenance a lot better. > > > > > > Thomas > > > > > > > > > > > ------------------------------------------------------- This SF.Net email is sponsored by Yahoo. Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005 _______________________________________________ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
