Comments
Sort by recent activity
SmartAssembly is designed to deal with this situation when merging. It merges all the satellite dlls for a particular culture into one single satellite dll, in a parallel way to how the main assembly is merged.
Perhaps you are embedding instead of merging? In this case, SA has no effect at all on the satellite dll resolution system, and you need to copy across the satellite dlls of the dependencies to the output folder as if the embedded assemblies were still there. / comments
SmartAssembly is designed to deal with this situation when merging. It merges all the satellite dlls for a particular culture into one single satellite dll, in a parallel way to how the main assem...
Sorry , I was not clear. I am not suggesting that you create a separate SA projects.
SmartAssembly will automatically obfuscate the satellite assemblies of the main assembly / comments
Sorry , I was not clear. I am not suggesting that you create a separate SA projects.
SmartAssembly will automatically obfuscate the satellite assemblies of the main assembly
Satellite Assemblies are not merged or embedded so that they can be loaded at run-time. They should be obfuscated (by SmartAssembly) with the same setting as the main executable. / comments
Satellite Assemblies are not merged or embedded so that they can be loaded at run-time. They should be obfuscated (by SmartAssembly) with the same setting as the main executable.
So you can view the error report from within SmartAssembly but you're not getting the notification email.
Can you please
- double check that the email address is correct ?
- check the spam filter
Also you could try
- using a different email address (say a gmail or yahoo account).
- generating the exception and sending the error from your machine (to ensure it's being sent properly) / comments
So you can view the error report from within SmartAssembly but you're not getting the notification email.
Can you please
- double check that the email address is correct ?
- check the spam filter
A...
Are you are viewing the error reports on the same machine that is building the assembly? If not, can you check that the machine you are viewing from has permission/access to the map files folder.
The problem could be related to the build script itself. Can you try building the assembly using the SmartAssembly GUI ? Do you see the same problem ? / comments
Are you are viewing the error reports on the same machine that is building the assembly? If not, can you check that the machine you are viewing from has permission/access to the map files folder....
Hi,
This is a difficult one , as you seem to be doing everything correctly. Unfortunately logging is not available is the current version of Smart Assembly.
Can you double check that the application you are running is the one you have just built with the build script ? (This problem could be caused by using a shortcut to an old version of the application) / comments
Hi,
This is a difficult one , as you seem to be doing everything correctly. Unfortunately logging is not available is the current version of Smart Assembly.
Can you double check that the applicati...
Hi Adam,
The "Decode Stack Trace" window actually doesn't use the MAP file , so that will be why that works even though Smart Assembly cannot find the MAP file
The Error Reporting Stack Trace decoding does use the MAP file (so I am surprised if the Error report stack trace from Admin looks decoded (perhaps you are looking at some code that was never obfuscated?)
Can you double-check that the MAP files are in the directory that specified in the "Options" section of Smart Assembly (under "Reports Database Options") ?
Can you please also check that the MAP files were created at the time of the latest build ? / comments
Hi Adam,
The "Decode Stack Trace" window actually doesn't use the MAP file , so that will be why that works even though Smart Assembly cannot find the MAP file
The Error Reporting Stack Trace decod...
Sorry, but the email that is sent to you cannot be customised. It is currently hard coded within SA and cannot be changed via the SDK. I will raise this as a feature request with the developers.
regards, / comments
Sorry, but the email that is sent to you cannot be customised. It is currently hard coded within SA and cannot be changed via the SDK. I will raise this as a feature request with the developer...
There is a helpful example of custom error reporting. You should look here:
C:\Program Files\Red Gate\SmartAssembly 6\SDK\Exception Reporting\3 Custom UI / comments
There is a helpful example of custom error reporting. You should look here:
C:\Program Files\Red Gate\SmartAssembly 6\SDK\Exception Reporting\3 Custom UI
You can give your DLLs strong names to prevent confusion.
To view and control dependencies:
Open SmartAssembly.settings using notepad.
You can find this in the program folder or in
c:\programdata\red gate\SmartAssembly
You can add <SearchPath> nodes in the <DependenciesSearchPaths> parent node. / comments
You can give your DLLs strong names to prevent confusion.
To view and control dependencies:
Open SmartAssembly.settings using notepad.
You can find this in the program folder or in
c:\programdata\r...