Ok I seem to have a work around for the “403 error” IIS 6.0 ala
Windows 2003.
Windows 2003 locks down everything on IIS by default so you will need
to enable WebDav or you cannot compile your code.
Additionally a rather nasty part….is that if you are compiling
your project via the sol
- Original Message -
From: "Sascha Andres" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, November 14, 2003 6:39 PM
Subject: Re: [Nant-users] asminfo und ComVisible Attribut
> Hallo Gert,
> * Am 14.11.2003 (17:41) schriebst Du:
> > I think I'm missing the problem here : why i
Hallo Gert,
* Am 14.11.2003 (17:41) schriebst Du:
> I think I'm missing the problem here : why is '[assembly:
> ComVisibleAttribute(false)]' wrong ?
The compiler doesn't reject ComVisibleAttribute set to
false, but when looking at the compiled result, ComVisible
is set to true (default), hence the
- Original Message -
From: "Sascha Andres" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, November 14, 2003 3:09 PM
Subject: [Nant-users] asminfo und ComVisible Attribut
> Hi,
>
> I want to set the ComVisible attribute to false. It is
> defined in System.Runtime.InteropService
Cool! Looking forward to that being in a stable release. Or is it
something that snuck into 0.8.3 that I missed?
(I've been awol from paying attention to the cvs list, did my file
comparison patch for make it? (I rely on it quite heavily at the
moment.)
> -Original Message-
> From: G
Jaroslaw Kowalski brilliantly extemporized:
>
>
Amen, brother. The only problem I can imagine you'll have are type
comparisons, but if you just throw an intelligent build exception when
the types don't match before you touch a.Equals(b)... I'd be a happy
man with just == and != to start with.
Hi,
I want to set the ComVisible attribute to false. It is
defined in System.Runtime.InteropServices. So I added an
import tag for that assembly to asminfo's imports. I also
added '' to the attributes node. The task now genereates
'[assembly: ComVisibleAttribute(false)]' which should be
'[assembly
Hi Rishi,
Not. A work around would be to use an exec task and specify the cvs
command.
I have put together a road map of sharpcvslib features and approximate
release times. The road map identifies approximate feature dates for
the command line client we are working on but as time permits
Hi,
I wanted to know if CVS tagging is supported in Nant or not?
-- rishi
Hi,
I had a problem getting the NAnt contrib VB6 task to work. Turns out the path
to the VB6.exe wasn't setup on my machine. My firm has all the dev tools
centrally scripted so this problem will repeat itself on other peoples
machines. So, I thought if I could setup the environment in my NAnt scri
Just a small hint : the task no longer requires IIS to build
ASP.NET projects as you can now use a to map project url's to file
paths :
http://localhost/A/A.csproj";
path="c:\inetpub\wwwroot\A\A.csproj" />
Gert
- Original Message -
From: "David Reed" <[EMAIL PROTEC
Every time I see constructs like this I want to scream for the support of
simple expression evaluator, because without them NAnt syntax gets uglier
every time someone invents a potentially useful extension.
MSBuild has a very simple EE here, and I think it's a good idea to support
it too.
I think
Hi,
I have been using the IDE for compiling and debugging my web appl project.It
works just fine.
But I built a NANT.build for the same,there seems to be some problem..
I have written the below nant.build file.
It says BUILD succeeded when I do "NANT" on the VS .NET cmd prompt. But when
I open
13 matches
Mail list logo
