This question is locked. New answers and comments are not allowed.
This issue is best described in xUnit bug 9696.
The problem lies in the runner setting up the AppDomain without a config file, which causes the System.Uri constructor to throw an exception. A workaround is to include an App.Config file.
The xUnit standalone runner has been updated to fix this issue here.
The problem lies in the runner setting up the AppDomain without a config file, which causes the System.Uri constructor to throw an exception. A workaround is to include an App.Config file.
The xUnit standalone runner has been updated to fix this issue here.
1 Answer, 1 is accepted
0
Hi Stephen,
We've been quite busy with the upcoming release so please excuse us for the late response. Thanks for the detailed explanation of the issue at hand. I looked at how we handle this and it turns out that it's currently working correctly. I did a quick test and creating a new Uri object in xUnit test (or any other framework that JustCode supports) works fine.
If you experience some problem and you are able to easily reproduce it, could you send over a small sample solution demonstrating it?
Thank you in advance for the collaboration.
Regards,
Deyan
the Telerik team
We've been quite busy with the upcoming release so please excuse us for the late response. Thanks for the detailed explanation of the issue at hand. I looked at how we handle this and it turns out that it's currently working correctly. I did a quick test and creating a new Uri object in xUnit test (or any other framework that JustCode supports) works fine.
If you experience some problem and you are able to easily reproduce it, could you send over a small sample solution demonstrating it?
Thank you in advance for the collaboration.
Regards,
Deyan
the Telerik team
Registration for Q1 2011 What’s New Webinar Week is now open. Mark your calendar for the week starting March 21st and book your seat for a walk through all the exciting stuff we ship with the new release!