Hmm not sure about the list etiquette after mis-posting. But I wanted to relay kudos.
Yes, that totally did the trick and I no longer required a hard coded framework path. After an initial learning curve. I now have one button compiliation of all Utility, Business, and UI assemblies in our software development project. This is an excellent producitivity boost for our team. Thank you NAnt developers! Kevin Miller -----Original Message----- From: Scott Hernandez [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 10, 2002 12:41 PM To: [EMAIL PROTECTED] Cc: 'Kevin Miller' Subject: RE: [nant-dev] References and the Framework path If the framework dir is in the path, you can specify that the 'include' should look there. <references> <includes frompath="true" name="System.dll"/> </references> In my environment with VS.Net the %vscomntools%\vsvars32.bat sets this correctly for me. >where system.dll \WINDOWS\Microsoft.NET\Framework\v1.0.3705\system.dll Does that work for you? Side Note: This is probably a user list question. Most of us read both, and if it isn't appropriate, we will just repost on dev and discuss... Later, Scott > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:nant-developers- > [EMAIL PROTECTED]] On Behalf Of Kevin Miller > Sent: Wednesday, July 10, 2002 7:04 AM > To: '[EMAIL PROTECTED]' > Subject: [nant-dev] References and the Framework path > > I apologize if this is a know or just plain a user issue. > > In playing with the vbc task I attempted to add a reference to System.dll. > > <vbc target="library" output="${build.dir}\Foo.dll" debug="${debug}" > optionstrict="true"> > <references><includes name="System.dll"/></references> > </vbc> > > Turning verbose on I saw that the reference was never made unless I added > the full path to the framework dlls > > <!-- Foundation Class Library install path - required as if NAnt cannot > find > the reference it punts --> > <property name="FCL.dir" > value="C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705"/> > > <vbc target="library" output="${build.dir}\Foo.dll" debug="${debug}" > optionstrict="true"> > <references><includes name="${FCL.dir}/System.dll"/></references> > </vbc> > > Have I missed something. Is there an easier way to tell the task where a > framework Dlls are? The main problem is that on different machines this > directory is in different paths (c:\win nt\..., or c:\win\...) In theory I > could possibly derive the path using environment variables but the sysinfo > task only exposes a few. > > <target name="test"> > <sysinfo verbose="true" /> > </target> > > --- > > test: > [sysinfo] Setting system information properties under sys.* > [sysinfo] nant.version = 0.7.9.0 > [sysinfo] sys.os.folder.temp = C:\DOCUME~1\Foo\LOCALS~1\Temp\ > [sysinfo] sys.clr.version = 1.0.3705.209 > [sysinfo] sys.os.platform = Win32NT > [sysinfo] sys.os = Microsoft Windows NT 5.1.2600.0 > [sysinfo] sys.os.version = 5.1.2600.0 > [sysinfo] sys.os.folder.system = C:\WINDOWS\System32 > > Kevin Miller ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Two, two, TWO treats in one. http://thinkgeek.com/sf _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
