On 16 Dez., 11:06, Flominator <[email protected]> wrote:
> Until yesterday it threw an exception which I'm currently not able to
> reproduce. It said something like "couldn't find NUnit assembly".
I found it:
[error] Could not resolve the location of an NUnit test assembly.
Location: ....\unitmessung\unitmessungtest\bin\debug
\unitmessungtest.dll
Reference: UnitmessungTest, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=null
Details: Gallio.Reflection.ReflectionWrapperResolveException: Could
not resolve Assembly 'UnitmessungTest, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=null'.
bei Gallio.Reflection.Impl.ReflectorResolveUtils.ResolveAssembly
(IAssemblyInfo assembly, Boolean fallbackOnPartialName, Boolean
throwOnError) in c:\RelEng\Projects\MbUnit v3\Work\src\Gallio\Gallio
\Reflection\Impl\ReflectorResolveUtils.cs:Zeile 68.
bei Gallio.Reflection.Impl.StaticAssemblyWrapper.Resolve(Boolean
throwOnError) in c:\RelEng\Projects\MbUnit v3\Work\src\Gallio\Gallio
\Reflection\Impl\StaticAssemblyWrapper.cs:Zeile 111.
bei Gallio.NUnitAdapter.Model.NUnitTestExplorer.CreateAssemblyTest
(IAssemblyInfo assembly)
[error] Could not resolve the location of an NUnit test assembly.
Location:....\Unitmessung\UnitmessungTest\bin\Debug
\UnitmessungTest.dll
Reference: UnitmessungTest, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=null
Details: Gallio.Reflection.ReflectionWrapperResolveException: Could
not resolve Assembly 'UnitmessungTest, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=null'.
bei Gallio.Reflection.Impl.ReflectorResolveUtils.ResolveAssembly
(IAssemblyInfo assembly, Boolean fallbackOnPartialName, Boolean
throwOnError) in c:\RelEng\Projects\MbUnit v3\Work\src\Gallio\Gallio
\Reflection\Impl\ReflectorResolveUtils.cs:Zeile 68.
bei Gallio.Reflection.Impl.StaticAssemblyWrapper.Resolve(Boolean
throwOnError) in c:\RelEng\Projects\MbUnit v3\Work\src\Gallio\Gallio
\Reflection\Impl\StaticAssemblyWrapper.cs:Zeile 111.
bei Gallio.NUnitAdapter.Model.NUnitTestExplorer.CreateAssemblyTest
(IAssemblyInfo assembly)
I seem to have found the solution, as well: The exception occurs when
the previous build process wasn't successful. Probably the assembly in
the debug directory is deleted/overwritten before VS starts building.
Does it make sense to improve the error message?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"MbUnit.User" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/MbUnitUser?hl=en
-~----------~----~----~----~------~----~------~--~---
