Comparing the assembly name resulted in the mismatch: Revision Number

[Stephan]

I'm currently trying to update my addin for v2.5.2. When I load it
into the addin directory I get the above error (after setting the
trace-switch to 4 and enabling the fusion log).

On the other hand, if I recompile NUnit from the source and run that,
I have no problems.

Any suggestions?

Thanks
Stephan

[Charlie Poole]

Hi Stephan,

That's odd, as it would suggest the NUnit assembly you originally
built your addin against was not available at runtime. Is it
possible you used a different version and only corrected it
at the time you built from source?

Charlie

> --
>
> You received this message because you are subscribed to the
> Google Groups "NUnit-Discuss" group.
> To post to this group, send email to nunit-...@googlegroups.com.
> To unsubscribe from this group, send email to
> nunit-discus...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/nunit-discuss?hl=en.
>
>
>

[Stephan]

Unfortunately not.I installed 2.5.2 from the MSI and then compiled my
addin. It didn't load.
Then I compiled 2.5.2 and added the Addin directory where the binaries
are. That loads the addin alright.

Here is what I see:
20:16:07.705 Debug [ 1] ServiceManager: Request for service
IAddinRegistry satisfied by AddinRegistry
20:16:07.705 Debug [ 1] AddinManager: Loaded
CookComputing.XmlRpcV2.dll
20:16:07.720 Debug [ 1] AddinManager: Loaded TestLinkAPI.dll
20:16:07.720 Debug [ 1] AddinManager: Loaded TestLinkFixture.dll
20:16:07.736 Debug [ 1] AddinManager: Loaded TlNUnitAddOn.dll
20:16:07.736 Error [ 1] AddinManager: Failed to loadE:\Program Files
\NUnit 2.5.2\bin\net-2.0\addins\TlNUnitAddOn.dll
System.IO.FileLoadException: Could not load file or assembly
'nunit.core.interfaces, Version=2.5.2.0, Culture=neutral,
PublicKeyToken=96d09a1eb7f44a77' or one of its dependencies. The
located assembly's manifest definition does not match the assembly
reference. (Exception from HRESULT: 0x80131040)
File name: 'nunit.core.interfaces, Version=2.5.2.0, Culture=neutral,
PublicKeyToken=96d09a1eb7f44a77'
at System.Reflection.Assembly._GetExportedTypes()
at System.Reflection.Assembly.GetExportedTypes()
at NUnit.Util.AddinManager.Register(String path)

-------
Could it be something to do with the GAC?

[Stephan]

Problem solved. Here's what happened.
When I set up the project my addin has to link to NUnit .Core and
Nunit.Core.Interfaces.
When I went in VS to add them I didn't see them in the .NET tab where
only Nunit.Framework shows up. So I did a browse and inadvertently
linked to the dlls that I had compiled from the source, instead of the
MSI installed ones under Program Files\Nunit\Bin\lib

The 'official' ones (from the MSI) have a version of 2.5.2.9222. The
ones I compiled had the version of 2.5.2. So when loading the addin
it looked for the dependencies and found the 2.5.2.9222 in the lib
directory. The loader saw that the ones it tried to load had a higher
version than the ones I compiled against and aborted the load.

That's what you get when you work late at night. At least I can now
put up my newest version of the testlink adapter for Nunit.

[Charlie Poole]

Glad you came up with a solution. Life will be easier when addins
no longer need to link to core.

Charlie

> -----Original Message-----
> From: Stephan [mailto:steph...@gmail.com]
> Sent: Wednesday, November 25, 2009 1:36 AM
> To: NUnit-Discuss
> Subject: [nunit-discuss] Re: Comparing the assembly name
> resulted in the mismatch: Revision Number
>

[Stephan]

Is there a plan to that? What shape would that take?

> >http://groups.google.com/group/nunit-discuss?hl=en.- Hide quoted text -
>
> - Show quoted text -

[Charlie Poole]

http://nunit.org/wiki/doku.php?id=dev:specs:framework_boundary_change

[Adam Connelly]

Charlie,

How far along are you in the development - it's just I've generally found it quite difficult to find out information about what the current architecture (of the 3.0 code) is. Maybe I'm just not looking hard enough. Specifically, how far are you with the test runner that other third party tools can use?

Also, I realise I'm hijacking this thread here, but I'm interested in doing some development for NUnit - what should I do? I tried to send a question about this to the list, but for whatever reason I don't think it arrived :(.

Cheers,
Adam

2009/11/25 Charlie Poole <cha...@nunit.com>

[Charlie Poole]

Hi Adam,

 

The framework is moving along. The runner projects have not yet been set up but I'm

feeling the need to get them going.

 

The existing Vision document (see this group's files area) is a bit out of date but

still useful. There is a lot of design info on the wiki as well. We can handle any

specific questions here.

 

Right now, there's a need for people to help in lots of ways: writing specs, coding,

testing on various platforms, etc. We also need help on some of the infrastructure

for building and installing NUnit. Drop me a line separately or post here with

your interests and we'll try to match you to some tasks.

 

Charlie

 

PS: If you're able to reply but not initiate a new post it probably indicates that

your default email account is not the one google knows about.

---

From: Adam Connelly [mailto:adam.rp...@googlemail.com]
Sent: Monday, November 30, 2009 5:33 AM
To: nunit-...@googlegroups.com
Subject: Re: [nunit-discuss] Re: Comparing the assembly name resulted in the mismatch: Revision Number

[Adam Connelly]

Charlie,

Could it be because my account on google groups is adam.rp...@googlemail.com, whereas when I send emails it comes from adam.rp...@gmail.com (AFAIK)? I know I've had trouble sending stuff to other lists from gmail.

As far as contributing, I'm up for doing more or less anything - although I'd prefer to do some coding rather than helping with specs at least until I understood the architecture and code base better. If you're got any relatively trivial coding tasks lying about I'd be interested in starting there to let me get a feel for how it hangs together. I'm also more than happy to proof read documentation, etc.

Adam

2009/11/30 Charlie Poole <cha...@nunit.com>

[Charlie Poole]

Hi Adam,

 

Could it be because my account on google groups is adam.rp...@googlemail.com, whereas when I send emails it comes from adam.rp...@gmail.com (AFAIK)? I know I've had trouble sending stuff to other lists from gmail.

That could be the cause of the problem. It's similar to one I have on some other groups, where my default email is not known and I have to manually select the proper account before sending - or after it's rejected!

 

Regarding the othe part of your note - about contributing - I'll respond separately. It got me thinking that we need a list of relatively easy things to get started with, which I'm now working on.

 

Charlie

[Charlie Poole]

Hi Adam,

 

Bet you thought I forgot about this question. :-)

 

It hasn't always been easy for people to get started with this project, so I took the opportunity to do a review of all the bugs that are out there and to finish off some partially completed work of my own that was clogging the queue. There will be more later, but for now here are a few ideas to help you get going...

 

You can work on NUnit 2.5, NUnit 3.0 or some related projects. The bug lists for each project are a good place to start:

  NUnit 2.5: http://bugs.launchpad.net/nunitv2

  NUNit 3.0: http://bugs.launchpad.net/nunit-3.0

For a list that covers both of them plus some related projects, see http://bugs.launchpad.net/nunit-xtp

 

Bugs are categorized using tags and you can see a list of those with a particular tag by clicking in the tag cloud on the right hand side of the bug list page.

 

One way to help out that doesn't involve writing any code at all other than tests is to confirm reported bugs. You can find

bugs needing confirmation under the 'confirm' tag. Just duplicate the bug on your system and change the status to confirmed. Ideally, add a comment and paste in your test case. Of course, if you can't confirm it, add a comment to that effect.

 

To work on code, you need to be able to create a local branch using bazaar and build NUnit. See the developer faq on the nunit wiki for info on how to do this: http://nunit.org/wiki/doku.php?id=dev:faq

 

To find easy bugs to get started with, click on the 'easy' tag. You may also want to look at the 'v2port' tag, which marks bugs already fixed in NUnit 2.5 but needing to have the fix ported to 3.0. Most of these are pretty simple, requiring little or no modification to work

in the NUnit 3.0 release.

 

I hope this will give you enough to get started. I'll be adding more potential tasks as time goes on. Feel free to ask for any help you need.

 

Charlie

 

As far as contributing, I'm up for doing more or less anything - although I'd prefer to do some coding rather than helping with specs at least until I understood the architecture and code base better. If you're got any relatively trivial coding tasks lying about I'd be interested in starting there to let me get a feel for how it hangs together. I'm also more than happy to proof read documentation, etc.

 

 Hi Adam,

 

The framework is moving along. The runner projects have not yet been set up but I'm

feeling the need to get them going.

 

The existing Vision document (see this group's files area) is a bit out of date but

still useful. There is a lot of design info on the wiki as well. We can handle any

specific questions here.

 

Right now, there's a need for people to help in lots of ways: writing specs, coding,

testing on various platforms, etc. We also need help on some of the infrastructure

for building and installing NUnit. Drop me a line separately or post here with

your interests and we'll try to match you to some tasks.

[Adam Connelly]

Thanks for the help Charlie.

I've submitted my first change for review. It's porting your fix of bug 419411 to nunit-3.0. I've submitted a branch to launchpad (https://code.launchpad.net/~adam-rpconnelly/nunit-3.0/bug-419411) for review. Hopefully I've done the right thing!

Cheers,

Adam

2009/12/11 Charlie Poole <cha...@nunit.com>

--

[Charlie Poole]

Fantastic! This is a good way to start. I'll review the change shortly.

 

Core-developers: Somebody else should jump in and review stuff as well!

 

Charlie

---

From: nunit-...@googlegroups.com [mailto:nunit-...@googlegroups.com] On Behalf Of Adam Connelly
Sent: Sunday, December 13, 2009 2:46 PM
To: nunit-...@googlegroups.com
Subject: Re: [nunit-discuss] NUnit 3.0 Status was Re: Comparing the assembly name resulted in the mismatch: Revision Number