[Nant-users] CodeDomProvider for C# could not be created - Please help
Title: Message Does anyone have an idea on this? It's almost like something in not installed correctly or configured correctly on our build machine. Any help would be greatly appreciated. Thanks, Evan A. Bonnett Reynolds Reynolds, IT ERA Integrated Desking Development 937-485-8577 Confidentiality Statement: this message is confidential and may contain confidential information. it is intended only for the individual[s] named herein. If this message is being sent from a member of the legal department, it may also be legally privileged. if you are not the named addressee[s] you must delete this email immediately. do not disseminate, distribute or copy. -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Todd, Craig MSent: Thursday, March 17, 2005 3:29 PMTo: nant-users@lists.sourceforge.netSubject: [Nant-users] CodeDomProvider for C# could not be created Guys, I get this when I call a target that contains a script language="c#" tag. Any ideas? My build scripts work on my box but now I'm trying to get them working on the build box. I have downloaded the latest stable build for nant and nantcontrib. Thanks, Evan CodeDomProvider for 'c#' could not be created.: NAnt.Core.BuildException: D:\Projects\Generations Series\EID\3.1\NAntBuild\Project.build(90,4): CodeDomProvider for 'c#' could not be created. --- System.TypeLoadException: Could not load type c# from assembly NAnt. DotNetTasks, Version=0.85.1869.0, Culture=neutral, PublicKeyToken=null. at System.Type.GetType(String typeName, Boolean throwOnError, Boolean ignoreCase) at NAnt.DotNet.Tasks.ScriptTask.CreateCompilerInfo(String language) --- End of inner exception stack trace --- at NAnt.DotNet.Tasks.ScriptTask.CreateCompilerInfo(String language) at NAnt.DotNet.Tasks.ScriptTask.ExecuteTask() at NAnt.Core.Task.Execute() at NAnt.Core.Target.Execute() at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies) at NAnt.Core.Tasks.CallTask.ExecuteTask() at NAnt.Core.Task.Execute() at NAnt.Core.Target.Execute() at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies) at NAnt.Core.Tasks.CallTask.ExecuteTask() at NAnt.Core.Task.Execute() at NAnt.Core.TaskContainer.ExecuteChildTasks() at NAnt.Core.Tasks.LoopTask.ExecuteChildTasks() at NAnt.Core.Tasks.LoopTask.DoWork(String[] propVals) at NAnt.Core.Tasks.LoopTask.DoWorkOnFileLines(String filename) at NAnt.Core.Tasks.LoopTask.ExecuteTask() at NAnt.Core.Task.Execute() at NAnt.Core.Target.Execute() at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies) at NAnt.Core.Project.Execute() at NAnt.Core.Project.Run() Total time: 2.5 seconds. Evan Bonnett
[Nant-users] Property not being set when including buildfile
Title: Property not being set when including buildfile
Hi all,
It's been a while. Here's my problem:
From the main buildfile, I iterate through a file and pull the csproj file. Then, I generate the buildfile using XSLT and the csproj file and call the generated build file. Below is an excerpt from the generated build file that is not working and I don't know why. ( ${project.settings} is the location of the project specific variables file with a .include extension)
?xml version=1.0 encoding=utf-8?
project default=default name=DeskingAppLauncher
include buildfile=${project.settings} /
ifnot test=${property::exists('project.ndoc.run')}
property name=project.ndoc.run value=true /
/ifnot
Now, the include file contains the following text:
project xmlns=http://nant.sf.net/schemas/nant-0.85.win32.net-1.0.xsd
property name=project.ndoc.run value=true /
property name=keyfile.path value=RR.snk /
property name=BuildStart.recipients value=[EMAIL PROTECTED] /
proporty name=BuildFailed.recipients value=[EMAIL PROTECTED] /
/project
So why, when I include the file, do I get the following build output?
BUILD FAILED
c:\temp\~ConfigMgmt\Desking\ApplicationLauncher\Builds\latest\ApplicationLauncher.build(313,10):
Property evaluation failed.
_expression_: ${keyfile.path}
:
NAnt.Core.BuildException: c:\temp\~ConfigMgmt\Desking\ApplicationLauncher\Builds\latest\ApplicationLauncher.build
(313,10):
Property evaluation failed.
_expression_: ${keyfile.path}
--- Property 'keyfile.path' has not been set.:
NAnt.Core.BuildException: Property 'keyfile.path' has not been set.
at NAnt.Core.ExpressionEvaluator.GetPropertyValue(String propertyName) in C:\DOCUME~1\drieseng\LOCALS~1\Temp\t
mp76E.tmp\src\NAnt.Core\ExpressionEvaluator.cs:line 141
at NAnt.Core.ExpressionEvaluator.EvaluateProperty(String propertyName) in C:\DOCUME~1\drieseng\LOCALS~1\Temp\t
mp76E.tmp\src\NAnt.Core\ExpressionEvaluator.cs:line 57
at NAnt.Core.ExpressionEvalBase.ParseValue() in C:\DOCUME~1\drieseng\LOCALS~1\Temp\tmp76E.tmp\src\NAnt.Core\Ex
pressionEvalBase.cs:line 597
--- End of inner exception stack trace ---
at NAnt.Core.PropertyDictionary.EvaluateEmbeddedExpressions(String input, Location location, Hashtable state,
Stack visiting) in C:\DOCUME~1\drieseng\LOCALS~1\Temp\tmp76E.tmp\src\NAnt.Core\PropertyDictionary.cs:line 380
at NAnt.Core.PropertyDictionary.ExpandProperties(String input, Location location, Hashtable state, Stack visit
ing) in C:\DOCUME~1\drieseng\LOCALS~1\Temp\tmp76E.tmp\src\NAnt.Core\PropertyDictionary.cs:line 285
at NAnt.Core.PropertyDictionary.ExpandProperties(String input, Location location) in C:\DOCUME~1\drieseng\LOCA
LS~1\Temp\tmp76E.tmp\src\NAnt.Core\PropertyDictionary.cs:line 253
at NAnt.Core.AttributeConfigurator.InitializeAttribute(PropertyInfo propertyInfo) in C:\DOCUME~1\drieseng\LOCA
LS~1\Temp\tmp76E.tmp\src\NAnt.Core\Element.cs:line 678
at NAnt.Core.AttributeConfigurator.Initialize() in C:\DOCUME~1\drieseng\LOCALS~1\Temp\tmp76E.tmp\src\NAnt.Core
\Element.cs:line 553
at NAnt.Core.Element.InitializeXml(XmlNode elementNode, PropertyDictionary properties, FrameworkInfo framework
) in C:\DOCUME~1\drieseng\LOCALS~1\Temp\tmp76E.tmp\src\NAnt.Core\Element.cs:line 287
at NAnt.Core.Element.Initialize(XmlNode elementNode, PropertyDictionary properties, FrameworkInfo framework) i
n C:\DOCUME~1\drieseng\LOCALS~1\Temp\tmp76E.tmp\src\NAnt.Core\Element.cs:line 269
at NAnt.Core.Element.Initialize(XmlNode elementNode) in C:\DOCUME~1\drieseng\LOCALS~1\Temp\tmp76E.tmp\src\NAnt
.Core\Element.cs:line 192
at NAnt.Core.AttributeConfigurator.InitializeBuildElement(XmlNode childNode, Element buildElement, Type elemen
tType) in C:\DOCUME~1\drieseng\LOCALS~1\Temp\tmp76E.tmp\src\NAnt.Core\Element.cs:line 1128
at NAnt.Core.AttributeConfigurator.InitializeBuildElementCollection(PropertyInfo propertyInfo) in C:\DOCUME~1\
drieseng\LOCALS~1\Temp\tmp76E.tmp\src\NAnt.Core\Element.cs:line 945
at NAnt.Core.AttributeConfigurator.Initialize() in C:\DOCUME~1\drieseng\LOCALS~1\Temp\tmp76E.tmp\src\NAnt.Core
\Element.cs:line 557
at NAnt.Core.Element.InitializeXml(XmlNode elementNode, PropertyDictionary properties, FrameworkInfo framework
) in C:\DOCUME~1\drieseng\LOCALS~1\Temp\tmp76E.tmp\src\NAnt.Core\Element.cs:line 287
at NAnt.Core.Element.Initialize(XmlNode elementNode, PropertyDictionary properties, FrameworkInfo framework) i
n C:\DOCUME~1\drieseng\LOCALS~1\Temp\tmp76E.tmp\src\NAnt.Core\Element.cs:line 269
at NAnt.Core.Element.Initialize(XmlNode elementNode) in C:\DOCUME~1\drieseng\LOCALS~1\Temp\tmp76E.tmp\src\NAnt
.Core\Element.cs:line 192
at NAnt.Core.Project.CreateTask(XmlNode taskNode, Target target) in C:\DOCUME~1\drieseng\LOCALS~1\Temp\tmp76E.
tmp\src\NAnt.Core\Project.cs:line 998
at NAnt.Core.Target.Execute() in C:\DOCUME~1\drieseng\LOCALS~1\Temp\tmp76E.tmp\src\NAnt.Core\Target.cs:line 24
7
at
RE: [Nant-users] Property not being set when including buildfile
Thanks Merrill. Appreciate the help. That was it. Thanks, Evan A. Bonnett Reynolds Reynolds, IT ERA Integrated Desking Development 937-485-8577 Confidentiality Statement: this message is confidential and may contain confidential information. it is intended only for the individual[s] named herein. If this message is being sent from a member of the legal department, it may also be legally privileged. if you are not the named addressee[s] you must delete this email immediately. do not disseminate, distribute or copy. -Original Message- From: Merrill Cornish [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 15, 2005 12:08 PM To: Bonnett, Evan A; nant-users@lists.sourceforge.net Subject: Re: [Nant-users] Property not being set when including buildfile Evan, If I read this right, your two files are in different namespaces, so the property names are actually different. Merrill --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95alloc_id396op=click ___ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
RE: [Nant-users] Compare nAnt and BuildIt
If you need any flexibility at all, use Nant. I did a comparison and, while it was a long time ago, I seem to remember that control of the build process is largely hidden from the user. If you need specifics, I can probably dig up a summary. One thing I seem to remember is that BuildIt prefers project references. They recommend that you have a master solution with ALL projects in it. This is not a good idea as VS.NET does not handle large numbers of projects in a single solution well. Also, if you have broken your solutions up for logical grouping reasons, references become a problem when developers get latest. Sure, there may be ways around these problems but I didn't spend time looking. It was evident to me that Nant was the superior product. Evan A. Bonnett Reynolds and Reynolds, IT -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Manish Jain Sent: Monday, September 20, 2004 9:32 PM To: [EMAIL PROTECTED] Subject: [Nant-users] Compare nAnt and BuildIt I am new to building tools, Appreciate if you can help on this: Can we compare nAnt and BuildIt to build .NET Application? If yes pls let me know which is better and why ? Thanks in Advance Manish --- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php ___ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users --- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php ___ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
[Nant-users] Deploying to remote machines
Title: Message Hi all, What is the recommended way to deploy to remote machines? I build on W2003 Enterprise, create a tar ball and ftp to linux machines. So, if I create the directory structure on the build machine then tar it, what would be the "recommended practice" to get that tar to another machine? Thanks, Evan A. Bonnett Reynolds and Reynolds, IT ERA Integrated Desking Development 937-485-8577 58577
RE: [Nant-users] Deploying to remote machines
Title: RE: [Nant-users] Deploying to remote machines Hmmm, well being that we currently ftp, I would agree with you that I should just use the scp task. Thanks, Gary. Evan A. Bonnett Reynolds and Reynolds, IT ERA Integrated Desking Development 937-485-8577 58577 -Original Message- From: Gary Feldman [mailto:[EMAIL PROTECTED]] Sent: Monday, September 13, 2004 12:25 PM To: Bonnett, Evan A; [EMAIL PROTECTED] Subject: Re: [Nant-users] Deploying to remote machines From: Bonnett, Evan A [EMAIL PROTECTED] Sent: Monday, September 13, 2004 11:43 AM What is the recommended way to deploy to remote machines? I build on W2003 Enterprise, create a tar ball and ftp to linux machines. So, if I create the directory structure on the build machine then tar it, what would be the recommended practice to get that tar to another machine? Much depends upon your internal setup, administration and security constraints. Probably the best approach is to use the scp task from the NantContrib project. I haven't used it, so I don't know whether it requires Cygwin or how well it works, but it is on my long term list. For the moment, we're using Samba to mount the UNIX disks, and vanilla copy. Samba raises its own set of administrative and security issues, but if you already have it, there's no reason not to use it. Gary
RE: [Nant-users] Build process unification
Title: Message As someone that is 4 months into NAnt, I think that is an excellent idea. It really took me a lot to understand what the best practices and standards are. This is because they are unspoken, kind of implied. However, if you are new to 1) configuration management and 2) build tools in general, well you have a double whammy. I thank all of you in the forum for answering my questions. Evan A. Bonnett Reynolds and Reynolds, IT -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jaroslaw KowalskiSent: Thursday, September 09, 2004 8:35 AMTo: [EMAIL PROTECTED]Subject: [Nant-users] Build process unification Hi! Inspired by the Gump project, Istarted looking at various open source projects (log4net, NDoc, NAnt, NUnit, ICSharpCode.*) to see how they are built and how they interoperate. The typical problem is: you want to build a component (one or more DLLs + some EXEs) based on a set of other pre-built components that is shipped along with your code or required to be provided. For example. Nant requires log4net, NDoc, NUnit andICSharpCode.*. ICSharpCode.SharpCvsLib requires log4net (AFAIR) and so on. Unfortunately the build files for each of the packages are very different. The seem to make different assumptions about the system they are running on and the system they are targetting. For example, log4net by default builds for all the frameworks while Nant builds just for the current framework. log4net doesn't fail when there's no signing key, while some other projects do. There are also differences in property names used to direct the build process. Do you think it would be feasible to create something like a ".NET OSS Build Standard" based on nant scripts that could then be adopted by all the projects. I think that it would greatly simplify the development process and integration among various projects. I think we could codify the following naming and semantics for: 1. Standard target names (build, install, clean, dist, test, doc, ...) 2. A standard way to set default/release build (using properties or targets) 3. A standard way to set and use the target framework 4. Standard directory layout (bin, build, src, doc, ...), signing key file placement and generation 5. A standard way of specifying external dependencies and output file placement (there should always be a clean option to use other binary than the one that comes with the package). 6. Standard compiler defines (NET, MONO, MONO_1_0, NETCF and so on) 7. Optimization options 8. Package generation tools (source package, binary package, installer package) 9. A way to structure your projects, split them into build files and manage dependencies 10. A standard way (directory structure, naming) to provide unit tests and a way to run them, generate and store reports. I believe that now, 3 years after the .NET release, there's been a lot of "best practice" accumulated in the community. It could be easily turned into a standard set of guidelines for the projects to follow. With this in place we could have a "NAnt Project Wizard" that would generate the standard build file based on these assumptions. Maybe we could include some of this logic in the NAnt itself (for example 2, 6, 7, perhaps also 5could become NAnt options). What do you think? Jarek
RE: [Nant-users] references to interop dll's
Title: RE: [Nant-users] references to interop dll's
So, what is the preferred practice to do this? Is it to create the wrappers and store the wrapped component in source control to be pulled at build-time? Or is it to wrap at build-time?
xsl:for-each select=../../References/Reference
xsl:choose
xsl:when test=@WrapperTool='tlbimp'
script language=C#
code
[System.Runtime.InteropServices.DllImport( oleaut32.dll, CharSet =System.Runtime.InteropServices.CharSet.Auto, PreserveSig = false,SetLastError=true )]
private static extern void QueryPathOfRegTypeLib( ref Guid guid, Int16 wVerMajor, Int16 wVerMinor, Int32 lcid, [System.Runtime.InteropServices.MarshalAs(System.Runtime.InteropServices.UnmanagedType.VBByRefStr)] ref StringBuilder lpbstrPathName);
public static void ScriptMain(Project project)
{
try
{
StringBuilder pathResult = new StringBuilder(1024); Guid g = new Guid(xsl:value-of select=@Guid /);
QueryPathOfRegTypeLib(ref g,
xsl:value-of select=@VersionMajor /,
xsl:value-of select=@VersionMinor /,
xsl:value-of select=@Lcid /,
ref pathResult);
project.Properties[xsl:value-of select=@Name /.path] = pathResult.ToString();
}
catch (Exception e)
{
throw e;
}
}
/code
/script
tlbimp output=${{config.binary.dir}}/[EMAIL PROTECTED] typelib=[EMAIL PROTECTED] keyfile=src\RR.snk //xsl:when
... And so on
Is there a better way to find the path for the COM object to be wrapped?
Is this a good way to do this?
Thanks,
Evan A. Bonnett
Reynolds and Reynolds, IT
ERA Integrated Desking Development
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Bert Jan Lappenschaar
Sent: Tuesday, August 17, 2004 8:28 AM
To: Ian MacLean; Gert Driesen
Cc: [EMAIL PROTECTED]
Subject: RE: [Nant-users] references to interop dll's
Thanks. I created new wrapper DLL's using the AXIMP tool. These do have the names that Nant expects. I don't know how the old wrapper DLLs were created. The developers who programmed the app have left the company so I can't ask. Let's forget about it.
Bert-Jan
-Oorspronkelijk bericht-
Van: Ian MacLean [mailto:[EMAIL PROTECTED]]
Verzonden: dinsdag 17 augustus 2004 9:00
Aan: Gert Driesen
CC: Bert Jan Lappenschaar; [EMAIL PROTECTED]
Onderwerp: Re: [Nant-users] references to interop dll's
- Original Message - From: Bert Jan Lappenschaar
[EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, August 16, 2004 3:26 PM
Subject: [Nant-users] references to interop dll's
I am running into the following problem:
I use a nant script that has produces an exe. It has a references to
Interop.TGXLib.dll and AxInterop.TGXLib.dll (wrapper dll's).
Everything compiles fine.
Now, when I run the program I just compiled, it is looking for dll's
TGXLib.dll and AxTGXLib.dll, but it can't find them because these
names
are wrong, it should look for Interop.TGXLib.dll and
AxIntererop.TGXLib.dll.
no - this is incorrect. the interop dlls are wrappers for the
non-interop ones. You need both to be available at runtime. The interop
ones should be in the same directory as you app ( or somewhere loadable
by .net ) while the com dlls ( TGXLib.dll and AxTGXLib.dll ) will need
to be registered using regsvr32 or some other com registration method.
If I rename my interop dll's to TGXLib.dll and AxTGXLib.dll,
everything
works fine.
I find that very surprising - if they are true interp dlls. I think as
Gert said, you had better package up a sample.
So the names of the references in the exe are wrong. The part
'interop.'
has dropped off.
Ian
---
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
___
Nant-users mailing list
[EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
RE: [Nant-users] references to interop dll's
Title: RE: [Nant-users] references to interop dll's Well, I humble myself and give all credit to a person named Ryan Cromwell. You probably recognize the name. I just modified the script that he sent me to suit my needs. In fact, I also use the same thing for aximp. I am not using the solution task because I am trying to create something for organization-wide use. I'd like to make it easy enough for the delivery group to just plug any project in and have it go. I think the solution task will crimp the flexibility. Thanks, Evan A. Bonnett Reynolds and Reynolds, IT ERA Integrated Desking Development Evan A. Bonnett Reynolds and Reynolds, IT ERA Integrated Desking Development 937-485-8577 58577 -Original Message- From: Ian MacLean [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 18, 2004 10:38 AM To: Bonnett, Evan A Cc: [EMAIL PROTECTED] Subject: Re: [Nant-users] references to interop dll's Bonnett, Evan A wrote: So, what is the preferred practice to do this? Is it to create the wrappers and store the wrapped component in source control to be pulled at build-time? Or is it to wrap at build-time? the nay-sayers will say that you should *never* put the outputs of a tool in source control. However with interop dlls I think you can go either way. If the underlying dll isn't going to change very often then I don't see any harm in generating the wrapper once and using it each build. xsl:for-each select=../../References/Reference xsl:choose xsl:when test=@WrapperTool='tlbimp' script language=C# code [System.Runtime.InteropServices.DllImport( oleaut32.dll, CharSet = System.Runtime.InteropServices.CharSet.Auto, PreserveSig = false,SetLastError=true )] private static extern void QueryPathOfRegTypeLib( ref Guid guid, Int16 wVerMajor, Int16 wVerMinor, Int32 lcid, script snipped ... And so on Is there a better way to find the path for the COM object to be wrapped? wow - I'm impressed, thats quite a cool way to lookup the location. You could manually account for all the dlls that need wrapping and do that in a seperate script. However if automating the conversion from vs projects is going to be a standard part of your build process then it seems as good a way as any. Is there any reason you decided not to use the solution task ? or did someone ask you that already ? Ian Is this a good way to do this? Thanks, Evan A. Bonnett Reynolds and Reynolds, IT ERA Integrated Desking Development
[Nant-users] RE: FW: XSLT Generated Build File with COM references
Title: RE: FW: XSLT Generated Build File with COM references
So, is there a command line interface for this? Looks like it will do the job if I can get to it from nant. If not, I can always operate on the assumption that the lib is in a particular folder, defined by the particular project variable. I'd rather search for the GUID though.
Does anyone have an example?
Evan A. Bonnett
Reynolds and Reynolds, IT
-Original Message-
From: Ian MacLean [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 12, 2004 11:12 AM
To: Bonnett, Evan A
Cc: 'Gert Driesen'; [EMAIL PROTECTED]
Subject: Re: FW: XSLT Generated Build File with COM references
Hi Evan,
If you just want to find the location of the dll then you need to search
the registry for that guid - or you might be able to use oleview to
help. On my machine its %SystemRoot%\System32\shdocvw.dll
To use COM or ActiveX components from .net code you need to create
wrapper assemblies using eiather tlbimp.exe or aximp.exe. So for
SHDocVw.dll the wrapper will be AxInterop.SHDocVw.dll. VisualStudio does this behind the scenes for you. NAnt has a TlbImp task and there is an AxImp task in NAntContrib. Once you've created the wrappers ( or interop assemblies as they are correctly known ) you can reference them as you would any other assembly from your csc tasks.
Its probably worth reading up on both those commandline tools and the interop process in gereral - there is plenty of stuff on MSDN.
As for copying to the build directory you only need to copy the interop assemblies. The dlls they wrap will be located by the COM subsystem at runtime ( using the GUID lookup in the registry ).
Ian
Bonnett, Evan A wrote:
Hey guys,
Sorry to hit you up directly like this. I posted this but no one came
to the rescue. Do you have any thoughts on this? I'm just a bit in
the dark here. Let me know if I am being vague.
TIA,
Evan A. Bonnett
Reynolds and Reynolds, IT
ERA Integrated Desking Development
937-485-8577
58577
-Original Message-
From: Bonnett, Evan A
Sent: Wednesday, August 11, 2004 1:42 PM
To: Nant-Users (E-mail)
Subject: XSLT Generated Build File with COM references
I am strong naming my assemblies now. What is the process to deal with
COM and ActiveX components? I am running the csproj file through an
XSLT to generate the Nant build file. Does anyone have a step by step
on when to do what with these components?
One problem I am running into is that the actual dll file name is not
what the attribute name is in the csproj file. Here is an example:
Reference
Name = SHDocVw
Guid = {EAB22AC0-30C1-11CF-A7EB-C05BAE0B}
VersionMajor = 1
VersionMinor = 1
Lcid = 0
WrapperTool = tlbimp
/
Reference
Name = AxSHDocVw
Guid = {EAB22AC0-30C1-11CF-A7EB-C05BAE0B}
VersionMajor = 1
VersionMinor = 1
Lcid = 0
WrapperTool = aximp
/
But the actual dll names are AxInterop.SHDocVw.dll and
Interop.SHDocVw.dll. Anyone have a simple way to map the names? Also,
how do you resolve the location of these dll's? I am having trouble
pulling these into the bin folder when I build. Is there a very
flexible and generic way to resolve the locations based on the GUID? I
am looking for a solution that can be reused throughout the
organization so it can't be project specific.
Thanks a bunch,
Evan A. Bonnett
Reynolds and Reynolds, IT
--
Ian MacLean, Developer,
ActiveState, a division of Sophos
http://www.ActiveState.com
[Nant-users] RE: XSLT Generated Build File with COM references
Title: RE: XSLT Generated Build File with COM references
Does ANYONE have any insight on this problem? Please... I thought about setting project specific variables that have a name equal to the reference name and a value of the dll name. That could serve as a mapping mechanism but it doesn't seem flexible or generic enough to be reused throughout an organization.
Thoughts? Anyone? Beuller? Beuller?
Evan A. Bonnett
Reynolds and Reynolds, IT
-Original Message-
From: Bonnett, Evan A
Sent: Wednesday, August 11, 2004 1:42 PM
To: Nant-Users (E-mail)
Subject: XSLT Generated Build File with COM references
I am strong naming my assemblies now. What is the process to deal with COM and ActiveX components? I am running the csproj file through an XSLT to generate the Nant build file. Does anyone have a step by step on when to do what with these components?
One problem I am running into is that the actual dll file name is not what the attribute name is in the csproj file. Here is an example:
Reference
Name = SHDocVw
Guid = {EAB22AC0-30C1-11CF-A7EB-C05BAE0B}
VersionMajor = 1
VersionMinor = 1
Lcid = 0
WrapperTool = tlbimp
/
Reference
Name = AxSHDocVw
Guid = {EAB22AC0-30C1-11CF-A7EB-C05BAE0B}
VersionMajor = 1
VersionMinor = 1
Lcid = 0
WrapperTool = aximp
/
But the actual dll names are AxInterop.SHDocVw.dll and Interop.SHDocVw.dll. Anyone have a simple way to map the names? Also, how do you resolve the location of these dll's? I am having trouble pulling these into the bin folder when I build. Is there a very flexible and generic way to resolve the locations based on the GUID? I am looking for a solution that can be reused throughout the organization so it can't be project specific.
Thanks a bunch,
Evan A. Bonnett
Reynolds and Reynolds, IT
[Nant-users] RE: FW: XSLT Generated Build File with COM references
Title: RE: FW: XSLT Generated Build File with COM references
Thanks Ian. I appreciate the help... A lot. I'm trying like hell to get this build process up and running in production.
Evan A. Bonnett
Reynolds and Reynolds, IT
-Original Message-
From: Ian MacLean [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 12, 2004 11:12 AM
To: Bonnett, Evan A
Cc: 'Gert Driesen'; [EMAIL PROTECTED]
Subject: Re: FW: XSLT Generated Build File with COM references
Hi Evan,
If you just want to find the location of the dll then you need to search
the registry for that guid - or you might be able to use oleview to
help. On my machine its %SystemRoot%\System32\shdocvw.dll
To use COM or ActiveX components from .net code you need to create
wrapper assemblies using eiather tlbimp.exe or aximp.exe. So for
SHDocVw.dll the wrapper will be AxInterop.SHDocVw.dll. VisualStudio does this behind the scenes for you. NAnt has a TlbImp task and there is an AxImp task in NAntContrib. Once you've created the wrappers ( or interop assemblies as they are correctly known ) you can reference them as you would any other assembly from your csc tasks.
Its probably worth reading up on both those commandline tools and the interop process in gereral - there is plenty of stuff on MSDN.
As for copying to the build directory you only need to copy the interop assemblies. The dlls they wrap will be located by the COM subsystem at runtime ( using the GUID lookup in the registry ).
Ian
Bonnett, Evan A wrote:
Hey guys,
Sorry to hit you up directly like this. I posted this but no one came
to the rescue. Do you have any thoughts on this? I'm just a bit in
the dark here. Let me know if I am being vague.
TIA,
Evan A. Bonnett
Reynolds and Reynolds, IT
ERA Integrated Desking Development
937-485-8577
58577
-Original Message-
From: Bonnett, Evan A
Sent: Wednesday, August 11, 2004 1:42 PM
To: Nant-Users (E-mail)
Subject: XSLT Generated Build File with COM references
I am strong naming my assemblies now. What is the process to deal with
COM and ActiveX components? I am running the csproj file through an
XSLT to generate the Nant build file. Does anyone have a step by step
on when to do what with these components?
One problem I am running into is that the actual dll file name is not
what the attribute name is in the csproj file. Here is an example:
Reference
Name = SHDocVw
Guid = {EAB22AC0-30C1-11CF-A7EB-C05BAE0B}
VersionMajor = 1
VersionMinor = 1
Lcid = 0
WrapperTool = tlbimp
/
Reference
Name = AxSHDocVw
Guid = {EAB22AC0-30C1-11CF-A7EB-C05BAE0B}
VersionMajor = 1
VersionMinor = 1
Lcid = 0
WrapperTool = aximp
/
But the actual dll names are AxInterop.SHDocVw.dll and
Interop.SHDocVw.dll. Anyone have a simple way to map the names? Also,
how do you resolve the location of these dll's? I am having trouble
pulling these into the bin folder when I build. Is there a very
flexible and generic way to resolve the locations based on the GUID? I
am looking for a solution that can be reused throughout the
organization so it can't be project specific.
Thanks a bunch,
Evan A. Bonnett
Reynolds and Reynolds, IT
--
Ian MacLean, Developer,
ActiveState, a division of Sophos
http://www.ActiveState.com
[Nant-users] XSLT Generated Build File with COM references
Title: XSLT Generated Build File with COM references
I am strong naming my assemblies now. What is the process to deal with COM and ActiveX components? I am running the csproj file through an XSLT to generate the Nant build file. Does anyone have a step by step on when to do what with these components?
One problem I am running into is that the actual dll file name is not what the attribute name is in the csproj file. Here is an example:
Reference
Name = SHDocVw
Guid = {EAB22AC0-30C1-11CF-A7EB-C05BAE0B}
VersionMajor = 1
VersionMinor = 1
Lcid = 0
WrapperTool = tlbimp
/
Reference
Name = AxSHDocVw
Guid = {EAB22AC0-30C1-11CF-A7EB-C05BAE0B}
VersionMajor = 1
VersionMinor = 1
Lcid = 0
WrapperTool = aximp
/
But the actual dll names are AxInterop.SHDocVw.dll and Interop.SHDocVw.dll. Anyone have a simple way to map the names? Also, how do you resolve the location of these dll's? I am having trouble pulling these into the bin folder when I build. Is there a very flexible and generic way to resolve the locations based on the GUID? I am looking for a solution that can be reused throughout the organization so it can't be project specific.
Thanks a bunch,
Evan A. Bonnett
Reynolds and Reynolds, IT
RE: [Nant-users] utiltiy to convert *.*proj to *.build
Title: RE: [Nant-users] utiltiy to convert *.*proj to *.build Or you can use an XSLT to transform the proj file to a build file. That's a bit more involved. If you don't need to do things that Slingshot won't do, use slingshot. Evan A. Bonnett Reynolds and Reynolds, IT ERA Integrated Desking Development 937-485-8577 58577 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Astie, Sebastien Sent: Wednesday, August 04, 2004 1:09 PM To: Felice Vittoria; Nant-Users (E-mail) Subject: RE: [Nant-users] utiltiy to convert *.*proj to *.build Felice, You can use the SlingShot tool from the NantContrib project. Sebastien -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Felice Vittoria Sent: Wednesday, August 04, 2004 10:00 AM To: Nant-Users (E-mail) Subject: [Nant-users] utiltiy to convert *.*proj to *.build Hello all, I'm sure this was answered before ... is there a tool that will convert all of my *.csproj and *.vbproj files into Nant *.build files? If so, where can I get this tool? Thanks, Felice --- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com ___ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users --- The information contained in this e-mail message, and any attachment, is confidential and for use solely by the intended recipient. If you have received this message in error, please delete this message immediately. Although Moody's KMV makes every effort to protect its computing environment from malicious code, Moody's KMV is not responsible for any virus or other type of suspect code that may be transferred via this e-mail message. --- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com ___ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
RE: [Nant-users] Obfuscation and NAnt
Title: Message I am looking into that too. May I call upon you if necessary? Sounds pretty straight forward but it's good to have a resource. Thanks, Evan A. Bonnett Reynolds and Reynolds, IT -Original Message-From: Joel Ross [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 14, 2004 3:13 PMTo: [EMAIL PROTECTED]Subject: RE: [Nant-users] Obfuscation and NAnt I do. I use an exec task to wrap it, and it works just fine. Make a valid XML config file for DotObfuscator, then call it from the command line. If you want more info, let me know Joel http://www.rosscode.com From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rick CaseySent: Wednesday, July 14, 2004 2:46 PMTo: [EMAIL PROTECTED]Subject: [Nant-users] Obfuscation and NAnt Does anyone use DotObfuscator in their builds? Or any other obfuscation utility for that matter... Rick Casey Octane8 Platform Development Manager Sungard Workflow Solutions (205) 408-3615
RE: [Nant-users] Ndoc errors - It can't access an xslt because it 's being used by another process
Title: RE: [Nant-users] Ndoc errors - It can't access an xslt because it's being used by another process NAnt 0.85 (Build 0.85.1653.0; net-1.0.win32; nightly; 7/11/2004) I am using the nightly, hoping that it becomes a stable release by the time I hit production. I am getting this error sporadically. Evan A. Bonnett Reynolds and Reynolds, IT ERA Integrated Desking Development 937-485-8577 58577 -Original Message- From: Gert Driesen [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 14, 2004 2:40 AM To: Bonnett, Evan A; [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [Nant-users] Ndoc errors - It can't access an xslt because it's being used by another process Evan, According to Kevin Downs (NDoc), this issue was fixed in February, and the NDoc binaries in NAnt (cvs) are from April (post beta 1). What version of NAnt are you using ? Gert - Original Message - From: Bonnett, Evan A [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, July 13, 2004 11:42 PM Subject: [Nant-users] Ndoc errors - It can't access an xslt because it's being used by another process I understand this is a known issue. The Ndoc folks say it is fixed but that the ndoc task uses an out of date version of ndoc. Can someone shed some light on this? Here is the exact error... c:\temp\~ConfigMgmt\Desking\Core.Data\Builds\latest\Core.Data.build(166,6): [ndoc] Error building documentation. The process cannot access the file doc.xslt because it is being used by another process. Can anyone assist me here? Thanks, Evan A. Bonnett Reynolds and Reynolds, IT ERA Integrated Desking Development 937-485-8577 58577
[Nant-users] Simple Question on DOS Commands
Title: Simple Question on DOS Commands So, how do I issue simple dos commands and make the output appear on the console? For example, I'm trying to debug something and I need to know the current directory. I just need the equivalent of typing cd. Thanks, Evan A. Bonnett Reynolds and Reynolds, IT
[Nant-users] Invalid ResX input?
Title: Invalid ResX input? I am having a bit of trouble with my build. This is a third party project that we have the source code to. Can someone tell me what's happening here so I can make better sense of what's going wrong? The project compiles fine in VS.NET. \Menus\MenuCommand.resx' Writing resource file... Done. Read in 0 resources from 'c:\temp\~ConfigMgmt\Desking\Core.MagicLibrary\Builds\latest\src \Menus\MenuControl.resx' Writing resource file... Done. error: Invalid ResX input. 1 error(s). Thanks, Evan A. Bonnett Reynolds and Reynolds, IT ERA Integrated Desking Development 937-485-8577 58577
RE: [Nant-users] Invalid ResX input?
Title: RE: [Nant-users] Invalid ResX input? [resgen] Starting 'C:\DOCUME~1\BonnetEA\LOCALS~1\Temp\2988a24c2d514ad0baf629abc510eddc\resgen.exe ( c:\temp\~ConfigMgmt\Desking\Core.MagicLibrary\Builds\latest\src\NAG\NAGScreen.resx c:\temp\~ConfigMgmt\Desking\Core.Magi cLibrary\Builds\latest\src\NAG\NAGScreen.resources)' in 'C:\DOCUME~1\BonnetEA\LOCALS~1\Temp\2988a24c2d514ad0baf629abc510eddc ' error: Invalid ResX input. 1 error(s). It is the file that I suspected. But I'm not sure why. Would it help to run resgen via command line? Evan A. Bonnett Reynolds and Reynolds, IT ERA Integrated Desking Development 937-485-8577 58577 -Original Message- From: Gert Driesen [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 14, 2004 2:14 PM To: Bonnett, Evan A; [EMAIL PROTECTED] Subject: Re: [Nant-users] Invalid ResX input? Evan, Can you try to run the build in verbose mode (NAnt.exe -verbose ) ? Currently, NAnt only outputs the name of the output file (in verbose mode) when the output file is not up-to-date (and not when it just doesn't exist). I'll try upload a new nightly build with an extra log message later today. If running the current nightly build in verbose mode does not provide information on the file its going to create, then you might wanna wait for the next nightly build. Gert - Original Message - From: Bonnett, Evan A [EMAIL PROTECTED] To: 'Gert Driesen' [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Wednesday, July 14, 2004 7:40 PM Subject: RE: [Nant-users] Invalid ResX input? Gert, Yes, I did get that with the latest nightly build. I am not sure what file it is referring to. If you look at the error, it appears as if it finishes one resource file and is moving to the next but does not give the name of the file. It chokes before it can print out the name. I assume that it is going to the next folder down the list in the project to get the 1 resource file out of it. In that case, it is not a 0 length file. I have included the file. Thanks, Evan A. Bonnett Reynolds and Reynolds, IT -Original Message- From: Gert Driesen [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 14, 2004 1:34 PM To: Bonnett, Evan A; [EMAIL PROTECTED] Subject: Re: [Nant-users] Invalid ResX input? Evan, That resx file is probably a zero-length file. Can you verify this ? Do you get this error with the latest nightly build ? Gert - Original Message - From: Bonnett, Evan A [EMAIL PROTECTED] To: 'Gert Driesen' [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Wednesday, July 14, 2004 6:32 PM Subject: [Nant-users] Invalid ResX input? I am having a bit of trouble with my build. This is a third party project that we have the source code to. Can someone tell me what's happening here so I can make better sense of what's going wrong? The project compiles fine in VS.NET. \Menus\MenuCommand.resx' Writing resource file... Done. Read in 0 resources from 'c:\temp\~ConfigMgmt\Desking\Core.MagicLibrary\Builds\latest\src \Menus\MenuControl.resx' Writing resource file... Done. error: Invalid ResX input. 1 error(s). Thanks, Evan A. Bonnett Reynolds and Reynolds, IT ERA Integrated Desking Development 937-485-8577 58577
RE: [Nant-users] Invalid ResX input?
Title: RE: [Nant-users] Invalid ResX input? ResGen gives me the same error so this is not an Nant thing. I'll look at the file and see what's going on. Thanks! Evan A. Bonnett Reynolds and Reynolds, IT ERA Integrated Desking Development 937-485-8577 58577 -Original Message- From: Gert Driesen [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 14, 2004 2:14 PM To: Bonnett, Evan A; [EMAIL PROTECTED] Subject: Re: [Nant-users] Invalid ResX input? Evan, Can you try to run the build in verbose mode (NAnt.exe -verbose ) ? Currently, NAnt only outputs the name of the output file (in verbose mode) when the output file is not up-to-date (and not when it just doesn't exist). I'll try upload a new nightly build with an extra log message later today. If running the current nightly build in verbose mode does not provide information on the file its going to create, then you might wanna wait for the next nightly build. Gert - Original Message - From: Bonnett, Evan A [EMAIL PROTECTED] To: 'Gert Driesen' [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Wednesday, July 14, 2004 7:40 PM Subject: RE: [Nant-users] Invalid ResX input? Gert, Yes, I did get that with the latest nightly build. I am not sure what file it is referring to. If you look at the error, it appears as if it finishes one resource file and is moving to the next but does not give the name of the file. It chokes before it can print out the name. I assume that it is going to the next folder down the list in the project to get the 1 resource file out of it. In that case, it is not a 0 length file. I have included the file. Thanks, Evan A. Bonnett Reynolds and Reynolds, IT -Original Message- From: Gert Driesen [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 14, 2004 1:34 PM To: Bonnett, Evan A; [EMAIL PROTECTED] Subject: Re: [Nant-users] Invalid ResX input? Evan, That resx file is probably a zero-length file. Can you verify this ? Do you get this error with the latest nightly build ? Gert - Original Message - From: Bonnett, Evan A [EMAIL PROTECTED] To: 'Gert Driesen' [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Wednesday, July 14, 2004 6:32 PM Subject: [Nant-users] Invalid ResX input? I am having a bit of trouble with my build. This is a third party project that we have the source code to. Can someone tell me what's happening here so I can make better sense of what's going wrong? The project compiles fine in VS.NET. \Menus\MenuCommand.resx' Writing resource file... Done. Read in 0 resources from 'c:\temp\~ConfigMgmt\Desking\Core.MagicLibrary\Builds\latest\src \Menus\MenuControl.resx' Writing resource file... Done. error: Invalid ResX input. 1 error(s). Thanks, Evan A. Bonnett Reynolds and Reynolds, IT ERA Integrated Desking Development 937-485-8577 58577
[Nant-users] Ftp task?
Title: Ftp task? Is there a need for an ftp task? I tar up all my files and ftp them to my servers. Now that I am getting close to putting Nant into production, I am thinking about an ftp and a tar task. Is this something anyone would be interested in? Just curious. Evan A. Bonnett Reynolds and Reynolds, IT
RE: [Nant-users] Ftp task?
Title: RE: [Nant-users] Ftp task? Let me know when you look into this. I would be glad to contribute to the cause by spearheading the tar/ task. For now, I am going to use the exec / but would like it to be a little cleaner. As soon as I get my build running smooth, I will start to work on the task. By the way, Special thanks to Ryan Cromwell for providing me with an XSLT template and answering a boat load of questions. Evan A. Bonnett Reynolds and Reynolds, IT ERA Integrated Desking Development 937-485-8577 58577 -Original Message- From: Gert Driesen [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 13, 2004 4:45 PM To: Bonnett, Evan A; [EMAIL PROTECTED] Subject: Re: [Nant-users] Ftp task? - Original Message - From: Bonnett, Evan A [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, July 13, 2004 9:37 PM Subject: [Nant-users] Ftp task? Is there a need for an ftp task? I tar up all my files and ftp them to my servers. Now that I am getting close to putting Nant into production, I am thinking about an ftp and a tar task. Is this something anyone would be interested in? A tar task would definitely be interesting, and it should be pretty easy to implement as #ziplib also supports tar. My might need to refactor the existing zip / unzip task, to have more code reuse ... Gert
[Nant-users] Ndoc errors - It can't access an xslt because it's being used by another process
Title: Ndoc errors - It can't access an xslt because it's being used by another process I understand this is a known issue. The Ndoc folks say it is fixed but that the ndoc task uses an out of date version of ndoc. Can someone shed some light on this? Here is the exact error... c:\temp\~ConfigMgmt\Desking\Core.Data\Builds\latest\Core.Data.build(166,6): [ndoc] Error building documentation. The process cannot access the file doc.xslt because it is being used by another process. Can anyone assist me here? Thanks, Evan A. Bonnett Reynolds and Reynolds, IT ERA Integrated Desking Development 937-485-8577 58577
RE: [Nant-users] Valid Framework Identifiers
Title: Message
You
are correct. Thanks!
Evan A. Bonnett
Reynolds and Reynolds,
IT ERA Integrated
Desking Development 937-485-8577 58577
-Original Message-From: Ryan Cromwell
[mailto:[EMAIL PROTECTED] Sent: Wednesday, June 23, 2004
10:24 AMTo: Bonnett, Evan A;
[EMAIL PROTECTED]Subject: RE: [Nant-users] Valid
Framework Identifiers
I'm not positive as i don't use the nightly builds, but seems that it
should be net-1.1, net-1.0, mono-1.0, etc
Original Message Follows
From: "Bonnett, Evan A" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [Nant-users] Valid Framework Identifiers
Date: Wed, 23 Jun 2004 09:36:49 -0400
What are the valid framework identifiers?
I am using the following function but need to know what a valid
param is:
${framework::get-framework-directory('1.0.3705')}
Thanks,
Evan A. Bonnett
Reynolds and Reynolds, IT
ERA Integrated Desking Development
937-485-8577
58577
RE: [Nant-users] Read file contents into nant property?
Title: RE: [Nant-users] Read file contents into nant property? I had the same problem but Jarek sent me this solution. Try it out, adapt as needed. Hope this helps. There's a trick that uses foreach task. Taken from my build script: target name=installer foreach item=Line in=version.txt delim=. property=sooda.major,sooda.minor,sooda.revision,sooda.build ... do something with the properties ... /foreach /target This will read ALL lines from version.txt (there's only one and that's the trick) and set sooda.* properties appropriately. See foreach task documentation for more info. Hope it helps. Jarek Evan A. Bonnett Reynolds and Reynolds, IT ERA Integrated Desking Development -Original Message- From: Sebastian [mailto:[EMAIL PROTECTED]] Sent: Friday, April 23, 2004 9:23 AM To: [EMAIL PROTECTED] Subject: [Nant-users] Read file contents into nant property? Hello! Is there a way to read the content of a file into an nant property? Thanks in advance, Sebastian This message was sent using IMP, the Internet Messaging Program. --- This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek For a limited time only, get FREE Ground shipping on all orders of $35 or more. Hurry up and shop folks, this offer expires April 30th! http://www.thinkgeek.com/freeshipping/?cpg=12297 ___ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
[Nant-users] More Questions on Versioning...
Title: Message Ok, last question on versioning... I think. Gert and others, You say that when using the asminfo task, you should just use the # of days since a certain date (I forget which date but I think it's the date VS was released?) Currently, I use the major.minor.build.revision model now, and my application is at 2.1.0.5. The revision is my daily build. The build is my weekly load build to the testers. The minor is used for releases to the public that are not the majors, and the final #, well you can figure that one out. So, when generating a new asminfo during the daily, weekly, or releasebuild, would I check out the AssemblyInfo.cs file from VSS, generate a new one, and check it back in? Which # (major, minor, build or revision) is incremented with the # of days since that certain date? the revision? Thanks all, Evan A. Bonnett Reynolds and Reynolds, IT ERA Integrated Desking Development
RE: [Nant-users] More Questions on Versioning...
Title: Message Ok. Sounds good. Thanks for the tip. Evan A. Bonnett Reynolds and Reynolds, IT ERA Integrated Desking Development -Original Message-From: Ryan Cromwell [mailto:[EMAIL PROTECTED] Sent: Thursday, April 22, 2004 12:10 PMTo: Bonnett, Evan A; [EMAIL PROTECTED]Cc: [EMAIL PROTECTED]Subject: RE: [Nant-users] More Questions on Versioning... i would suggest using version task's revisiontype=increment for the daily build and revisiontype=automatic when you are going to test. Major and minor or done manually to the .version file that is maintained by the version task. I think that would follow your scheme Original Message Follows From: "Bonnett, Evan A" [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: "'Gert Driesen'" [EMAIL PROTECTED] Subject: [Nant-users] More Questions on Versioning... Date: Thu, 22 Apr 2004 11:00:11 -0400 Ok, last question on versioning... I think. Gert and others, You say that when using the asminfo task, you should just use the # of days since a certain date (I forget which date but I think it's the date VS was released?) Currently, I use the major.minor.build.revision model now, and my application is at 2.1.0.5.The revision is my daily build.The build is my weekly load build to the testers.The minor is used for releases to the public that are not the majors, and the final #, well you can figure that one out. So, when generating a new asminfo during the daily, weekly, or release build, would I check out the AssemblyInfo.cs file from VSS, generate a new one, and check it back in? Which # (major, minor, build or revision) is incremented with the # of days since that certain date? the revision? Thanks all, Evan A. Bonnett Reynolds and Reynolds, IT ERA Integrated Desking Development Watch LIVE baseball games on your computer with MLB.TV, included with MSN Premium!
RE: [Nant-users] XSLT to generate build files
Title: RE: [Nant-users] XSLT to generate build files I will be using solution files for c# projects as a source doc. (at least I think that's the way to go) Evan A. Bonnett Reynolds and Reynolds, IT ERA Integrated Desking Development 937-485-8577 58577 -Original Message- From: Ian MacLean [mailto:[EMAIL PROTECTED]] Sent: Monday, April 19, 2004 10:54 AM To: Bonnett, Evan A Cc: [EMAIL PROTECTED] Subject: Re: [Nant-users] XSLT to generate build files Evan, depends on what you are using as a source document. You can find an xslt stylesheet to transform vs.net vcproj files here: http://radio.weblogs.com/0106046/VSConvert.xsl You might find that useful even if your input source is somthing different. Ian Bonnett, Evan A wrote: From what I have read, this sounds like the most flexible method to auto-generate build files. Can someone explain how this works and possibly send a template file or sample? Thanks, Evan A. Bonnett Reynolds and Reynolds, IT -- Ian MacLean, Developer, ActiveState, a division of Sophos http://www.ActiveState.com
RE: [Nant-users] Versioning the Assembly
Title: Message While I have not done this yet, I plan on it. Try using the asminfo task to create an AssemblyInfo file on the fly. Then, check in the newly create file. Hope that helps, Evan A. Bonnett Reynolds and Reynolds, IT -Original Message-From: Bob Archer [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 06, 2004 10:49 AMTo: [EMAIL PROTECTED]Subject: [Nant-users] Versioning the Assembly Ok, Here's the kicker. I am using the Version task to create my build number. Now, how do I update the version numbers of the assemblies to match? I assume checking out the AssemblyInfo.cs files which I can do, updating them (not so sure about) and checking them back in. If anyone can point me to something that demos this I would be great full? Thanks, Bob
RE: [Nant-users] Setting a property to output of executable
Title: Message I had the same problem but Jarek sent me this solution. Try it out, adapt as needed. Hope this helps. There's a trick that uses foreach task. Taken from my build script: target name="installer" foreach item="Line" in="version.txt" delim="." property="sooda.major,sooda.minor,sooda.revision,sooda.build" ... do something with the properties ... /foreach /target This will read ALL lines from "version.txt" (there's only one and that's the trick) and set sooda.* properties appropriately. See foreach task documentation for more info. Hope it helps. Jarek Evan A. Bonnett Reynolds and Reynolds, IT -Original Message-From: Nicklas Norling [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 31, 2004 8:19 AMTo: [EMAIL PROTECTED]Subject: [Nant-users] Setting a property to output of executable Hi. I'm looking and looking and just can't find a way to set a property to the value of output from a program. Or from the content of a file or any other communicative and dynamic way. Does anyone have any tips in this area? What I'm doing is running "svn -Nqu status" and what the revision line in a property so I can use the property functions to trim it down to only the number and later use that as information for the build. I can't communicate with files, I must have a property. /Nicke
[Nant-users] Nant vs. BuildIt
Title: Nant vs. BuildIt All, I have been pressured to test MS's BuildIt as our Architecture team is recommending it for all new development projects. I would like to tell you all what I've found: 1) While much of the complexity is hidden from the user, as is so common for MS products, much of the control is also hidden leaving the developer one choice; to modify the source code. 2) MS recommends that you go with a single solution whenever possible so that VS can manage the dependencies. When not possible, a partitioned single solution is recommended where there is a master solution that the build process uses and several sub-solutions that development team uses. What they failed to mention is that in order to use project references , developers will have to reset their references EVERY TIME they get the latest code. 3) BuildIt does not have near the flexibility that Nant has and as a result, you have to wrap the call to build it in Batch files, something that I am trying to get away from. 4) The code seems to be buggy. For example, the copying of the build output is encapsulated in the code. I have a project called Desking.Core and a project called Core. It tries to copy both outputs into the Latest/Core folder and throws an exception because a dll already exists with the same name (Desking.Core references Core.dll) 5) BuildIt calls devenv.exe which is significantly more overhead than csc.exe. 6) If the virtual directory for a web project does not exist, it actually shows the VS prompt and makes the user accept the directories before continuing. I'm sure there is more but I just wanted to share some observations that I have painfully learned. You guys are really developing a great solution and I just wanted to say Kudos. The support is timely as well. Thanks for that. I believe I will be sticking with Nant. Evan A. Bonnett
[Nant-users] Slingshot Question
Title: Slingshot Question
All,
When slingshot generates the build file, its default target is debug.
project name=ApplicationLauncher default=Debug
But when my debug property in the the calling build file (the file that calls slingshot) is false, it still calls the debug target. Any idea on why? Here is the target that calls slingshot:
target name=build depends=getsource
mkdir dir=${build.basedir}\${basename} /
slingshot solution=ApplicationLauncher.sln format=nant output=${source.basedir}\ApplicationLauncher.build
parameters
option name=build.basedir value=${build.basedir}\${basename} /
/parameters
/slingshot
nant buildfile=${source.basedir}\ApplicationLauncher.build
properties
property name=build.dir value=${build.basedir}\${basename}\bin /
/properties
/nant
/target
Now, the csc call in the generated build file looks like this...
csc target=winexe output=${output} debug=${debug} define=${define} doc=${doc} warninglevel=${warninglevel}
The ${debug} property is not defined in the file so I assumed that it was the property that I am setting in the calling file. But, if that's the case, it should be false.
Help?
Evan A. Bonnett
[Nant-users] RE: Slingshot Question
Title: RE: Slingshot Question
Please disregard this question. Got it figured out. I have to specify the Release target in the call to nant.
Thanks anyway...
Evan A. Bonnett
-Original Message-
From: Bonnett, Evan A
Sent: Wednesday, March 31, 2004 12:28 PM
To: [EMAIL PROTECTED]
Subject: Slingshot Question
All,
When slingshot generates the build file, its default target is debug.
project name=ApplicationLauncher default=Debug
But when my debug property in the the calling build file (the file that calls slingshot) is false, it still calls the debug target. Any idea on why? Here is the target that calls slingshot:
target name=build depends=getsource
mkdir dir=${build.basedir}\${basename} /
slingshot solution=ApplicationLauncher.sln format=nant output=${source.basedir}\ApplicationLauncher.build
parameters
option name=build.basedir value=${build.basedir}\${basename} /
/parameters
/slingshot
nant buildfile=${source.basedir}\ApplicationLauncher.build
properties
property name=build.dir value=${build.basedir}\${basename}\bin /
/properties
/nant
/target
Now, the csc call in the generated build file looks like this...
csc target=winexe output=${output} debug=${debug} define=${define} doc=${doc} warninglevel=${warninglevel}
The ${debug} property is not defined in the file so I assumed that it was the property that I am setting in the calling file. But, if that's the case, it should be false.
Help?
Evan A. Bonnett
RE: [Nant-users] Slingshot Question
Title: RE: [Nant-users] Slingshot Question
Well, as I'm finding out, you can specify a target once you call the slingshot task but you have to have prior knowledge of what it generates. As stated below, it defaults to the Debug target but when you call the nant task, you can specify the Release target if the build is a release build. At least that is how I'm doing it.
As for C++ support, I seem to remember it only supporting C# and VB.NET. I wouldn't take my word for it though as I am a newbie (for now ;~)
Good luck
Evan A. Bonnett
Reynolds and Reynolds, IT
ERA Integrated Desking Development
937-485-8577
58577
-Original Message-
From: Castro, Edwin Gabriel (Firing Systems Engr.) [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 31, 2004 2:04 PM
To: [EMAIL PROTECTED]
Subject: RE: [Nant-users] Slingshot Question
Hello All,
Slingshot looks like a cool tool! Can I specify a different Target? Also, does it support VC++ projects?
--
Edwin G. Castro
Firing Systems Engineer
[EMAIL PROTECTED]
Â
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Bonnett, Evan A
Sent: Wednesday, March 31, 2004 9:28 AM
To: [EMAIL PROTECTED]
Subject: [Nant-users] Slingshot Question
All,
When slingshot generates the build file, its default target is debug.
project name=ApplicationLauncher default=Debug
But when my debug property in the the calling build file (the file that calls slingshot) is false, it still calls the debug target. Any idea on why? Here is the target that calls slingshot:
target name=build depends=getsource
   mkdir dir=${build.basedir}\${basename} /
     Â
   slingshot solution=ApplicationLauncher.sln format=nant output=${source.basedir}\ApplicationLauncher.build
      parameters
         option name=build.basedir value=${build.basedir}\${basename} /
      /parameters
   /slingshot
     Â
   nant buildfile=${source.basedir}\ApplicationLauncher.build
      properties
         property name=build.dir value=${build.basedir}\${basename}\bin /         Â
      /properties
   /nant
     Â
/target
Now, the csc call in the generated build file looks like this...
csc target=winexe output=${output} debug=${debug} define=${define} doc=${doc} warninglevel=${warninglevel} The ${debug} property is not defined in the file so I assumed that it was the property that I am setting in the calling file. But, if that's the case, it should be false. Help?
Evan A. Bonnett
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click
___
Nant-users mailing list
[EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
[Nant-users] Command Line args Help
Title: Message Sorry, sent this under a bad subject line... Does anyone have an example of a command line arg that is passed in with the call to nantand how to get it into a property? Evan A. Bonnett Reynolds and Reynolds, IT
RE: [Nant-users] Slingshot Question
Title: Message Does anyone have an example of a command line arg that is passed in with the call to nantand how to get it into a property? Evan A. Bonnett Reynolds and Reynolds, IT
RE: [Nant-users] Getting Code from VSS via NAnt
Title: Message
Cool,
thanks. I am setting the version #'s to "" globally to start with.
Then, I call an exe using the exec task. That outputs the new
version # to a txt file. Using a foreach, I set the
properties. Here is the code. Let me know what you think. I am
basing this off an example that Jarek provided. I hope I am doing
things right.
property name="version.major" value=""
/property name="version.minor" value=""
/property name="version.revision" value=""
/property name="version.build" value=""
/
.
.
.
target name="label"exec
program="${versioning.prog}" commandline="AssemblyInfo.cs"
output="${version.file}" /foreach item="Line"
in="${version.file}" delim="."
property="major.temp,minor.temp,revision.temp,build.temp"property
name="version.major" value="${major.temp}"
/property name="version.minor"
value="${minor.temp}" /property
name="version.revision" value="${revision.temp}"
/property name="version.release"
value="${build.temp}"
//foreach
.
.
.
Label
VSS files
forthevssget/target
Anyone
see any problems?
Thanks,
Evan A. Bonnett
Reynolds and Reynolds,
IT
RE: [Nant-users] Properties files
Title: RE: [Nant-users] Properties files All, Quick question... I am getting this exception when checking out code to label in VSS. I have come to the conclusion that when checking out via the vsscheckout, it will not overwrite and will fail if the files already exist. Is this accurate? So, if I have to check out the AssemblyInfo.cs file to update the version num, I should check it into a temp directory, modify it, check it in, and then delete it? Then, if I label the code for a future vssget, I should do the same in a temp dir? (e.g. checkout, modify, checkin, delete directory). Is this correct? C:\Inetpub\wwwroot\Reynolds\GenerationsSeries\DeskingPortal\default.build(95,4): Checkout failed: NAnt.Core.BuildException: C:\Inetpub\wwwroot\Reynolds\GenerationsSeries\DeskingPortal\default.build(95,4): Checkout failed --- System.Runtime.InteropServices.COMException (0x8004D841): File c:\NAntVSSTest\DeskingPortal\DeskingPort al already exists at SourceSafeTypeLib.VSSItemClass.Checkout(String Comment, String Local, Int32 iFlags) at NAnt.Contrib.Tasks.SourceSafe.CheckoutTask.ExecuteTask() --- End of inner exception stack trace --- at NAnt.Contrib.Tasks.SourceSafe.CheckoutTask.ExecuteTask() at NAnt.Core.Task.Execute() in C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp244.tmp\src\NAnt.Core\Task.cs:line 151 at NAnt.Core.Target.Execute() in C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp244.tmp\src\NAnt.Core\Target.cs:line 252 at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies) in C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp244.tm p\src\NAnt.Core\Project.cs:line 878 at NAnt.Core.Project.Execute(String targetName) in C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp244.tmp\src\NAnt.Core\Project.cs: line 848 at NAnt.Core.Tasks.CallTask.ExecuteTask() in C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp244.tmp\src\NAnt.Core\Tasks\CallTask.cs :line 110 at NAnt.Core.Task.Execute() in C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp244.tmp\src\NAnt.Core\Task.cs:line 151 at NAnt.Core.Target.Execute() in C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp244.tmp\src\NAnt.Core\Target.cs:line 252 at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies) in C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp244.tm p\src\NAnt.Core\Project.cs:line 878 at NAnt.Core.Project.Execute() in C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp244.tmp\src\NAnt.Core\Project.cs:line 835 at NAnt.Core.Project.Run() in C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp244.tmp\src\NAnt.Core\Project.cs:line 903 Total time: 1.4 seconds. Evan A. Bonnett Reynolds and Reynolds, IT
[Nant-users] VSS checkout task question
Title: Message Sorry all, I didn't change the subject on the last email. Won't happen again. Evan A. Bonnett Reynolds and Reynolds, IT All, Quick question... I am getting this exception when checking out code to label in VSS. I have come to the conclusion that when checking out via the vsscheckout, it will not overwrite and will fail if the files already exist. Is this accurate? So, if I have to check out the AssemblyInfo.cs file to update the version num, I should check it into a temp directory, modify it, check it in, and then delete it? Then, if I label the code for a future vssget, I should do the same in a temp dir? (e.g. checkout, modify, checkin, delete directory). Is this correct? C:\Inetpub\wwwroot\Reynolds\GenerationsSeries\DeskingPortal\default.build(95,4): Checkout failed: NAnt.Core.BuildException: C:\Inetpub\wwwroot\Reynolds\GenerationsSeries\DeskingPortal\default.build(95,4): Checkout failed --- System.Runtime.InteropServices.COMException (0x8004D841): File "c:\NAntVSSTest\DeskingPortal\DeskingPort al" already exists at SourceSafeTypeLib.VSSItemClass.Checkout(String Comment, String Local, Int32 iFlags) at NAnt.Contrib.Tasks.SourceSafe.CheckoutTask.ExecuteTask() --- End of inner exception stack trace --- at NAnt.Contrib.Tasks.SourceSafe.CheckoutTask.ExecuteTask() at NAnt.Core.Task.Execute() in C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp244.tmp\src\NAnt.Core\Task.cs:line 151 at NAnt.Core.Target.Execute() in C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp244.tmp\src\NAnt.Core\Target.cs:line 252 at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies) in C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp244.tm p\src\NAnt.Core\Project.cs:line 878 at NAnt.Core.Project.Execute(String targetName) in C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp244.tmp\src\NAnt.Core\Project.cs: line 848 at NAnt.Core.Tasks.CallTask.ExecuteTask() in C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp244.tmp\src\NAnt.Core\Tasks\CallTask.cs :line 110 at NAnt.Core.Task.Execute() in C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp244.tmp\src\NAnt.Core\Task.cs:line 151 at NAnt.Core.Target.Execute() in C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp244.tmp\src\NAnt.Core\Target.cs:line 252 at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies) in C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp244.tm p\src\NAnt.Core\Project.cs:line 878 at NAnt.Core.Project.Execute() in C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp244.tmp\src\NAnt.Core\Project.cs:line 835 at NAnt.Core.Project.Run() in C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\tmp244.tmp\src\NAnt.Core\Project.cs:line 903 Total time: 1.4 seconds. Evan A. Bonnett Reynolds and Reynolds, IT
[Nant-users] Test Cases in NAnt
Title: Test Cases in NAnt All, I have somewhat completed a build file for a portal app. It's pretty simple but here are the steps: Update version Label VSS Get code by label Compile Package into zip for distribution Clean target area Install (unzip) My question is regarding testing. What are some common Nunit tests that are run? I'm not familiar with testing a build. Could someone offer some help here? Thanks, Evan A. Bonnett Reynolds and Reynolds, IT
RE: [Nant-users] Getting Code from VSS via NAnt
Title: Message
Cool,
thanks. I am setting the version #'s to "" globally to start with.
Then, I call an exe using the exec task. That outputs the new
version # to a txt file. Using a foreach, I set the
properties. Here is the code. Let me know what you think. I am
basing this off an example that Jarek provided. I hope I am doing
things right.
property name="version.major" value=""
/property name="version.minor" value=""
/property name="version.revision" value=""
/property name="version.build" value=""
/
.
.
.
target name="label"exec
program="${versioning.prog}" commandline="AssemblyInfo.cs"
output="${version.file}" /foreach item="Line"
in="${version.file}" delim="."
property="major.temp,minor.temp,revision.temp,build.temp"property
name="version.major" value="${major.temp}"
/property name="version.minor"
value="${minor.temp}" /property
name="version.revision" value="${revision.temp}"
/property name="version.release"
value="${build.temp}"
//foreach
.
.
.
Label
VSS files
forthevssget/target
Anyone
see any problems?
Thanks,
Evan A. Bonnett
Reynolds and Reynolds,
IT ERA Integrated
Desking Development 937-485-8577 58577
-Original Message-From: Noel Gifford
[mailto:[EMAIL PROTECTED] Sent: Thursday, March 18, 2004
10:40 PMTo: [EMAIL PROTECTED]Subject: RE:
[Nant-users] Getting Code from VSS via NAnt
Yes,
you just use the property syntax. Of course, the property will now be
changed globally - not just in the target.
Noel
-Original
Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]On Behalf Of Bonnett, Evan ASent: Thursday, March 18, 2004 2:31
PMTo: 'Jaroslaw Kowalski';
'Morris, Jason'; [EMAIL PROTECTED]Subject: RE: [Nant-users] Getting Code
from VSS via NAnt
So, if I declare properties
in the top of the build file for use by any target, what if I want to
manipulate the property in a target? What is the syntax to set a
property value mid target if its already been declared?
Do I just use the
property??
Evan A.
Bonnett
Reynolds and Reynolds,
IT
-Original
Message-
From: Jaroslaw Kowalski [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 16,
2004 3:22 PM
To: Bonnett, Evan A; 'Morris, Jason';
[EMAIL PROTECTED] Subject: Re: [Nant-users] Getting Code
from VSS via NAnt
There's a trick that uses
foreach task. Taken from my build script:
target
name="installer" foreach item="Line"
in="version.txt" delim="."
property="sooda.major,sooda.minor,sooda.revision,sooda.build"
... do
something with the properties ...
/foreach
/target
This will read ALL lines
from "version.txt" (there's only one and that's the trick) and set sooda.*
properties appropriately.
See foreach task
documentation for more info. Hope it helps.
Jarek
- Original Message
- From: "Bonnett, Evan A"
[EMAIL PROTECTED] To: "'Morris, Jason'"
[EMAIL PROTECTED];
[EMAIL PROTECTED] Sent: Tuesday, March 16, 2004 7:45
PM
Subject: RE: [Nant-users] Getting Code
from VSS via NAnt
Great. But is
there no way to get the value from a file and set a property? If not, would that be
a good candidate for a custom task? Evan A.
Bonnett
Reynolds and Reynolds,
IT
ERA Integrated Desking
Development
937-485-8577
58577
-Original
Message-
From: Morris, Jason [mailto:[EMAIL PROTECTED]] Sent: Monday, March
15, 2004 11:04 PM
To:
[EMAIL PROTECTED] Subject: RE: [Nant-users] Getting
Code from VSS via NAntThere is a nant task
called asminfo which should be able to do what
you want. Check
out
http://nant.sourceforge.net/help/tasks/asminfo.html http://nant.sourceforge.net/help/tasks/asminfo.html
_
From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
On Behalf Of Bonnett, Evan A Sent: Monday, March
15, 2004 11:32 AM
To: 'Price, Henry';
[EMAIL PROTECTED] Subject: RE: [Nant-users] Getting
Code from VSS via NAnt
All,
What about versioning
the assembly? We use the standard Major, Minor, Build, Revision.
Is there a standard means of doing this, or one that is
common?
Thanks,
Evan A.
Bonnett
Reynolds and Reynolds,
IT
-Original
Message-
From: Price, Henry [mailto:[EMAIL PROTECTED]] Sent: Monday, March
15, 2004 11:44 AM
To: Bonnett, Evan A;
[EMAIL PROTECTED] Subject: RE: [Nant-users] Getting
Code from VSS via NAnt Yes there is, but it's
in the NAnt Contrib rather than the core (more info on NAntCon
RE: [Nant-users] Getting Code from VSS via NAnt
Title: Message Great. But is there no way to get the value from a file and set a property? If not, would that be a good candidate for a custom task? Evan A. Bonnett Reynolds and Reynolds, IT ERA Integrated Desking Development 937-485-8577 58577 -Original Message-From: Morris, Jason [mailto:[EMAIL PROTECTED] Sent: Monday, March 15, 2004 11:04 PMTo: [EMAIL PROTECTED]Subject: RE: [Nant-users] Getting Code from VSS via NAnt There is a nant task called asminfo which should be able to do what you want. Check out http://nant.sourceforge.net/help/tasks/asminfo.html From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bonnett, Evan ASent: Monday, March 15, 2004 11:32 AMTo: 'Price, Henry'; [EMAIL PROTECTED]Subject: RE: [Nant-users] Getting Code from VSS via NAnt All, What about versioning the assembly? We use the standard Major, Minor, Build, Revision. Is there a standard means of doing this, or one that is common? Thanks, Evan A. Bonnett Reynolds and Reynolds, IT -Original Message-From: Price, Henry [mailto:[EMAIL PROTECTED] Sent: Monday, March 15, 2004 11:44 AMTo: Bonnett, Evan A; [EMAIL PROTECTED]Subject: RE: [Nant-users] Getting Code from VSS via NAnt Yes there is, but it's in the NAnt Contrib rather than the core (more info on NAntContrib can be found at: http://sourceforge.net/projects/nantcontrib) http://nantcontrib.sourceforge.net/help/tasks/vssget.html Will fill you in on the vssget command, http://nantcontrib.sourceforge.net/help/tasks/ Will show you all tasks available in the NAnt Contrib (there are a load of other SourceSafe ones). As for the get task - I typically have it in a separate target (cvsUpdate seeing as we're using CVS here) which is called before the build target. As I divide each of the clean, build, deploy and test targets up into their own scripts (each containing a whole pile of their own targets), that means it goes in the build target (as you would look at it). Hope that helps :) Henry -Original Message-From: Bonnett, Evan A [mailto:[EMAIL PROTECTED] Sent: 15 March 2004 4:09PTo: [EMAIL PROTECTED]Subject: [Nant-users] Getting Code from VSS via NAnt Hi all, Is there support for VSS or do I need to call the exec task to run a batch file? Is there a better way to get the latest from VSS? Also, which target does this task really belong in? I have the following targets now... clean - Deletes all files from the bin directory and recopies the dll's from a given reference directory build - Compiles the code and outputs the resultant dll to the bin directory package - zips up all the necessary files for the web app to be copied to the destination directory install - copies the zip over to the install directory and unzips I know I need a test target but I'm building my way to that as I am new to NAnt. Is it standard practice to put the source code extraction in one of the existing targets or it's own target? Thanks, Evan A. Bonnett Reynolds and Reynolds, IT "This communication is intended solely for the addressee and is confidential and not for third party unauthorised distribution."
RE: [Nant-users] Getting Code from VSS via NAnt
Title: Message Hi, I have an executable that takes an AssemblyInfo.cs file as a command line arg and updates the version attribute. When I call it using the exec task, I see the resultant version # on the screen. In addition,I output the version # to a file. Is there any way to get that value into a property so I can use it for the label? Thanks, Evan A. Bonnett Reynolds and Reynolds, IT
RE: [Nant-users] Where are command line options documented?
Title: RE: [Nant-users] Where are command line options documented? Gary, Try this... http://danpupek.homeip.net/tools/nAnt-Help.pdf Evan A. Bonnett Reynolds and Reynolds, IT ERA Integrated Desking Development 937-485-8577 58577 -Original Message- From: Gary Feldman [mailto:[EMAIL PROTECTED]] Sent: Friday, March 12, 2004 10:43 AM To: [EMAIL PROTECTED] Subject: [Nant-users] Where are command line options documented? Where are command line options documented? The online docs at http://nant.sourceforge.net/help/fundamentals/fog80.html only discusses the --buildfile option, and not others like MailLogger. Giuseppe Greco's document at http://developer.agamura.com/technotes/building-projects-with-nant/running-nant.html discusses a couple more, but still is incomplete. Gary --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470_id=3638=click ___ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
RE: [Nant-users] Where are command line options documented?
Title: RE: [Nant-users] Where are command line options documented? I have a build file and would like to delete a directory IF it exists and then re make it. If the dir doesn't exist, nant throws an error. Is there a way to do an existence check on the directory? Evan A. Bonnett Reynolds and Reynolds, IT ERA Integrated Desking Development 937-485-8577 58577
RE: [Nant-users] Where are command line options documented?
Title: RE: [Nant-users] Where are command line options documented?
Great. I'll try that. Thanks!
Evan A. Bonnett
Reynolds and Reynolds, IT
ERA Integrated Desking Development
937-485-8577
58577
-Original Message-
From: Jaroslaw Kowalski [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 12, 2004 2:07 PM
To: Bonnett, Evan A; 'Gert Driesen'; [EMAIL PROTECTED]
Subject: Re: [Nant-users] Where are command line options documented?
If you use the nightly build (recommended):
property name=dir.name value=c:\some\path\to\delete / delete dir=${dir.name} if=${directory::exists(dir.name)} /
If you want to use the release build, you available task is the solution.
Jarek
- Original Message -
From: Bonnett, Evan A [EMAIL PROTECTED]
To: 'Gert Driesen' [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Friday, March 12, 2004 7:43 PM
Subject: RE: [Nant-users] Where are command line options documented?
I have a build file and would like to delete a directory IF it exists
and then re make it. If the dir doesn't exist, nant throws an error.
Is
there
a way to do an existence check on the directory?
Evan A. Bonnett
Reynolds and Reynolds, IT
ERA Integrated Desking Development
937-485-8577
58577
RE: [Nant-users] Does anyone have a Web App Build File Template
Title: Message Thanks a lot. I will check it out. Evan A. Bonnett Reynolds and Reynolds, IT ERA Integrated Desking Development 937-485-8577 58577 -Original Message-From: Clayton Harbour [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 10, 2004 9:19 PMTo: Bonnett, Evan ACc: NAnt-usersSubject: RE: [Nant-users] Does anyone have a Web App Build File Template Hi, I am not sure if this is "typical"but it works :-): http://cvs.sourceforge.net/viewcvs.py/*checkout*/sharpschedule/sharpschedule/build/schedule.web.xml?content-type=text%2Fplainrev=1.2 there are additional build files defined in the upper directory that define some of the properties: http://cvs.sourceforge.net/viewcvs.py/sharpschedule/sharpschedule/build/ Cheers, Clayton -Original Message-From: Bonnett, Evan A [mailto:[EMAIL PROTECTED] Sent: March 10, 2004 1:52 PMTo: [EMAIL PROTECTED]Subject: [Nant-users] Does anyone have a Web App Build File Template Does anyone have an example of a typical build file for a web app? For example: ?xml version="1.0"? project name="HelloWebWorld" default="build" basedir="." target name="build" csc target="library" output="projName.dll" / sources ???Which files go in here? All aspx, ascx, incudes, images, resx? Am I missing anything or do I have too much? /sources references ???All referenced dll's here? What form is the reference path (e.g. c:\WINDOWS\... Or just System.dll)? /references /target /project How would I create this with Slingshot? I'm trying, just bare with me... Thanks all, Evan A. Bonnett Reynolds and Reynolds, IT ERA Integrated Desking Development 937-485-8577 58577
RE: [Nant-users] Unhandled Exception when using SLingShot
Title: Message Can you point me to documentation or a how to? Thanks, Evan A. Bonnett Reynolds and Reynolds, IT ERA Integrated Desking Development 937-485-8577 58577 -Original Message-From: Gert Driesen [mailto:[EMAIL PROTECTED] Sent: Thursday, March 11, 2004 4:35 AMTo: Bonnett, Evan A; NanT ForumSubject: Re: [Nant-users] Unhandled Exception when using SLingShot The Slingshot command line utility and task are very much deprecated. I suggest using the solution task instead. Gert - Original Message - From: Bonnett, Evan A To: NanT Forum Sent: Wednesday, March 10, 2004 8:40 PM Subject: [Nant-users] Unhandled Exception when using SLingShot Can anyone tell me why I'm getting the following exception when it hits my references? I am using the following command line: C:\GenerationsSeries\EID\2.0\WEBSUPPORTslingshot -nant build.basedir=c:\Intepub\wwwroot\Reynolds\GenerationsSeries\DeskingPortal -maphttp://localhost/ C:\Inetpub\wwwroot\ includes name="C:\Inetpub\wwwroot\Reynolds\GenerationsSeries\DeskingPortal\UserControls\VinDecodeCriteria.ascx.cs" / /sources referencesUnhandled Exception: System.NotSupportedException: The given path's format is not supported. at System.Security.Util.StringExpressionSet.CanonicalizePath(String path, Boolean needFullPath) at System.Security.Util.StringExpressionSet.AddExpressions(String[] str, Boolean checkForDuplicates, Boolean needFullPath) at System.Security.Permissions.FileIOPermission.AddPathList(FileIOPermissionAccess access, String[] pathList, Boolean checkForDuplicates, Boolean needFullPath) at System.Security.Permissions.FileIOPermission..ctor(FileIOPermissionAccess access, String[] pathList, Boolean checkForDuplicates,Boolean needFullPath) at System.IO.Path.GetFullPath(String path) at SLiNgshoT.Core.Driver.WriteSolution(SolutionWriter writer, TextWriter textWriter, String sln, Hashtable parameters, Hashtable uriMap) at SLiNgshoT_Console.Main(String[] args) C:\GenerationsSeries\EID\2.0\WEBSUPPORT Thanks, Evan A. Bonnett Reynolds and Reynolds, IT ERA Integrated Desking Development 937-485-8577 58577 -Original Message-From: Morris, Jason [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 09, 2004 3:33 PMTo: NanT ForumSubject: FW: [Nant-users] Deployment Issue looks like the first send didn't go through From: Morris, Jason Sent: Monday, March 08, 2004 7:29 PMTo: NanT ForumSubject: RE: [Nant-users] Deployment Issue I think this is applicable to this forum since we are talking about using nAnt...if I am mistaken, please letme know and Steve and I will take this offline. I have defined several nAnt target, one for each of the environments that my application gets installed to. The environments are local development integration pre-production production On my local development box, my "local" target preps the machine with all the latest code (does a CVS update), copies any 3rd party dlls that are needed, constructs virtual directories and anything else that is needed. Then I open my *.sln and do my coding. When I want to build, then I use VS.NET to dothe build as I am working. If I add any references, create a new project, etc, then I have to go into my build script and make the necessary modification. I don't use the solution task since I started my script before it was available and I feel the extra control of the build process is worth the extra maintenance. Now, when I am ready to move my code inthe "Development" environment, I executemy "development" target. This target does all the things to build, test,and copy the code out tothe development server. As you probably guessed, I execute similar targets for my integration, pre-prod and production environments, however with these I don't rebuild or retest my code, I just copy the files out to these servers. My development build actually creates a versioned copy of my code that I just reference in these scripts. So, on my build server, I have a directory structure like ./MyApp/MyApp-1.0.0.1/... ./MyApp/MyApp-1.0.0.2/... ./MyApp/MyApp-1.0.0.3/... etc I am greatly simplifying my build process, but I hope you get the idea. Except in the local deve
[Nant-users] Does anyone have a Web App Build File Template
Title: Does anyone have a Web App Build File Template Does anyone have an example of a typical build file for a web app? For example: ?xml version=1.0? project name=HelloWebWorld default=build basedir=. target name=build csc target=library output=projName.dll / sources ???Which files go in here? All aspx, ascx, incudes, images, resx? Am I missing anything or do I havetoo much? /sources references ???All referenced dll's here? What form is the reference path (e.g. c:\WINDOWS\... Or just System.dll)? /references /target /project How would I create this with Slingshot? I'm trying, just bare with me... Thanks all, Evan A. Bonnett Reynolds and Reynolds, IT ERA Integrated Desking Development 937-485-8577 58577
[Nant-users] General Nant Question
Title: General Nant Question All, I'm checking Nant out and am considering employing it for my application. First, a little bit about my app... The main app is a WinForms app. There are 2 web services and a portal app as well. All in all, there are 7 solutions containing somewhere around 20 projects or so. The deployment consists of the following tasks: 1)shut down IIS and uninstall and reinstall asp.net 2)get all files from VSS into a staging directory 3)label all projects in VSS 4)compile all projects and send an email a) in compile, if it's a web app or svc, copy all dlls and necessary files to virt dir b) if forms app, copy dll's into the reference dir for other projects to ref 5)clean up Now, obviously, this is an over-simplification of the whole process but you get the jist. My question is this: I have heard that maintenance of build files can be an unwieldy task. Is this true? How do you handle it? Given the information I have set forth above, does it sound like I can gain significant benefit from Nant? Thanks, Evan A. Bonnett Reynolds and Reynolds, IT ERA Integrated Desking Development 937-485-8577 58577
[Nant-users] NAntContrib Build Problem...
Title: Message I am getting some errors when trying to build NAntContrib.Is this a known issue? I have nant set up in C:\NAnt I have NAntContrib in C:\NAntContrib I followed the instructions in the readme.txt file but got this... (only included the failure. There were many successful builds but this one failed). [csc] Compiling 5 files to C:\NAntContrib/build/nantcontrib-0.84-debug/bin/NAnt.Contrib.Tests.dll. C:\NAntContrib\tests\Util\SqlStatementListTests.cs(27,7): error CS0246: The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?) C:\NAntContrib\tests\Alltests.cs(28,7): error CS0246: The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?) C:\NAntContrib\tests\GetTaskTests.cs(26,7): error CS0246: The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?) C:\NAntContrib\tests\GetTaskTests.cs(205,10): error CS0246: The type or namespace name 'SetUp' could not be found (are youmissing a using directive or an assembly reference?) C:\NAntContrib\tests\GetTaskTests.cs(317,10): error CS0246: The type or namespace name 'TearDown' could not be found (are you missing a using directive or an assembly reference?) C:\NAntContrib\tests\GetTaskTests.cs(337,10): error CS0246: The type or namespace name 'Test' could not be found (are you missing a using directive or an assembly reference?) C:\NAntContrib\tests\GetTaskTests.cs(352,10): error CS0246: The type or namespace name 'Test' could not be found (are you missing a using directive or an assembly reference?) C:\NAntContrib\tests\GetTaskTests.cs(367,10): error CS0246: The type or namespace name 'Test' could not be found (are you missing a using directive or an assembly reference?) C:\NAntContrib\tests\GetTaskTests.cs(386,10): error CS0246: The type or namespace name 'Test' could not be found (are you missing a using directive or an assembly reference?) C:\NAntContrib\tests\GetTaskTests.cs(401,10): error CS0246: The type or namespace name 'Test' could not be found (are you missing a using directive or an assembly reference?) C:\NAntContrib\tests\GetTaskTests.cs(420,10): error CS0246: The type or namespace name 'Test' could not be found (are you missing a using directive or an assembly reference?) C:\NAntContrib\tests\GetTaskTests.cs(439,10): error CS0246: The type or namespace name 'Test' could not be found (are you missing a using directive or an assembly reference?) C:\NAntContrib\tests\GetTaskTests.cs(452,10): error CS0246: The type or namespace name 'Test' could not be found (are you missing a using directive or an assembly reference?) C:\NAntContrib\tests\GetTaskTests.cs(468,10): error CS0246: The type or namespace name 'Test' could not be found (are you missing a using directive or an assembly reference?) C:\NAntContrib\tests\GetTaskTests.cs(479,10): error CS0246: The type or namespace name 'Test' could not be found (are you missing a using directive or an assembly reference?) C:\NAntContrib\tests\GetTaskTests.cs(496,10): error CS0246: The type or namespace name 'Test' could not be found (are you missing a using directive or an assembly reference?) C:\NAntContrib\tests\GetTaskTests.cs(513,10): error CS0246: The type or namespace name 'Test' could not be found (are you missing a using directive or an assembly reference?) C:\NAntContrib\tests\GetTaskTests.cs(536,10): error CS0246: The type or namespace name 'Test' could not be found (are you missing a using directive or an assembly reference?) C:\NAntContrib\tests\GetTaskTests.cs(569,10): error CS0246: The type or namespace name 'Test' could not be found (are you missing a using directive or an assembly reference?) C:\NAntContrib\tests\GetTaskTests.cs(608,10): error CS0246: The type or namespace name 'Test' could not be found (are you missing a using directive or an assembly reference?) C:\NAntContrib\tests\GetTaskTests.cs(181,6): error CS0246: The type or namespace name 'TestFixture' could not be found (areyou missing a using directive or an assembly reference?) C:\NAntContrib\tests\Util\SqlStatementListTests.cs(38,5): error CS0246: The type or namespace name 'TestFixture' could notbe found (are you missing a using directive or an assembly reference?) BUILD FAILED C:\NAntContrib\NAntContrib.build(156,10):External Program Failed: C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\csc.exe (return code was 1) Total time: 9.1 seconds. Evan A. Bonnett Reynolds and Reynolds, IT ERA Integrated Desking Development 937-485-8577 58577 -Original Message-From: Mats Cederholm [mailto:[EMAIL PROTECTED] Sent: Friday, March 05, 2004 9:30 AMTo: NAnt-usersSubject: [Nant-users] MSI Hi, quite new to nant but I'm starting to get the hang of it and I'm very pleased with everything so far. One thing I have a problem with is
RE: [Nant-users] Can't build Nant
Title: Message Disregard this all. Sorry, don't know how this got thru. Changing the attribute worked. Evan A. Bonnett Reynolds and Reynolds, IT ERA Integrated Desking Development 937-485-8577 58577 -Original Message-From: Bonnett, Evan A Sent: Thursday, February 26, 2004 4:23 PMTo: [EMAIL PROTECTED]Subject: RE: [Nant-users] Can't build Nant Getting the following error... Anyone know why? self-test: [attrib] Setting file attributes for 1 files to Normal. [xmlpoke] Found '1' nodes matching XPath _expression_ '//configuration/nant/frameworks/[EMAIL PROTECTED]'win32']/@default'. [echo] testing with config 'C:\Nant\build\net-1.0.win32\nant-0.84-debug\bin\nant.tests.config' [nant] C:\Nant\tests\NAnt.Console\NAnt.Console.build test Buildfile: file:///C:/Nant/tests/NAnt.Console/NAnt.Console.build Target(s) specified: test build: test: [nunit2] Tests run: 9, Failures: 1, Not run: 0, Time: 3.8696592 seconds Failures: 1) Tests.NAnt.Console.NAntTest.Test_ShowHelp : expected:2004 but was:2003 at Tests.NAnt.Console.NAntTest.Test_ShowHelp() in C:\Nant\tests\NAnt.Console\NAntTest.cs:line 211 BUILD FAILED Tests Failed Total time: 4.8 seconds. BUILD FAILED Nested build failed. Refer to build log for exact reason. Total time: 5.4 seconds. Evan A. Bonnett Reynolds and Reynolds, IT ERA Integrated Desking Development 937-485-8577 58577 -Original Message- From: Jaroslaw Kowalski [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 26, 2004 2:21 PM To: Steven Hawkes; [EMAIL PROTECTED] Subject: Re: [Nant-users] Test Build of NANT Can you please download the latest nightly build? It should detect the current framework properly. If you prefer to stick with the release version (0.84), use "-k" parameter on the command line or modify nant.exe.config to specify a default framework. If you need more assistance, let us know. Jarek - Original Message - From: "Steven Hawkes" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, February 26, 2004 8:14 PM Subject: [Nant-users] Test Build of NANT Tried to do a test build of ANT and got the following error ..Framework\v1.0.3705\csc.exe failed to start This is correct as the actual directory where cdc.exe is located is ...Framework\v1.1.4322 Can anyone tell me why nant is choosing a different dir. Is it enough to copy csc.exe to the required location. I am a bit worried I will run into other problems later. Kind regards Steve --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356alloc_id=3438op=click ___ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
RE: [Nant-users] Can't build Nant
Title: RE: [Nant-users] Can't build Nant Getting the following error... Anyone know why? self-test: [attrib] Setting file attributes for 1 files to Normal. [xmlpoke] Found '1' nodes matching XPath _expression_ '//configuration/nant/frameworks/[EMAIL PROTECTED]'win32']/@default'. [echo] testing with config 'C:\Nant\build\net-1.0.win32\nant-0.84-debug\bin\nant.tests.config' [nant] C:\Nant\tests\NAnt.Console\NAnt.Console.build test Buildfile: file:///C:/Nant/tests/NAnt.Console/NAnt.Console.build Target(s) specified: test build: test: [nunit2] Tests run: 9, Failures: 1, Not run: 0, Time: 3.8696592 seconds Failures: 1) Tests.NAnt.Console.NAntTest.Test_ShowHelp : expected:2004 but was:2003 at Tests.NAnt.Console.NAntTest.Test_ShowHelp() in C:\Nant\tests\NAnt.Console\NAntTest.cs:line 211 BUILD FAILED Tests Failed Total time: 4.8 seconds. BUILD FAILED Nested build failed. Refer to build log for exact reason. Total time: 5.4 seconds. Evan A. Bonnett Reynolds and Reynolds, IT ERA Integrated Desking Development 937-485-8577 58577 -Original Message- From: Jaroslaw Kowalski [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 26, 2004 2:21 PM To: Steven Hawkes; [EMAIL PROTECTED] Subject: Re: [Nant-users] Test Build of NANT Can you please download the latest nightly build? It should detect the current framework properly. If you prefer to stick with the release version (0.84), use -k parameter on the command line or modify nant.exe.config to specify a default framework. If you need more assistance, let us know. Jarek - Original Message - From: Steven Hawkes [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, February 26, 2004 8:14 PM Subject: [Nant-users] Test Build of NANT Tried to do a test build of ANT and got the following error ..Framework\v1.0.3705\csc.exe failed to start This is correct as the actual directory where cdc.exe is located is ...Framework\v1.1.4322 Can anyone tell me why nant is choosing a different dir. Is it enough to copy csc.exe to the required location. I am a bit worried I will run into other problems later. Kind regards Steve --- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356_id=3438=click ___ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
RE: [Nant-users] bug in Element.cs?
Title: RE: [Nant-users] bug in Element.cs?
Hi all,
I'm new to Nant and don't know a thing about it. Never used Ant either.
I have a build process that uses DOS batch files. It's UGLY and very spaghetti-like.
I would like to look into using Nant but cannot find documentation that clearly tells me exactly how to use it.
Can someone provide me a link to tutorials or how-to's for dummies ;~)
Thanks,
Evan A. Bonnett
Reynolds Reynolds, IT
-Original Message-
From: Gert Driesen [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 10, 2003 5:14 PM
To: Ben Lowery; [EMAIL PROTECTED]
Subject: Re: [Nant-users] bug in Element.cs?
Ben,
This issue has now been fixed in cvs.
Thanks for reporting this and tracking it down !!!
Gert
- Original Message -
From: Ben Lowery [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, December 10, 2003 9:37 PM
Subject: [Nant-users] bug in Element.cs?
hi there,
I'm trying to build a task that includes a [BuildElementCollection]
property
that returns a null ref on first access. ie:
[TaskName(foo)]
class Foo {
MyCollection col = null;
[BuildElementCollection(bits, bit)]
public property MyBits {
get { return col; }
set { col = value; }
}
}
I think Element.cs has a bug on line 868. It's tries to set the
property value onto the AttributeConfigurator instead of onto the
element:
// if value of property is null, create new instance of collection
object collection = propertyInfo.GetValue(Element,
BindingFlags.Default,
null,
null,
CultureInfo.InvariantCulture);
if (collection == null) {
if (!propertyInfo.CanWrite) {
throw new BuildException(string.Format(CultureInfo.InvariantCulture,
BuildElementArrayAttribute cannot be applied to read-only
property with +
uninitialized collection-based value '{0}' element for {1}
... /.,
buildElementArrayAttribute.Name, Name),
Location);
}
object instance = Activator.CreateInstance(propertyInfo.PropertyType,
BindingFlags.Public | BindingFlags.Instance,
null,
null,
CultureInfo.InvariantCulture);
// borked?
propertyInfo.SetValue(this,
instance,
BindingFlags.Default,
null,
null,
CultureInfo.InvariantCulture);
}
I think that last line should be:
propertyInfo.SetValue(this.Element,
instance,
BindingFlags.Default,
null,
null,
CultureInfo.InvariantCulture);
Thanks,
--b
---
This SF.net email is sponsored by: SF.net Giveback Program. Does
SourceForge.net help you be more productive? Does it help you create
better code? SHARE THE LOVE, and help us help YOU! Click Here:
http://sourceforge.net/donate/
___
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users
---
This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___
Nant-users mailing list
[EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
[Nant-users] How-To for NAnt...
Title: Message
Sorry,
here is a proper subject line.
Thanks,
Evan A.
Bonnett
Reynolds Reynolds, IT
Hi all,
I'm new to Nant and don't know a thing about it. Never
used Ant either.
I have a build process that uses DOS batch files. It's
UGLY and very spaghetti-like.
I would like to look into using Nant but cannot find
documentation that clearly tells me exactly how to use it.
Can someone provide me a link to tutorials or how-to's for
dummies ;~)
Thanks, Evan A. Bonnett Reynolds Reynolds,
IT
-Original Message- From: Gert
Driesen [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, December 10, 2003 5:14 PM
To: Ben Lowery; [EMAIL PROTECTED]
Subject: Re: [Nant-users] bug in Element.cs?
Ben,
This issue has now been fixed in cvs.
Thanks for reporting this and tracking it down !!!
Gert
- Original Message - From:
"Ben Lowery" [EMAIL PROTECTED] To:
[EMAIL PROTECTED] Sent:
Wednesday, December 10, 2003 9:37 PM Subject:
[Nant-users] bug in Element.cs?
hi there, I'm trying to build a task that includes a
[BuildElementCollection] property that returns a null ref on first access. ie:
[TaskName("foo")]
class Foo {
MyCollection col = null; [BuildElementCollection("bits", "bit")]
public property MyBits { get { return col; } set { col = value; } } } I think Element.cs has a bug on line
868. It's tries to set the property value
onto the AttributeConfigurator instead of onto the element:
// if value of property is null, create new instance of collection
object collection =
propertyInfo.GetValue(Element,
BindingFlags.Default, null,
null, CultureInfo.InvariantCulture); if (collection == null) {
if (!propertyInfo.CanWrite) { throw new
BuildException(string.Format(CultureInfo.InvariantCulture, "BuildElementArrayAttribute
cannot be applied to read-only property with"
+ "
uninitialized collection-based value '{0}' element for {1}
... /.",
buildElementArrayAttribute.Name, Name), Location); } object
instance = Activator.CreateInstance(propertyInfo.PropertyType,
BindingFlags.Public |
BindingFlags.Instance,
null, null,
CultureInfo.InvariantCulture); // borked?
propertyInfo.SetValue(this, instance, BindingFlags.Default, null, null, CultureInfo.InvariantCulture);
} I think that last line should be:
propertyInfo.SetValue(this.Element, instance, BindingFlags.Default, null, null, CultureInfo.InvariantCulture);
Thanks, --b
--- This SF.net email is sponsored by: SF.net Giveback Program. Does
SourceForge.net help you be more
productive? Does it help you create better
code? SHARE THE LOVE, and help us help YOU! Click Here:
http://sourceforge.net/donate/
___
Nant-users mailing list
[EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it help you
create better code? SHARE THE LOVE, and help us help YOU! Click
Here: http://sourceforge.net/donate/
___
Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
[Nant-users] Nant Help for a Newbie?
Title: Nant Help for a Newbie?
Looks like people aren't to hot to help a new guy? Posted a couple messages requesting help but have received no answers. I read through some documentation but it wasn't intuitive enough to teach me how to use Nant. I'm very interested in learning this tool but does anyone have a how-to? Step by step? Something? A url would be great.
Thanks in advance
Evan A. Bonnett
-Original Message-
From: Thomas Marshall [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 11, 2003 2:38 PM
To: Michael Dang; [EMAIL PROTECTED]
Subject: Re: [Nant-users] license tag help
I updated the license task to take out the path as
recommended, but it does not make any difference.
When I run the build the FlexGridBuildTest.exe.license
file is created, but it looks like it is not getting
included as a reference (i.e. I don't get any XXX
References read from FlexGridBuildTest.exe.license
messages). Below is the current build file, please
let me know if there are any other ideas to get this
working:
?xml version=1.0?
project name=FlexGridBuildTest default=build
descriptionTest building a project with a flex grid/description
property name=flex.debug value=true/
property name=flex.lib.dir value=C:\Program Files\ComponentOne Studio.NET\bin/
property name=flex.out
value=FlexGridBuildTest\bin\debug/
property name=flex.src
value=FlexGridBuildTest/
target name=init description=create a directory
for the files, and get the util files
!-- Create an output directory --
mkdir dir=${flex.out}/
!-- Copy DLLs from the lib directory --
copy todir=${flex.out}
fileset basedir=${flex.lib.dir}
includes name=C1.Win.C1FlexGrid.dll/
/fileset
/copy
/target
target name=clean description=remove all
generated files
delete dir=${flex.out} failonerror=false/
/target
target name=build depends=init
description=compile the code
license input=${flex.src}\licenses.licx output=${flex.out}\FlexGridBuildTest.exe.license
licensetarget=FlexGridBuildTest.exe
assemblies
includes
name=${flex.out}\C1.Win.C1FlexGrid.dll/
/assemblies
/license
csc target=winexe output=${flex.out}\FlexGridBuildTest.exe
debug=${flex.debug}
references
includes
name=${flex.out}\C1.Win.C1FlexGrid.dll/
/references
resources
includes name=${flex.src}\*.resx/
includes name=${flex.out}\*.license/
/resources
sources
includes name=${flex.src}\*.cs/
/sources
/csc
/target
/project
__
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/
---
This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ ___
Nant-users mailing list
[EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
RE: [Nant-users] Nant Help for a Newbie?
Title: RE: [Nant-users] Nant Help for a Newbie? Thanks a million. I really appreciate it. My batch files for build and deployment are spaghetti. Evan A. Bonnett -Original Message- From: Jaroslaw Kowalski [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 11, 2003 3:21 PM To: Bonnett, Evan A; [EMAIL PROTECTED] Subject: Re: [Nant-users] Nant Help for a Newbie? 1. http://nant.sourceforge.net/help/introduction/fog41.html This contains instructions for downloading NAnt. 2. http://nant.sourceforge.net/help/fundamentals/index.html This document explains main concepts (tasks, targets, properties) 3. After downloading, take a look at files in examples directory. You may want to extend them to your needs. 4. You may want to look at NAnt WIKI: http://nant.sourceforge.net/wiki/ If you have some specific questions - post them to the nant-users list. Jarek - Original Message - From: Bonnett, Evan A [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, December 11, 2003 8:44 PM Subject: [Nant-users] Nant Help for a Newbie? Looks like people aren't to hot to help a new guy? Posted a couple messages requesting help but have received no answers. I read through some documentation but it wasn't intuitive enough to teach me how to use Nant. I'm very interested in learning this tool but does anyone have a how-to? Step by step? Something? A url would be great. Thanks in advance Evan A. Bonnett
[Nant-users] (no subject)
I'm trying to build nant but this project is failing. Can anyone lend a hand here? Thanks, [nant] tests/NAnt.VisualCpp/NAnt.VisualCpp.build test Buildfile: file:///C:/nant/tests/NAnt.VisualCpp/NAnt.VisualCpp.build build: test: [nunit2] Tests run: 8, Failures: 8, Not run: 0, Time: 2.3905944 seconds Failures: 1) Tests.NAnt.VisualCpp.Tasks.ClTaskTest_HelloWorld.Test_HelloWorldC ompile : Error Executing Project at Tests.NAnt.Core.BuildTestBase.ExecuteProject(Project p) in C:\ nant\tests\NAnt.Core\BuildTestBase.cs:line 96 at Tests.NAnt.Core.BuildTestBase.RunBuild(String xml) in C:\nant\ tests\NAnt.Core\BuildTestBase.cs:line 80 at Tests.NAnt.VisualCpp.Tasks.ClTaskTest_HelloWorld.Test_HelloWor ldCompile() in C:\nant\tests\NAnt.VisualCpp\Tasks\ClTaskTest.cs:line 64 2) Tests.NAnt.VisualCpp.Tasks.ClTaskTest_CompileOnDemand.Test_BuildA ll : Error Executing Project at Tests.NAnt.Core.BuildTestBase.ExecuteProject(Project p) in C:\ nant\tests\NAnt.Core\BuildTestBase.cs:line 96 at Tests.NAnt.Core.BuildTestBase.RunBuild(String xml) in C:\nant\ tests\NAnt.Core\BuildTestBase.cs:line 80 at Tests.NAnt.VisualCpp.Tasks.ClTaskTest_CompileOnDemand.Test_Bui ldAll() in C:\nant\tests\NAnt.VisualCpp\Tasks\ClTaskTest.cs:line 139 3) Tests.NAnt.VisualCpp.Tasks.ClTaskTest_CompileOnDemand.Test_BuildN othingChanged : Error Executing Project at Tests.NAnt.Core.BuildTestBase.ExecuteProject(Project p) in C:\ nant\tests\NAnt.Core\BuildTestBase.cs:line 96 at Tests.NAnt.Core.BuildTestBase.RunBuild(String xml) in C:\nant\ tests\NAnt.Core\BuildTestBase.cs:line 80 at Tests.NAnt.VisualCpp.Tasks.ClTaskTest_CompileOnDemand.Test_Bui ldNothingChanged() in C:\nant\tests\NAnt.VisualCpp\Tasks\ClTaskTest.cs:line 151 4) Tests.NAnt.VisualCpp.Tasks.ClTaskTest_CompileOnDemand.Test_BuildS ourceChanged : Error Executing Project at Tests.NAnt.Core.BuildTestBase.ExecuteProject(Project p) in C:\ nant\tests\NAnt.Core\BuildTestBase.cs:line 96 at Tests.NAnt.Core.BuildTestBase.RunBuild(String xml) in C:\nant\ tests\NAnt.Core\BuildTestBase.cs:line 80 at Tests.NAnt.VisualCpp.Tasks.ClTaskTest_CompileOnDemand.Test_Bui ldAll() in C:\nant\tests\NAnt.VisualCpp\Tasks\ClTaskTest.cs:line 139 at Tests.NAnt.VisualCpp.Tasks.ClTaskTest_CompileOnDemand.Test_Bui ldSourceChanged() in C:\nant\tests\NAnt.VisualCpp\Tasks\ClTaskTest.cs:line 159 5) Tests.NAnt.VisualCpp.Tasks.LinkTaskTest_HelloWorld.Test_HelloWorl d : Error Executing Project at Tests.NAnt.Core.BuildTestBase.ExecuteProject(Project p) in C:\ nant\tests\NAnt.Core\BuildTestBase.cs:line 96 at Tests.NAnt.Core.BuildTestBase.RunBuild(String xml) in C:\nant\ tests\NAnt.Core\BuildTestBase.cs:line 80 at Tests.NAnt.VisualCpp.Tasks.LinkTaskTest_HelloWorld.Test_HelloW orld() in C:\nant\tests\NAnt.VisualCpp\Tasks\LinkTaskTest.cs:line 73 6) Tests.NAnt.VisualCpp.Tasks.LinkTaskTest_CompileOnDemand.Test_Buil dAll : Error Executing Project at Tests.NAnt.Core.BuildTestBase.ExecuteProject(Project p) in C:\ nant\tests\NAnt.Core\BuildTestBase.cs:line 96 at Tests.NAnt.Core.BuildTestBase.RunBuild(String xml) in C:\nant\ tests\NAnt.Core\BuildTestBase.cs:line 80 at Tests.NAnt.VisualCpp.Tasks.LinkTaskTest_CompileOnDemand.Test_B uildAll() in C:\nant\tests\NAnt.VisualCpp\Tasks\LinkTaskTest.cs:line 171 7) Tests.NAnt.VisualCpp.Tasks.LinkTaskTest_CompileOnDemand.Test_Buil dNothingChanged : Error Executing Project at Tests.NAnt.Core.BuildTestBase.ExecuteProject(Project p) in C:\ nant\tests\NAnt.Core\BuildTestBase.cs:line 96 at Tests.NAnt.Core.BuildTestBase.RunBuild(String xml) in C:\nant\ tests\NAnt.Core\BuildTestBase.cs:line 80 at Tests.NAnt.VisualCpp.Tasks.LinkTaskTest_CompileOnDemand.Test_B uildNothingChanged() in C:\nant\tests\NAnt.VisualCpp\Tasks\LinkTaskTest.cs:line 182 8) Tests.NAnt.VisualCpp.Tasks.LinkTaskTest_CompileOnDemand.Test_Buil dSourceChanged : Error Executing Project at Tests.NAnt.Core.BuildTestBase.ExecuteProject(Project p) in C:\ nant\tests\NAnt.Core\BuildTestBase.cs:line 96 at Tests.NAnt.Core.BuildTestBase.RunBuild(String xml) in C:\nant\ tests\NAnt.Core\BuildTestBase.cs:line 80 at Tests.NAnt.VisualCpp.Tasks.LinkTaskTest_CompileOnDemand.Test_B uildAll() in C:\nant\tests\NAnt.VisualCpp\Tasks\LinkTaskTest.cs:line 171 at Tests.NAnt.VisualCpp.Tasks.LinkTaskTest_CompileOnDemand.Test_B uildSourceChanged() in C:\nant\tests\NAnt.VisualCpp\Tasks\LinkTaskTest.cs:line 1 90 Total time: 2 seconds. BUILD FAILED Tests Failed Total time: 24 seconds. BUILD FAILED Nested build failed. Refer to build log for exact reason. Total time: 40 seconds. BUILD FAILED C:\nant\NAnt.build(120,10): External Program Failed: C:\nant/build/nant-0.8.3.50105-debug/bin/NAnt.exe (ret urn code was 1) C:\nant Thanks, Evan A. Bonnett Reynolds Reynolds, IT ERA Integrated Desking Development 937-485-8577
