-users-boun...@lists.sourceforge.net
[mailto:nant-users-boun...@lists.sourceforge.net] On Behalf Of Dominik
Guder
Sent: Friday, September 16, 2011 3:40 AM
To: nant-users@lists.sourceforge.net
Subject: Re: [NAnt-users] Getting errors after upgrading to NAnt .90 -
Any ideas?
Hi James,
calling LoadTasks
On 18/09/2011 3:03 a.m., Macdiarmid, James D. wrote:
I don't believe XP has an Unblock feature.
Yes, it does - both XP Professional and XP Home have this feature. IIRC,
it was introduced in SP3 - the big security patch for XP.
Keep Smiling,
Bevan.
Subject: Re: [NAnt-users] Getting errors after upgrading to NAnt .90 -
Any ideas?
On 18/09/2011 3:03 a.m., Macdiarmid, James D. wrote:
I don't believe XP has an Unblock feature.
Yes, it does - both XP Professional and XP Home have this feature. IIRC,
it was introduced in SP3 - the big security
Hi James,
calling LoadTasks is by design. For short: Nant.exe crawls all
*Tasks.dll files in its folder and search for Tasks.
One question: Did you unblock the downloaded zip file?
From nant's issue tracker:
I had this exact same problem. It comes from the assembly not being
trusted. Windows 7
I upgraded to NAnt .90 and modified the NAnt.Exe.Config to support .NET
Framework 4. Installed the latest Windows SDK. I don't understand why
my script is calling the LoadTasks when they are not even in the script.
Anyone know how to fix these errors?
I'm running Nant on a simple script to
