Can't detect the strong name key when assemblies are signed using attributes about resharper-internalsvisibleto HOT 7 CLOSED

Thanks for the report!
I'm actually using ReSharper's infrastructure to look at the public key, they parse it themselves. Looks like ReSharper itself might not support signing via attributes, in which case I will have to do it manually. Either way, that's going to be fixed 👍

from resharper-internalsvisibleto.

Actually thinking about it, these two things could be linked. I hit both problems in the same solution. Once you have the correct assembly name, maybe the signing will just start working?
--Tim

From: Igal Tabachnik [mailto:[email protected]]
Sent: 20 May 2013 16:52
To: hmemcpy/ReSharper.InternalsVisibleTo
Cc: Timothy P. Long
Subject: Re: [ReSharper.InternalsVisibleTo] Can't detect the strong name key when assemblies are signed using attributes (#2)

Thanks for the report!
I'm actually using ReSharper's infrastructure to look at the public key, they parse it themselves. Looks like ReSharper itself might not support signing via attributes, in which case I will have to do it manually. Either way, that's going to be fixed [:+1:]

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-18155022.

ExchangeDefender Message Security: Click below to verify authenticity
http://www.exchangedefender.com/verify.asp?id=r4KG0XZk012732&[email protected]
Complete email hygiene and business continuity solution available from http://www.tigranetworks.co.uk

from resharper-internalsvisibleto.

Well, I'll dig into this later, but now, thanks to you, there's a new cool feature in this plugin :)

(path completion for this attribute)

from resharper-internalsvisibleto.

So it turns out, as far as I can see, that ReSharper will pick the key from the attribute, as long as you build the entire solution first (ReSharper can only detect the public key if the solution has been built either way). So I guess as long as the completion is correct (as noted by Issue #1), this should "just work".

from resharper-internalsvisibleto.

Ah, that makes sense. I’ve had to uninstall R# 8 because it refused to run my unit tests. I don’t suppose your addin works with R#7? Otherwise we’ll have to wait for R#8 release before I can re-test.

--Tim

From: Igal Tabachnik [mailto:[email protected]]
Sent: 20 May 2013 20:30
To: hmemcpy/ReSharper.InternalsVisibleTo
Cc: Timothy P. Long
Subject: Re: [ReSharper.InternalsVisibleTo] Can't detect the strong name key when assemblies are signed using attributes (#2)

So it turns out, as far as I can see, that ReSharper will pick the key from the attribute, as long as you build the entire solution first (ReSharper can only detect the public key if the solution has been built either way). So I guess as long as the completion is correct (as noted by Issue #1#1), this should "just work".

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2#issuecomment-18167278.

ExchangeDefender Message Security: Click below to verify authenticity
http://www.exchangedefender.com/verify.asp?id=r4KJZCW4015088&[email protected]
Complete email hygiene and business continuity solution available from http://www.tigranetworks.co.uk

from resharper-internalsvisibleto.

It does, actually! R#7 doesn't have the NuGet extension manager, unfortunately, so you have to manually install it. The link to the zip file is at the bottom of the readme page: https://github.com/hmemcpy/ReSharper.InternalsVisibleTo

Just extract it somewhere, then run the batch file, it will copy.

I remember there was some issue with ReSharper test runner and VS2012, you needed to install Update 2 for it to work...

from resharper-internalsvisibleto.

I just released the fixed version for both ReSharper 8 (via extensions manager), and ReSharper 7 via the zip file in the readme file. Please let me know if this works!

from resharper-internalsvisibleto.