Michael,
VB.NET does not support xml docs out of the box. You did mention that you
do get the xml doc when building using VS.NET, so are you using some add-in
in VS.NET to generate the xml docs ?
Gert
- Original Message -
From: "Michael A. Angelo" <[EMAIL PROTECTED]>
To: "'Gert Driesen'
I house mine in the parent folder of the app. In
other words:
D:\Program Files\MyApp
All of our projects exist in a subfolder of this
folder such as:
D:\Program Files\MyApp\Project1
--- Brian Beaudet <[EMAIL PROTECTED]> wrote:
> I'm interested in hearing where other's stick their
> .build fi
Should I mention that these are VB.net projects? I don't think the doc .xml
file gets created with VB.net projects
Help
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gert Driesen
Sent: Friday, April 09, 2004 4:07 AM
To: Michael A. Angelo; [
I'm using the tag with the tag. I am not using the
.sln file. Is this why I cannot get the .xml doc file?
TIA
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
Ge
I forgot to mention that the top lines of the config file
need to look like this. The PublicKeyToken will change depending on the version
of the .NET framework you are using. It is also possible to use other section
handlers in place of the NameValueSectionHandler.
Derek Pierson
3Leaf Solutions, LLC
[EMAIL PROTECTED]
I'm not an expert with the task, but I would recommend that you do the
following:
* If possible make sure all paths to files, resources, etc, in your solution and
project files are relative to the solution root directory. (VS.NET will show some of
the paths in the properties as absolute paths
You know, you can create a user specific config file and just specify it
in the main config file. This way, each developer and/or test server can
have the connect strings there. If the user.config isn't there, it
doesn't error, if it is there, those settings override what is in
web.config
-Ori
Why do you have to modify the config files anyway? In the
past this is what I have done.
Created custom config sections in the app.config or
web.config file tied to NameValueHandlers (Google for “custom config
files c#”). Then I create a general section that contains the environment
nam
I tend to keep mine in the same directory as the project file (.csproj). If
there is more than one project in the solution, then I usually have a
"master" build file (which calls each project build file as needed) in the
same directory as the solution.
Jim
> I'm interested in hearing where other
Eric,
At this point I'm only using Nant to perform test builds and run unit
tests at some regular frequency (nightly or continuously?). This is all
done on a dedicated server.
Each developer is responsible for grabbing the source code and modifying
the config files (custom or .config) to suit
I’m interested in hearing where other’s stick
their .build file(s). I’m currently housing mine in a directory one
level above my source code just to keep things cleanly separated. However, I’m
starting to wonder if it’s worth it and I’m considering moving to
the same level in my source co
If I use the task to make a build, how
would that work if I’m grabbing the source files from version control and
placing them on our build server. Will I have to make an exact duplicate directory
structure as what’s on the development machine? Do I have to start with
the same drive and w
Hello,
It’s my first time using a mailing list, and
also my first time using nant, so be gentle J
My problem is as follows:
I have a script to build some solutions. Some of them
c#, some of them vb.net. The problem is that, while building the c# solutions works
fine, th
I am not using the task with the .sln file. I am only wanting to
specify the projects using the tag.
Is this why I am not getting my .xml doc file?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gert Driesen
Sent: Friday, April 09, 2004 4:07 AM
To: Mi
Michael,
The task definitely also creates the xml doc. Are you sure
you're building the solution using the task in the same
configuration as you do when you build it using VS.NET ?
Gert
- Original Message -
From: "Michael A. Angelo" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: T
Brian,
You can also just use the task
(http://nant.sourceforge.net/nightly/help/tasks/xmlpoke.html) to change
values in your XML configuration files for a specific deployment scenario.
Hope this helps,
Gert
- Original Message -
From: "Brian Beaudet" <[EMAIL PROTECTED]>
To: "'Nant User
Getting nant to work with mono 0.31 is non-trivial. Can you update mono from
CVS and do:
$ export MONO_NO_UNLOAD=1
before running nant?
This is a workaround to a known bug in mono which messes up nant/nunit.
Jarek
- Original Message -
From: "Pedro Santos" <[EMAIL PROTECTED]>
To: <[EMAI
On Thu, 2004-04-08 at 23:09, Markel, Kris wrote:
> You should also have these dlls in your bin directory:
> NAnt.NUnit.dll
> NAnt.NUnit1Tasks.dll
> NAnt.NUnit2Tasks.dll
>
> If any of these are missing, the NUnit tasks won't run.
>
> -k
It was that, those files were not compiled. Now Nant detects
19 matches
Mail list logo
