Hi,
I'll need to take a look at this to see if something has cooked in the build cycle, in the mean time build 48 should be ok to use.
I am really snowed under at the moment with the day job so my response times on this will be on the slow side, if anyone else wants to look into this issue (check the proj\sln files etc) then your welcome. The same goes for any bugs\issues you have run into, you more than welcome to submit patches for fixes.
Thanks
Andy
On 4/27/06, MisterD <[EMAIL PROTECTED]> wrote:
Andy, Thanks for the reply. You understand correctly. I already
tried changing the MbUnit.GUI.exe.config file without it making any
difference. The GUI still reports itself as 1.0.2265.31914 (on .Net
2.0.0.0) after making the config file change and it still does not load
my .NET 2.0 assembly.
FYI, Lutz Roeders .NET Reflector reports:
MbUnit.GUI.exe in the v2.3.49 release has a reference to
MbUnit.Framework 1.0.2265.31914.
MbUnit.GUI.exe in the v2.3.23 release has a reference to
MbUnit.Framework 2.3.0.0.
So that would suggest there's a build problem maybe?
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
