Hmm, missed the 2.0 Framework reference. The problem you are striking is
to do with CAS (code access security), which should help with searching.
OK, go to Administrative Tools, and select "Microsoft .NET Framework 2.0
Configuration"
Then select "Runtime Security Policy" from the nav tree.
My gues
Hi, We're in the middle of converting our c# codebase to VS 2005 Projects/Solutions and thus are running into the inability to build projects/solutions with nant. We've been using the contributed task lately to build individual solutions but doesn't seem like this will work for our wider scale
I've tried but still failled.
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 to run executables from network shares. One quick
>
Lorenzo,
Unless you include the csc element from your script file, it's difficult
to say for sure, but the most obvious question to ask is, have you
included a sub-element in your csc task? Have a look at
the bottom of the csc task's documentation page for an example.
http://nant.sourceforge.net
