Closed GoogleCodeExporter closed 9 years ago
I fixed most of those issues, beside the config file. .NET 1.1 does not load
config
files for DLLs so this is purely mono. I have to think about how to run this
nicely
from within NUNIT on windows... the 1.1 mentioning was related to the .NET
runtime
used, i clarified that. I also added a VS2003 csproj file.
Original comment by fman...@gmail.com
on 16 Aug 2006 at 1:18
I thought it was NUnit doing some behind-the-scenes hacking to load the config
file
for a DLL.
Indeed, this blog entry suggest this is what is happening.
"NUnit tells the .NET framework the name of the configuration file to use."
http://nunit.com/blogs/?p=9
Original comment by rbir...@gmail.com
on 16 Aug 2006 at 2:37
hmmm.. i got to check that, as this does not happen on my windows setup. Will
investigate
Original comment by fman...@gmail.com
on 16 Aug 2006 at 4:31
Fixed the config file so that it should be .net 2.0 compliant per documentation
Original comment by fman...@gmail.com
on 1 Sep 2006 at 8:15
Original comment by fman...@gmail.com
on 1 Sep 2006 at 8:15
Original issue reported on code.google.com by
rbir...@gmail.com
on 11 Aug 2006 at 8:25