I've just finished coding the .licx file compilation routines. You can
now compile a .csproj file containing licensed components with the
classnames stored in an .licx file. This file then is compiled to
Outputname.extension.licenses and embedded as a resource.
If anyone is interested, I can
I have a task for NAnt that will compile projects exactly as VS.NET
does. Please see my earlier messages for more information, and let me
know if you are interested in trying out the custom NAnt task.
Szymon Kobalczyk wrote:
Ok, here is the last problem I had to face today. Some of our project
Szymon,
Glad to have you on the list.
Because I was determined not to surrender easily I have spend some time to
extend SLiNgshoT with all necessary functionality. My current version is
able to generate proper build files for solutions that use enterprise
projects.
Awesome. Sounds cool.
I
Ok, here is the last problem I had to face today. Some of our projects are
strongly named and signed. All of them use the same key that is located in
the top folder of the project tree that is referenced by relative path. So
the adequate line of AssemblyInfo.cs file in such projects may look like:
Hello again,
The next problem I've stumbled on is that our projects reference some other
assemblies that are neither in the same solution nor standard system
libraries. Instead these assemblies are kept in separate folder and
referenced by setting the 'Reference Path' option in project properties.
Hi,
I'm new on this list so some of my questions may seem trivial and may be
already solved. Recently I have discovered NAnt and I intend to use it to
prepare scripts for automatic nightly builds for few projects I'm currently
working on. All these projects are created in VS.NET and I have already
Sorry about that. The right version is checked in now.
Ian
i could be completely wrong about this, but it seems as though the checked
in version of CompileBase from nov 7 expects the method
'GetManifestResourceName' to exist in ResourceFileSet. the version of
ResourceFileSet checked in to CVS,
I've setup a script to take a snapshot of the latest nantcontrib project
and place it on a link on the nant snapshot page. It doesn't keep
backup copies because I'm soon going to run over the quota for web disc
space (100 MB).
http://nant.sourceforge.net/snapshot/
Scroll down to the bottom of th
I believe that there are a few important differences between SLiNgshoT
and my VS project compiler, that I outlined in a previous message:
1. SLiNgshoT works on solutions, the code I've written works on projects
2. The build files that SLiNgshoT generates require resgen - this is
included with
i could be completely wrong about this, but it seems as though the checked
in version of CompileBase from nov 7 expects the method
'GetManifestResourceName' to exist in ResourceFileSet. the version of
ResourceFileSet checked in to CVS, as far as i can tell is missing this
method.
owen.
Hello,
A good point. Gerry, would it be possible to make a nightly CVS
snapshot available for NAntContrib?
In the meantime, contact me directly if you want me to mail the latest
version of NAntContrib.
Best regards,
Bernard
> -Original Message-
> From: Dag Christensen [mailto:Dag.Chri
Off topic, but would it be much work providing a nightly build or archive
of Nantcontrib? My company is Microsoft-only and has thus blocked cvs
access in the firewall. The extras folder in the nant nightly build
contains the slingshot folder but it is empty.
I just signed on to this list, so pleas
Hello Matthew,
Your description sounds like what SLiNgshot does, a tool and a task that
are already included in the NAntContrib [1] project.
It converts VS.NET solutions to NAnt build files, as in the following
example:
However, the to
13 matches
Mail list logo
