block.
> Â
> pseudo code:Â Set MyTestResult = Failed. ??
>
> On Tue, Jan 5, 2016 at 10:00 PM, mawa316 . <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=60858&i=0>> wrote:
>
>> Here's the file I spoke of...
>> Â
>> Â
>>
>&
27;s the file I spoke of...
>
>
>
> On Tue, Jan 5, 2016 at 9:01 PM, superfreak3 [via Apache Logging] <
> ml-node+s6191n60848...@n7.nabble.com> wrote:
>
>> I noticed something strange that has happened since adding logging with
>> log4Net. When exceptions occur,
Here's the file I spoke of...
On Tue, Jan 5, 2016 at 9:01 PM, superfreak3 [via Apache Logging] <
ml-node+s6191n60848...@n7.nabble.com> wrote:
> I noticed something strange that has happened since adding logging with
> log4Net. When exceptions occur, they are caught and writ
I noticed something strange that has happened since adding logging with
log4Net. When exceptions occur, they are caught and written as desired to
the log. However, running via both mstest and Visual Studio 2015, despite
the fact exceptions occur, the tests are still seen as successful.
I verifie
I was able to get everything to work by changing the Copy to Output Directory
property to Copy always. Once the app.config file was actually present, the
log was created and updated as hoped.
Now if I can only get the Microsoft Test Tools unit test exception for my
web app tests, I'll be all set,
