Hi,
did anyone tried to compile vcxproj projects?
I just came to do quick tests for 0.91 on our environment and vcxproj
failed. I'm using solution task.
Martin
--
All the data continuously generated in your IT
and pretty
fast! Hard to say that for longtime svn supporter. J
mailto:martin_ali...@gordic.cz Ing. Martin Aliger
http://www.gordic.cz/ Popis: Popis:
C:\Users\maliger\Documents\podpis\a_soubory\image001.gif
GORDIC spol. s r.o. Erbenova 4, 586 01 JIHLAVA
TEL: 567 309 136, 567 303 601
control over the build process.
Hopefully they will not change API again in 4.5...
Martin
-Original Message-
From: Martin Aliger [mailto:martin_ali...@gordic.cz]
Sent: Monday, December 05, 2011 12:53 PM
To: nant-developers@lists.sourceforge.net
Subject: [nant-dev] vcxproj in 0.91
Hi
).
Perhaps something like filterchains copy and move tasks have? Or even
something pretty basic can help (e.g. setting verbosity level for each task
individually).
Regards,
Martin Aliger
--
The demand for IT networking
(SolutionBase solution, String
projectPath, XmlElement xmlDefinition, SolutionTask solutionTask,
TempFileCollection tfc, GacCache gacCache, ReferencesResolver refResolver,
DirectoryInfo outputDir)
...
ToolsVersion should be more accurate as well. I'd need to test it yet,
though.
Martin Aliger
in
which assemblies are loaded?
The registration is done in PluginScanner class from Core. All loaded types
should be send into that (via TypeFactory).
Btw: I noticed, the solution providers from MSBuild assembly got VSNet
namespace. Maybe it should be changed, for clarity.
Martin Aliger
_msproj.GetEvaluatedProperty(OutputPath);
}
}
Solutions without explicitlly set OutputPath failed. (all mine test cases
got OutputPath set).
Martin
-Original Message-
From: Ryan Boggs [mailto:rmbo...@gmail.com]
Sent: Thursday, June 16, 2011 3:37 PM
To: Martin Aliger
Cc: Dominik Guder
I do not see problem _targeting_ net-4.0-client Framework. No real need to
be hosted in that, imho.
Martin
-Original Message-
From: Ryan Boggs [mailto:rmbo...@gmail.com]
Sent: Wednesday, May 18, 2011 9:52 PM
To: Martin Aliger
Cc: nant-developers@lists.sourceforge.net
Subject: Re: [nant
I got same need and implemented that. But it never made its way to trunk
(posted atleast twice).
I'll repost all mine changes today or tommorow. There are known problems
(wpf, silverlight), but most of 4.0 solution stuff works well.
Martin Aliger
-Original Message-
From: Dominik Guder
Maybe you want to ask in ccnet-devel list? I believe alot people her eis
using ccnet, but development questions should be asked in thein forums.
Martin Aliger
_
From: Michael Craig [mailto:mcrai...@yahoo.com]
Sent: Friday, July 02, 2010 1:35 AM
To: nant-developers
:
static Encoding ConsoleEncoding {
get {
#if NET_2_0
return System.Console.OutputEncoding;
#else
return Encoding.Default;
#endif
}
}
Ing. Martin Aliger
martin_ali...@gordic.cz
-Original Message-
From: Ryan Boggs
to some of newer (2005,2008,2010) ?
Ing. Martin Aliger
martin_ali...@gordic.cz
-Original Message-
From: Ryan Boggs [mailto:rmbo...@gmail.com]
Sent: Sunday, May 30, 2010 4:03 AM
To: mono-l...@lists.ximian.com; nant-us...@lists.sourceforge.net;
nant-developers@lists.sourceforge.net; nant
Same with me. Target 1.0/1.1 is important!
M.
-Original Message-
From: Gert Driesen [mailto:gert.drie...@telenet.be]
Sent: Friday, February 26, 2010 7:36 AM
To: 'Charles Chan'; nant-developers@lists.sourceforge.net
Subject: Re: [nant-dev] Drop support for .NET-1.x?
Hey Charles,
I
I'd love to see 1.0 out soon. Not sure, what 'soon' can be though :)
VS solutions 2005 and 2008 should be supported (via MSBuild). I wrote that,
and using it daily :) VS2010 is comming soon as well (c++ project revamped
to msbuild)
M.
Roadmap
===
0.87 - bug fix only to stabilize the
And since our competetive product MSBuild do not work on 1.0/1.1 platform,
there could be some use of that.
For, me personally, same as Ryan apply.
Ing. Martin Aliger
martin_ali...@gordic.cz
-Original Message-
From: Ryan Boggs [mailto:rmboggs.obsd.po...@gmail.com]
Looking
is not the best message you
should get. I'll look on this one.
Ing. Martin Aliger
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
SourceForge.net
Sent: Sunday, March 16, 2008 12:45 PM
To: [EMAIL PROTECTED]
Subject: [nant-dev] [ nant-Bugs-1915375
NAnt attribute also makes non-fatal error from fatal ones.
Ing. Martin Aliger
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chris
Lambrou
Sent: Wednesday, November 14, 2007 12:46 PM
To: nant-developers@lists.sourceforge.net
Subject: Re
Hello,
as far as I know, it was not :( The only way to control it is global NAnt
switch (verbose/normal/quiet) but no control on task level.
Ing. Martin mailto:[EMAIL PROTECTED] Aliger
http://www.gordic.cz/ http://www.gordic.cz/ GORDIC spol. s r.o.
GORDIC spol. s.
target name=build
property name=filepath value=c:\mallow.exe/
echo message=${filepath}/
if test=${file::exists('${filepath}')}
echo message=File Exists/
/if
if test=${not
: Ryan Parlee [mailto:[EMAIL PROTECTED]
Sent: Friday, February 16, 2007 6:46 AM
To: Martin Aliger
Subject: ***SPAM*** RE: [nant-dev] solution and compiler arguments
Thanks for responding. So the CustomProperties is still in proposal and
not implemented in the latest NAnt release? I couldn't find
Hi Eric,
I'd prefer converting your Web Sites to Web Application projects (included
with VS2005 SP1). Those have .csproj files and from the building view,
behave exactly same as all others c# projects.
hth,
Martin Aliger
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
Hi Ryan,
yes - I implemented it locally in my patched version. It never propagate to
main revisions though.
In last versions there is proposal for CustomProperties, an array of
arbitrary properties, which .net 1.1 builder could use as /nowarn and
/codepage values. I think, this will be quite
Hi Ram,
I'd love to see such a task, even more if it supports WebApplication model
(as well as web sites). Also there is aspnet_merge tool, which would be very
nice to have (they are interconnected afaik).
btw: those functionalities could be accessed directly via
System.Web.Compilation
, those project haven't be
compiled at all :-). Then there is web application model, which is normal csproj
(vbproj) and is completely compatible with NAnt (or msbuild or whatever). You
could find more info about it around web.
Ing. Martin
Aliger
Hi,
some time ago I
proposed an attribute forerror suppression when no node is found (xpath
returns empty nodeset). Sometimes one have to ask, whether certain node exist or
not, and there is not such option unless you set failonerror=false _and_ ignore
error messages. My new attribute
Hello,
I needed new function for datetime formatting to be able to add current
datetime to file/directory name. Normal to-string coudn't be used, since it
produce string with ':' and '/' characters.
Implementation is very simple (below). Here is example of use for new
function:
Hello,
I think, such a task could be useful! I bet NAntContrib project will welcome
that!
Martin Aliger
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of John Duff
Sent: Monday, August 14, 2006 3:48 AM
To: nant-developers@lists.sourceforge.net
0.85 though. We need a
release for every cost :-) But that VSWebCache should be
documented on solution page!
If we do not leave the VSWebCache concept, I think this should be well
documented on release. Unless that, I think we could postpone the solution
to next release (1.0?)
Martin Aliger
I have the same setup as you, everything is in distinct
directories and then it ends up sharing VSWebCache because
the project names are the same.
First - bad documentation! If there was any mention of VSWebCache, I'd try
to prepare for this. I was not aware of any (shared) cache up to
look into msbuild stuff soon. Promise.
Martin Aliger
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of mike61079
Sent: Tuesday, August 01, 2006 10:44 PM
To: nant-developers@lists.sourceforge.net
Subject: Re: [nant-dev] VSWebCache ObjectDir solution
But I'm not sure, if using _any_ cache is good thing.
I understand, but we should remain compatible with VS where
possible and in this case it's even necessary (for creating
strong named assemblies).
Could you clarify that strong name thing, please?
VS compatibility is a good thing, but I
Would a clean mode help you sleep better, or do you want to
get rid of the
VSWebCache for another reason (eg. for parellel builds,
although you'll have
this problem too with local obj dirs) ?
The parallel builds nighmares me. obj dirs are ok, I think. They should not
cause any trouble.
Changing to a local store for intermediate build output will
not resolve
issues if you build a project in parallel from the same local project
directory, but I'm sure that's not what you're doing.
No no! I have 2 distinct local directories with project of the same name.
Those 2 projects
this on simple project, but you know - those
synchonization problems are hard to simulate. And even harder to debug.
Thanks for quick response, Gert!
Martin
-Original Message-
From: Gert Driesen [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 27, 2006 5:59 PM
To: 'Martin Aliger
:-)
But I'm still not sure, this is the way, NAnt would go. That saddens me...
Martin Aliger
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Andrew Davey
Sent: Tuesday, February 07, 2006 5:32 AM
To: nant-developers@lists.sourceforge.net
Hello,
I think, we have some time, since xBuild seems to be in pre-alpha stage. But
interestingly, MSBuild is using Microsoft.Build.* namespace - xBuild mimics
this as well? Seems little ugly to me.
The difference between xBuild and MSBuild is only the platform, they both
use the same file
I'd like something like Miranda-IM has. See
http://www.miranda-im.org/
and their Addons site.
That's a nice idea, but I can't imagine how to justify
putting it into 1.0.
For someone with enough website administration experience it should be
matter of day or two. Of course, i'm not
, integration (if 3 will be chosen) have to be done
carefully. Or could we restrict NAnt to 2.0 framework? I don't thing so...
Maybe 2 distributions: 1.0 compatible, and 2.0, compiled for 2.0 and with
additional features?
Martin Aliger
-Original Message-
From: [EMAIL PROTECTED]
[mailto
This is another thing worth of implementation under 1.0.
I'd like something like Miranda-IM has. See http://www.miranda-im.org/ and
their Addons site.
Martin Aliger
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Martin Aliger
Sent: Tuesday
should addess in 1.0: VS2005 projects. Or MSBuild cooperation. The
Are people really waiting for this ?
I think so. How many of 1.0 users use solution task? Same percentage of
2.0 users would want to use simmilar feature under 2.0. Or they have to use
something else...
Shouldn't we focus
Mike, Brad,
FWIW, we just use the exec / task to run MSBuild, using the
2.0 Framework. Works just fine.
Yes - but you give up many features solution do for you. Inter-project
dependency solving is what I desperatelly need. We have ~300 .csprojs (under
1 ccnet project) with new ones
)
Martin Aliger
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Flex
Sent: Wednesday, June 28, 2006 11:37 AM
To: nant-developers@lists.sourceforge.net
Subject: [nant-dev] MailLogger task failing...
Hi guys, I have posted this in the users list
there is some way how to accomplish this initialization by hand,
without OE magic. Try to search for System.Web.Mail.SmtpMail. That is what
nant is using.
btw: Confusing? Mailing systems are! Wish MS do some cleanup it this area.
Perhaps WinFX...
Martin Aliger
-Original Message-
From
the
same) and I never have a problem with installing OE to the server machine.
But, it should be documented as dependancy in nant's documentation. Or
atleast add troubleshoot section as ccnet has. You are not the only one,
having problems, that's sure.
Martin Aliger
-Original Message
for FTP (in .net 2.0) or other protocols in .net.
WebDavClient.cs from solution helped! Giving a credit to Matthew
Mastracci!!
GetTask.cs also helped. Credits go to Jay Turpin and Gerry Shaw.
Regards,
Martin Aliger
---
All the advantages of Linux
, even that not
so well tested, perhaps. We could always rerelease patched version.
Regards,
Martin Aliger
In my opinion, that's enough to close out 0.85 and release
it. Granted, I'm exploiting the fact that the default
priority is 5, not 9.
Nevertheless, 0.85 is still a pre-1.0 version number
. Maybe not in
mine, but they certainly helped many other users with unit testing. As well
as I hope msbuild-* tasks would help with msbuild integration. If not, I'd
simply wrote mine own NAnt and do not share with others.
Martin Aliger
-Original Message-
From: Brass Tilde [mailto:[EMAIL
be worth of. Mainly
since in large solutions, resgen time is crutial (every ms counts).
Martin Aliger
-Original Message-
From: Gert Driesen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 07, 2006 9:56 AM
To: 'Martin Aliger'; nant-developers@lists.sourceforge.net
Subject: RE: [nant
FWIW, I've had great success just using the exec / task for
running MSBuild. It works just fine, and I can pass in any
of the parameters I want. We started using it just about 5
minutes after we started building our .NET 2.0 applications,
i.e. long enough to modify the build files to
I haven't had any problem resolving project dependencies.
MSBuild seems to be smart enough to navigate the hintpaths
defined in the various project files and deals with those
just fine. Even the COM Interop stuff is working just peachy keen.
There are issues, believe me. Maybe its not
Namespacemanager on Element should be there for namespace
handling of nant build file itself. I do not test this funcionality, but we're
solving this issue some time ago.
I'm
looking forward to get a look into your changed tasks. Is it on nightlies
already or have you a patch somewhere?
Hello,
Has anymore work been completed on the msbuild-solution task?
No, nothing serious since early january. I'm testing overall stability and
performance on our enterprise build. But most of our projects are still on
net-1.1. Anyway, it looks very well.
Looking through the
Gert,
you wrote (in
response to one issue report):
Resgen should be a lot
faster in the nightly builds of
NAnt (http://nant.sourceforge.net/nightly/latest). Can you try this and let us know if
performance is acceptable ?
I tried and there is very significant speed improvement
Hi,
To build them, you have several options. There's a few
patches floating around that will create new tasks for
MSBuild projects
Give a try to mine proposal. It could be found here:
http://maliger.webpark.cz/binaries.zip (there are sources as well, if
you're interested)
You need
it is considered error, blaming nant users with false
errors.
I'm open to any changes/expansions to this. Maybe defaultValue=whatever is
better? (and use this value if no match found?)
Martin Aliger
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Ian MacLean
.
Good luck,
Martin Aliger
-Original Message-
From: Mike Edenfield [mailto:[EMAIL PROTECTED]
Sent: Friday, January 20, 2006 4:56 PM
To: Martin Aliger
Cc: nant-developers@lists.sourceforge.net;
[EMAIL PROTECTED]
Subject: Re: [nant-dev] Ongoing work on MSBuild project file
formats
Hello,
I dont know how much is mine work official. Hard to determine in
open-source projects :-)
Which link is dead?
http://maliger.webpark.cz/binaries.zip. This should work. (try to copy/paste
into yout browser if you find link broken). You'll find modified solution
task and new
I think, it could be worth addition to NAnt's core. Even
that we could not deprecate xmlpeek task, becouse of XML namespace support. Or
we have to find some way how to pass namespace map into functions (new
datatype?).
Regards,
Martin
From:
[EMAIL PROTECTED]
[mailto:[EMAIL
Hello,
strangly, it do even for me, when clicked on that url directly. It works,
when I copypaste it into mine IE. No idea why. This freeweb is rather
buggy, it seems. Unfortunatelly, maillist refuse to accept .zips 40kB.
Sorry for inconvenience.
Otherwise, I'm glad you want to try out this
Hello,
This introduce new boolean flag, which disable error message when XmlPeek
task coudn'd find any maching node. This is very useful in some scenarios.
I think, it could be useful to community, se here it is.
Regards,
Martin
[I sent this once before, but maybe it wasn't documented
certainly need some time to
tune it.
btw: Do you review mine changes to NAnt.VSNet? Are they ok? I'd like to keep
msbuild stuff separate from core for while. Maybe in NAntContrib or
elsewhere (becouse of 2.0 dependency). And those patches was needed to
enable it.
Martin Aliger
Martin,
I'm
http://maliger.webpark.cz/binaries.zip
http://maliger.webpark.cz/sources.zip
http://maliger.webpark.cz/nant.vsnet.diff.zip
Hello,
finally I get first working version of MSBuild support to NAnt. I hope, you
would like it.
[for you lazy guys: copy attached binaries to latest NAnt bin
exec
program="..\nant\bin\nant.exe"
commandline="-buildfile:MiddleTier\MTM.MiddleTier.build build
..\..\..\Log\MTM.MiddleTier.build.log" /
This will never work. "" sign
is shell (cmd.exe) special handling, its not common to process running. NAnt's
exec task have special attribute for
threshold=Error/
Martin
_
From: chellu pradeep [mailto:[EMAIL PROTECTED]
Sent: Sunday, December 11, 2005 4:26 PM
To: Martin Aliger
Subject: RE: [nant-dev] writing the NAnt output to a log file ??
even after i use exec task's output attribute i can see the result on the
command prompt
Hi,
I don't think we need to make solution task compatibility a
goal here.
I was thinking same, but first I wanted to use msbuild, I found myself in
situation where solution is used today. Even that msbuild is quite general
system, we, nant users, will call it mainly to compile vs2005
to NAnt.exe.config under framework name=net-2.0.
Regards,
Martin Aliger
PS: I'll refactor to follow nant's conding standarts lately. Sorry for
inconvenience. This is just a preview...
Note: MSBuild from net 2.0 Beta 2 will not compile solutions from VS2005
final. Took me hour to figure :)
// NAnt - A .NET
-is2005 function
(suggest name). It could be good starting point atleast. I'll give you know.
Martin Aliger
-Original Message-
From: Gert Driesen [mailto:[EMAIL PROTECTED]
Sent: Monday, December 05, 2005 1:54 PM
To: Ian MacLean; Martin Aliger
Cc: [EMAIL PROTECTED]; ! nant
Subject: Re
at all to write msbuild task
just as a wrapper around msbuild.exe as ccnet do it. Something like ant
already do. Not bad idea. What others think about this? Maybe I'd not give
up mine hard-earned build scripts after all :-)
Martin Aliger
-Original Message-
From: Gean Boegman [mailto
with
msbuild. For now, we have 2 incompatible build systems (I'm sorry I ignore
others...)
btw: vs2003 sln support is not simple xslt either. Its more than 5000 c#
line codes.
Regards,
Martin Aliger
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf
Hello,
I just noticed that
fileset containting pattern like this "foo*/xxx" are
considered recursive and therefore DirectoryScanner scans whole directory
structure. That is not (completely) true - thosepatterns could not contain
files in other depth than 1.
I'd like to come with some
c:\test\foo\etc should be discarded when scanned and not dip into, since
none file/folder in it could ever satisfy any pattern.
c:\test\foo\Gordic1 shouldn't be discarded and scanned normaly as today.
c:\test\foo\Gordic1\_svn shouldn't be discarded as well
Hello,
I agree, these problems should be resolved before we
introduce this feature.
I'm tempted to include it and let people have a play with
it and then
refine it as necessary rather than holding out until its
perfect. What
do people think ?
I'm not convinced to either. Resolve
I'd rather have a more general approach, where all global types
implement support for merging two distinct instances.
Is this meaningful for all types? Or just those that are
collections?
Does it make sense, for example, to talk about merging two proxies?
Exactly. btw: it would be
I would definitely like the ability to combine filesets, personally...
it places less onus on the task creator to add explicit
support to reference files in different locations.
I think that it is critical to support merging filesets with
different basedirs, given this is probably the
already sent patch for this and could send more
current one, if community have interest for it. I'd like to see that
incorporated in NAnt's core.
btw: it also allow adding to existing fileset - and its what I need in
production.
Martin Aliger
-Original Message-
From: [EMAIL PROTECTED
...
Martin Aliger
-Original Message-
From: Rory Becker [mailto:[EMAIL PROTECTED]
Sent: Friday, August 26, 2005 10:50 AM
To: Martin Aliger
Subject: Re: [nant-dev] Fwd: Filesets referencing filesets ?
Assuming that your syntax has not varied too greatly from the
version I saw
be hell. I personally trying to do all stuff in
NAnt.
- external shells are hard to maintain and port to other OS, NAnt script
is not.
Martin Aliger
---
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find
/BuildServer/clean.build
unless=${debug} /
!--#endif--
/target
(or use of PI ?if ?)
Just an idea,
Martin Aliger
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Gert Driesen
Sent: Wednesday, June 29, 2005 9:40 PM
To: 'Shawn Oster'
Cc: nant
Here is testcase covering all possible scenarios which comes to my mind. If
you see anything more those few let me know, I'll add it!
Martin
-Original Message-
From: Gert Driesen [mailto:[EMAIL PROTECTED]
Sent: Monday, June 13, 2005 10:11 PM
To: 'Martin Aliger'; nant-developers
Hello,
in past releases
there was very nice feature in solution task named "Continuing build
with non-dependent projects.". When any project in solution failed for any
reason (compile error, missing reference, ...), projects which do not depend on
this failed one was still built.
Somehow
to prevent future regressions.
Martin Aliger
in past releases there was very nice feature in solution
task named
Continuing build with non-dependent projects.. When any project in
solution failed for any reason (compile error, missing
reference, ...),
projects which do not depend
/example.txt
/fileset
!-- /if --
--
Comment By: Martin Aliger (maliger)
Date: 2005-06-13 17:55
Message:
Logged In: YES
user_id=655297
its by design in current sources. I just completed patch to
allow type definitions
directly?
Martin Aliger
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Martin Aliger
Sent: Monday, June 13, 2005 3:52 PM
To: 'Gert Driesen'; nant-developers@lists.sourceforge.net
Subject: RE: [nant-dev] solution continuing build with
non
, it was really
simple.
Martin Aliger
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of SourceForge.net
Sent: Friday, May 27, 2005 7:53 PM
To: [EMAIL PROTECTED]
Subject: [nant-dev] [ nant-Bugs-1210046 ] Fileset fails when
nested in an if block
Hello,
I checked Serge's implementation of his xmllist task and like it much. It
adds some features to official xmlpeek like no-node default value
fall-back and multi-node list retrieval.
I sent him personal mail about ideas how to make those extension directly to
xmlpeek and still be
Interesting. I think there is an opportunity for optimizing this, to
eliminate the asis by changing the synchronization point.
For example, if the contents of the foo1 fileset were not computed until
actually needed, then you could do away with the asis and apply the exclude.
I'm not sure I want
I think you should await consensus that this feature is
indeed necessary, and as such will end up in NAnt cvs.
That is what I'm waiting for. If more test-cases or some fine-tuning (like
no 'asis') will be needed, I'll do it. That is also reason why I dont want
change alot of things, just
. But I see, there is no way how to filter out existing
fileset to another one... So maybe its not right way? Ideas?
Note: reason why I used asis is to prevent double-scan. asis includes are
not scanned anymore, and all included files via includesfileset was scanned
once already.
Martin Aliger
Hi
all,
Attached is patch
and test-case for extension for fileset type. It allows to include
another fileset in current one. E.g.:
fileset id="foo1"
includes name="world.peace" /
/fileset
fileset id="foo2"
includesfileset refid="foo1" /
includes name="world.war" /
/fileset
It works even
Hi all,
gratulations for rc3! However I tried to bootstrap from source distribution
on Windows and failed. Here is the error:
System.Resources.MissingManifestResourceException: Could not find any
resources appropriate for the specified culture (or the neutral culture) in
the given assembly.
(.vsproj)'s which is pretty easy but no very clean.
What you think about this approach?
Ing. Martin
Aliger
GORDIC spol. s. r.o., Erbenova 4, 586 01 JIHLAVATel: 567 309
136, 567 303 601
From:
[EMAIL
results as MSDataSetGenerator
(intentionally).
Anyway, it could be cool to have this as nant task! Even more if it works
under mono (doesn't mono project have something like this?)
Martin Aliger
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Brar
mentioned below :-)
Martin Aliger
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of James, Justin
Sent: Monday, February 14, 2005 6:09 PM
To: nant-developers@lists.sourceforge.net
Subject: RE: [nant-dev] DataSetGenerator
What Visual Studio uses
GD I had a very quick look and apparently there seems to be
another prefix :
GD hklm\publicassemblies
It refers to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\7.1\AssemblyFolders\Publi
cAssemblies
only \dn seems to have special meaning.
GD But I'm not sure yet what this refers
If this change is done, what about to lower verbosity when deleting
non-existing files/folders also? I think verbose level is ok for that
(todays it is error via BuildException).
Martin Aliger
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Owen
Hi Nicke,
good call I think. Verbosity problem is here, and I really want so solve it,
but I prefer to do it after release. I also think (and beleive others also)
we need shorter release cycle (aprox. 4 a year?)
1/: I didnt catch it - sorry. Structure of Nant's XML log is pretty vague -
thats
ps : I've got a small nant function called is-assembly (to
determine
whether a file is a valid assembly or not). Is it worth
contributing ?
I'm using it to separate my legacy dll from assemblies. I know
there's the get-assembly-name trick, but maybe it's worth
it. Tell me
what
- Ant's arg element allows a reference to an existing
path definition to be specified using a pathref attribute
on arg, while we do not allow this.
arg pathref=fop-classpath /
Is this something we should support ? I'd like to avoid
this, if its not really necessary.
Isn't
Exactly as Gary wrote! :-)
But the xmlpeek task is definitely something different as a user
expects
a
given property to be set to a value. If we don't output
anything at a
all,
when no matching node is found then that property will not
be set and
users
will have a hard time
We could just go for a nested fileset element after all. I'm
implementing
something similar for a type called path or pathset
(similar to the Ant
path element). Meaning :
fileset id=...
fileset refid= /
include name=... /
/fileset
ok. I could implment
1 - 100 of 225 matches
Mail list logo
