Comments
Sort by recent activity
I have over 42000 samap files, of which I only need a couple hundred. With that amount of files, any manual search and delete won't work in any reasonable amount of time.
So please add me to the list of people who could really use such a tool! / comments
I have over 42000 samap files, of which I only need a couple hundred. With that amount of files, any manual search and delete won't work in any reasonable amount of time.
So please add me to the li...
After lots of updating and testing, I finally figured out the problem: The .NET 2.0 assembly used a different key to sign the assembly, so the MandatoryPath doesn't work.
With the following change I get it to compile: <Assembly AssemblyName="mscorlib, Culture=neutral, PublicKeyToken=b77a5c561934e089" MandatoryPath="C:\Windows\Microsoft.Net\assembly\GAC_32\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll" />
<Assembly AssemblyName="mscorlib, Culture=neutral, PublicKeyToken=7cec85d7bea7798e" MandatoryPath="C:\Windows\Microsoft.Net\assembly\GAC_32\mscorlib\v4.0_4.0.0.0__b77a5c561934e089\mscorlib.dll" />
However, I now get the following warning:
One or more of the merged assemblies uses internal members of unmerged assemblies via InternalsVisibleToAttribute. Your assembly may not work.
However, so far I have not noticed any problems. / comments
After lots of updating and testing, I finally figured out the problem: The .NET 2.0 assembly used a different key to sign the assembly, so the MandatoryPath doesn't work.
With the following change ...
If you are doing your own handling: There is a method SetProxy() on the UnhandledExceptionHandler. / comments
If you are doing your own handling: There is a method SetProxy() on the UnhandledExceptionHandler.
I did a bit of disassembly. When error reporting is added to an assembly, SA does two things:
The code of all methods, constructors and properties is wrapped in a try-catch, which allows getting the local values of variables.
The error handling template code is added.
The error template code is only used in two cases: If the assembly is an application, and if the assembly manually passes an exception to SmartAssembly, using SmartAssembly.ReportException.ExceptionReporting.Report(). So if you have a DLL, and it doesn't manually pass an exception to SA, the code is AFAICT unnecessary.
This (useless) code may or may not result in much bloat of your assembly, since it is fixed in size. On the other hand, since every bit of code you have is wrapped in a try-catch, this will definitely bloat the code, especially if you have many small methods and simple properties. / comments
I did a bit of disassembly. When error reporting is added to an assembly, SA does two things:
The code of all methods, constructors and properties is wrapped in a try-catch, which allows getting t...
williamw wrote:
In your SmartAssembly projects I assume you only turned on usage reporting for that one assembly, and not for the ones that are calling it to do reporting?
Exactly. I have two different SA project files. One has usage and crash reporting on (which I use for only that "core" assembly) and the other one has only crash reporting on (which I use for everything else). / comments
williamw wrote:
In your SmartAssembly projects I assume you only turned on usage reporting for that one assembly, and not for the ones that are calling it to do reporting?
Exactly. I have two ...
I have the same issue in my application.
When applying feature usage reporting to the different assemblies, this results in each assembly being considered a different "version", even if the have the same application name. So even if they belong to the same application, you will see the feature reports being split up. Depending on how you handle asking the user for consent, this can also result in a prompt for each assembly.
The way I solved it was by having a method to report usage in an assembly known by all assemblies, which is wrapper over the actual call to usage reporting. That way, there is only one assembly which gets feature reporting compiled into it, and thus all feature reports for the application appear together. / comments
I have the same issue in my application.
When applying feature usage reporting to the different assemblies, this results in each assembly being considered a different "version", even if the have th...
See http://www.red-gate.com/supportcenter/C ... ommandLine
Use
smartassembly.com /downloadnewreports
(make sure you call smartassembly.com and not smartassembly.exe). / comments
See http://www.red-gate.com/supportcenter/C ... ommandLine
Use
smartassembly.com /downloadnewreports
(make sure you call smartassembly.com and not smartassembly.exe).
Is the original project output strong-name signed? / comments
Is the original project output strong-name signed?
You could reference an assembly that has been processed by smartassembly and let that assembly report the error for you. / comments
You could reference an assembly that has been processed by smartassembly and let that assembly report the error for you.