Please remove [EMAIL PROTECTED] from the mailing
list.
Thank-you.
__
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com
---
This SF.Net email sponsored by: Parasoft
Error pro
Hello Matthew,
For more info on Web Projects, see
http://msdn.microsoft.com/library/en-us/vbcon/html/vbconintroductiontowe
bprojects.asp
The mapping problem could be solved by letting the user of the solution
task specify the mappings.
This is an easy approach that is used in Slingshot.
Example
Ahh... How does VS.NET get the mapping from IIS path to file share? I
would love to know. :) I've had so many problems with an auto-build
system when the web share wasn't properly set up, etc.
From running Etherial traces while opening/compiling an ASP.NET trace,
I got the impression that
Hello Matthew,
While it is true that VS.NET can use FrontPage extensions to do this,
another way is to use file shares. This access mode tends to be faster
and (obviously) does not require to have FrontPage extensions installed.
This is an option when creating a new project, and can be checked in
[EMAIL PROTECTED] wrote:
Matt,
Thank you for your reply. Unfortunately, I'm even more confused now. The
.sln file points to http://localhost/blah/blah.csproj yet VS.NET is able to
resolve all this and compile just fine, without any extra steps to enable
WebDAV write access and source access.
Ther
Scrub this - it was my mistake. Looks like I typo'd a source filename somehow and it
wasn't being thrown out. Is there a way of getting to throw an error in the case
when source files are missing, instead of just compiling the ones it does find and
carrying on as if nothing was wrong?
Hi
I've got a prob with a DLL that NAnt 0.8.2 compiles on a machine that has .NET
Framework 1.0 on it, not 1.1. In short:
- it fails if I have a reference to the NAnt-compiled version of this DLL when
compiling another DLL
- it works if I have a reference to the VS.NET-compiled version of thi
Title: [Nant-users] Conditional Actions on build failure
Hi again,
If your problem is the following: sending the test results in case of
filure of the test, you could do is the following:
let all your unit test runnen with the "failonerror" false, let the nunit
task gather all informatio
Title: [Nant-users] Conditional Actions on build failure
Hi david,
I think the problem is the following
I dont think you can set properties in the nunit2 task;
fork="true"/>
try changing to this
