Gert,
>We actually need the verbose output that you get when NAnt is initializing
>it's framework configuration. This is done at startup.
How can I get that information? I've done following:
nant -t:net-2.0 -verbose
and the output looks as follows:
>>>
NAnt 0.85 (Build 0.85.2344.0; rc4; 02.0
ent: Tuesday, August 01, 2006 9:01 AM
Subject: RE: [NAnt-users] windows application won't start after compilation
>Are you sure you've installed the SDK, not just the redistributable ?
>Try running NAnt in verbose (NAnt.exe -verbose ...) or debug mode
>(NAnt.exe -debug ...)t
>Are you sure you've installed the SDK, not just the redistributable ?
>Try running NAnt in verbose (NAnt.exe -verbose ...) or debug mode
>(NAnt.exe -debug ...)to get more information as to why the .NET Framework
>2.0 could not be found.
Following output I've got with -verbose:
build:
- Original Message -
From: "Rico Schaepe" <[EMAIL PROTECTED]>
To: "Gary Feldman" <[EMAIL PROTECTED]>;
Sent: Tuesday, August 01, 2006 6:54 AM
Subject: Re: [NAnt-users] windows application won't start after compilation
> >Do you have the
>Do you have the .Net 2.0 SDK installed? This is a separate installation
>from the .Net 2.0 framework (which must be installed first).
It is installed but although it doesn't work if I compile for the .Net 2.0
framework. The error is:
The SDK for the 'net-2.0' framework is not available or not
Rico Schaepe wrote:
> Thanks Gary,
>
> It works with net1.1 but what do I have to do that it also works for net2.0 ?
>
Do you have the .Net 2.0 SDK installed? This is a separate installation
from the .Net 2.0 framework (which must be installed first).
Gary
-
Thanks Gary,
It works with net1.1 but what do I have to do that it also works for net2.0 ?
And is there a better solution to copy the external libs to the build path, so
that the existing libs can be used ?
Thanks in forward
Cando
Rico Schaepe wrote:
> ...
>
> The first compilation attempt wo
Rico Schaepe wrote:
> ...
>
> The first compilation attempt works but the application won’t start
> without error. I opened the windows task manager and look at start up.
> The app was seen short in the process list and disappear. I was
> looking for the reason and found some threads in the mail
