Comments
Sort by recent activity
The CryptoLicensing assembly is invalid. It has two Assembly metadata items.
The next EAP will read the first Assembly metadata item instead of the second, the same as the CLR does. This means that you can process your assembly. / comments
The CryptoLicensing assembly is invalid. It has two Assembly metadata items.
The next EAP will read the first Assembly metadata item instead of the second, the same as the CLR does. This means that...
Yes, it sounds like SA might be finding the wrong version of your assembly.
Try the latest EAP of SA 5.5, there have been lots of improvements in this area. http://www.red-gate.com/MessageBoard/vi ... .php?f=116
If not, you can force which assembly to use using MandatoryPath. Details are here: http://www.red-gate.com/supportcenter/C ... 032210.htm / comments
Yes, it sounds like SA might be finding the wrong version of your assembly.
Try the latest EAP of SA 5.5, there have been lots of improvements in this area.http://www.red-gate.com/MessageBoard/vi ....
When the map file is missing, SA should place the .saencryptedreport file somewhere on your computer in case you want it again.
In windows xp/2003 it puts it in program files, in SmartAssembly's folder.
In windows vista and above, it puts in in ProgramData, again in SmartAssembly's folder.
You can just double click these (on a machine which does have the appropriate map file) to open them. / comments
When the map file is missing, SA should place the .saencryptedreport file somewhere on your computer in case you want it again.
In windows xp/2003 it puts it in program files, in SmartAssembly's fo...
Is the inner try-catch block there in the original source code?
The outer one is applied to all methods (it isn't worth checking for cases like this where it has no effect) to capture variables for the error reporting. / comments
Is the inner try-catch block there in the original source code?
The outer one is applied to all methods (it isn't worth checking for cases like this where it has no effect) to capture variables for...
Hi Marco,
You're right, that is a bad bug that we noticed soon after releasing version 5.1.
It's fixed in the early access builds of 5.2 here: http://www.red-gate.com/MessageBoard/vi ... .php?f=116
Or alternatively, you can work around it by referencing the ReportException dll found in the SDK folder in Program Files.
Apologies for that / comments
Hi Marco,
You're right, that is a bad bug that we noticed soon after releasing version 5.1.
It's fixed in the early access builds of 5.2 here:http://www.red-gate.com/MessageBoard/vi ... .php?f=116
...
We've deliberately kept the add-in installation per-user to avoid needing admin access to the machine.
You should be able to install the add-in per-machine instead. Do this by moving the .addin file to:
%ALLUSERSPROFILE%\Application Data\Microsoft\MSEnvShared\Addins
I don't know how multiple versions of Visual Studio will deal with that though.
Hope that helps, / comments
We've deliberately kept the add-in installation per-user to avoid needing admin access to the machine.
You should be able to install the add-in per-machine instead. Do this by moving the .addin fil...
You should only use the regenerated version of assemblies while you need to debug them. Once you've finished debugging, go back to using the normal versions.
Having said that, I have no idea why they would be slower. / comments
You should only use the regenerated version of assemblies while you need to debug them. Once you've finished debugging, go back to using the normal versions.
Having said that, I have no idea why th...
The way to do this is using a separate SA project for each assembly. / comments
The way to do this is using a separate SA project for each assembly.
Yes, that's what I meant when I said:
"It usually works if you set R# to open the Object Browser when you press F12."
Thanks for the extra details how to do that, I'd forgotten. / comments
Yes, that's what I meant when I said:
"It usually works if you set R# to open the Object Browser when you press F12."
Thanks for the extra details how to do that, I'd forgotten.
It's not really either of our fault, I've been working with the guys at JetBrains. The trouble is that the only way it was feasible to add this feature in Reflector is by piggybacking on VS's go to definition (F12) feature. Without doing that, we would have to implement a complete parser for the language.
Of course R# does implement a parser, and extends the go to definition in ways the Reflector add-in can't deal with.
It usually works if you set R# to open the Object Browser when you press F12. / comments
It's not really either of our fault, I've been working with the guys at JetBrains. The trouble is that the only way it was feasible to add this feature in Reflector is by piggybacking on VS's go to...