I was getting the same error too and nothing seemed to work for me... then i realized that nunit.framework.dll was missing in my projects debug folder. I just copied it and tried runnig the test again... booom it went ..:)
Hmmm, tough one. I'm getting the same error (both in the NUnit GUI as well as within TestDriven.NET.
What's odd is, it only happens on some of our machines.
I tried fixing it like the Google Groups post said, didn't work. Found your solution posted here -- unfortunately I don't have a .config file for the dll I'm testing; no config files in play here at all, as far as I can tell.
Any other ideas?
What version of NUnit and TestDriven.Net are you using Judah? Make sure all the machines have the correct/same version of NUNit installed as if you specify the version number and you have a different version you may get this error also.
I've had the same problem, I was exposing an enum as part of a data contract on WCF and seeing the returning message crash out.
I reverted to a primitive type and it solved the problem.
Thanks for this Damien. Very helpful.
Regards,
David
Cheers for the heads up, big fan of the Resharper. I’ve also been using the Resharper (R#) v4 nightly builds to get the LINQ & XAML support.
It is a pity; .Net 3.5 SP1 and Visual Studio 2008 SP1 are both allot more than a collection of fixes (even thou they include over 100 fixes).
There are such goodies as ASP.NET URLs routing support (nice clean URLs) which allows you to define the syntax of the URL (as seen in MVC), ASP.NET Dynamic Data, improved WPF designer (I’ve had my had my fair share of issues with this past year), “Back Button” support for AJAX enabled web applications... and so much more.
It is more like .Net 4.0 than a simple Service Pack! (Another misleading name)
If you care here is where I heard all about the included new features from better men than I:
Scott Gu: weblogs.asp.net/.../visual-studio-2008-and-net-framework-3-5-service-pack-1-beta.aspx
.Net Rocks Podcasts: www.dotnetrocks.com/default.aspx
Now I am torn between which of the 2 to choose... R#v4 or VS9 & .NET 3.5 SP1.
I’ve been really digging the Visual Studio integrated unit test runner allot and the productivity and macro support within Resharper for creating new Class from templates.
P.S. I had a colleague that had to reinstall visual studio 2005 due to a dodgey build (I can’t remember the number of hand but it was a few weeks ago Note: 799 has been ok for me)
R#v4 Nightly Builds: (in case any stray readers are interested) www.jetbrains.net/.../ReSharper+4.0+Nightly+Builds
I got this issue after upgrading my version; It was working for other team members but not me. I was able to fix this issue by running Clean Solution within Visual Studio, then rebuild all. That seemed to fix my issue.
Id say it is a service pack Because these are Items that should have been with 3.5 to begin with but were not ready?
Damien,
My name is Tom Fuller and I work for Microsoft on the WCF support team. I just worked through this issue with another customer and we found that you do *not* need to make the web application project as updateable to get WCF services to work. The only tricky part is keeping the application project name and virtual directory name in sync. If you don't you'll need to fix the customString node in the .compile file. I have written up some instructions at forums.microsoft.com/.../ShowPost.aspx
Thanks, this was really helpful.
~Paras
Thanks you just saved me a lot of time!
void main() { printf("Hello Kidoos World"); return 0; } Syntax Highlighting started working
I solved the problem by copying the nunit.framework.dll into the debug folder and ran the tests successfully. Thanks Shehzad and Everyone.
To fix Enum problem you need to fully specify enum values e.g.
enum Test
{ Code1, Code2} - doesn't work
{Code1=1,Code2=2} - works