Comment 26 for bug 1064804

NetworkCredential works on challenge, I believe, so please confirm if your
console app has the same code as the test call. Is "Globe" the fully
qualified domain name? I think that it has got to do with
security/authentication/proxyId of your logonAs method.

Jv

On Thu, Oct 11, 2012 at 8:33 AM, Mun Wai Chan
<email address hidden>wrote:

> Yup. I have 3 separate projects in one solution (NUnit, Console and
> MSTest). Below is the source code for NUnit.
>
> using System;
> using System.Net;
> using Microsoft.Dynamics.BusinessConnectorNet;
> using NUnit.Framework;
>
> namespace ClassLibrary1
> {
> [TestFixture]
> public class Class1
> {
> [Test]
> public void Test()
> {
> Axapta ax = new Axapta();
> ax.LogonAs("User1", "Globe", new
> NetworkCredential("User1", "pwd", "Globe"), default(string),
> default(string), "devaos2:2714",
> default(string));
> ax.Logoff();
> }
> }
> }
>
> --
> You received this bug notification because you are a member of NUnit
> Developers, which is subscribed to NUnit V2.
> https://bugs.launchpad.net/bugs/1064804
>
> Title:
> Test throws an exception in NUnit but works when running in MSTest or
> as a Console application
>
> Status in NUnit V2 Test Framework:
> New
>
> Bug description:
> Hi,
>
> I have a simple test which throws an error when I run it using NUnit
> (fails on both NUnit GUI/console and Resharper in VS). However, if ran
> using Visual Studio's Test -> Debug option or as a Console
> application, it runs fine. The code is exactly the same for the 3
> different projects types (NUnit, Console and MSTest).
>
> Source code for NUnit test:
>
> using System.Net;
> using Microsoft.Dynamics.BusinessConnectorNet;
> using Microsoft.VisualStudio.TestTools.UnitTesting;
>
> namespace TestProject1
> {
> [TestClass]
> public class UnitTest1
> {
> [TestMethod]
> public void TestMethod1()
> {
> Axapta ax = new Axapta();
> ax.LogonAs("User1", "Globe", new NetworkCredential("User1",
> "pwd", "Globe"), default(string), default(string),
> "A6BuildTestAos:6004", default(string));
> ax.Logoff();
> }
> }
> }
>
> Error:
>
> FatalExecutionEngineError was detected.
> The runtime has encountered a fatal error. The address of the error was
> at 0x5785ca87, on thread 0x792c. The error code is 0xc0000005. This error
> may be a bug in the CLR or in the unsafe or non-verifiable portions of user
> code. Common sources of this bug include user marshaling errors for
> COM-interop or PInvoke, which may corrupt the stack.
>
> Thanks in advance.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nunitv2/+bug/1064804/+subscriptions
>

--
Regards,

Ravichandran Jv
http://ravichandranjv.blogspot.com