This is the exact reason I shifted to InnoSetup. We were using Windows
Installer but were also using the Microsoft Application Updater block to
provide automatic deployments of new versions of our various applications.
Windows Installer would quite happily realise some changes had been made to i
One of the latest nightly builds supports VS2005, but of course that is
a beta software. Works well for me though.
Angus.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Alan
Guedeney
Sent: Friday, 21 September 2007 2:18 AM
Check what version of the framework nAnt is running under. It could be
running under 1.1 and not 2.0 as VS 2005 does.
You can pass this as a command line parameter in your call to nant
(-t:net-1.1. I assume -t:net-2.0 for version 2.0 frameowrk) or I think
there is a setting in nant.exe.config or
You can also tell nAnt which framework version to use in the config
file. You can then avoind always telling it which framework to use from
nAnt calls
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob
Archer
Sent: Wednesday, 17 Ja
XMLSlapWithATrout is due in the next major version!!! :-)
he he!!
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of R. Tyler
Ballance
Sent: Thursday, 4 January 2007 8:46 AM
To: nant-users@lists.sourceforge.net
Subjec
led.
> But you talk about .NET Wizzards 1.1,
> and I'm working on .NET 2.0.
>
> Are they compatible?
>
> Olivier.
>
>
> angus.grant wrote:
> >
> > I think this comes down to .NET Framework security permissions. By
> > default, .NET refuses t
I think this comes down to .NET Framework security permissions. By
default, .NET refuses to run executables from network shares. One quick
way I have found is to go to Administrative Tools, and select the
"Microsoft .NET Framework 1.1 Wizards". There is a choice there to
"Trust an assembly". You ca
I use
nAnt all the time for all our companies projects. But I must admit I am a bit of
a lazy user, simply pointing nAnt to our solution files to build debug or
release versions depending on choice, a clean up task, another task to create
install packages, nUnit testing, and nCover tests as
To
in-charge-type-dudes,
There seems to be a
lot of emails about the nUnit2 task not working properly. And generally the
reply is a canned "nUnit2 task is not really supported. You are better off using
and the nunit executable"
For the 1.0 release, would it be an idea to remove the nUnit2
