User profile for Chris.Allen

I have noticed mem leaks in SA too. I've logged a bug for this so, hopefully, it will get looked at. / comments

I have noticed mem leaks in SA too. I've logged a bug for this so, hopefully, it will get looked at.

0 votes

Can you try an EAP version please- we have fixed a few leaks: http://downloads.red-gate.com/EAP/Smart ... 151868.exe / comments

Can you try an EAP version please- we have fixed a few leaks:http://downloads.red-gate.com/EAP/Smart ... 151868.exe

0 votes

This is a little bit difficult to know what has occurred- will need to check several things. Firstly- can you run this within Visual Studio? Profiling tends to work better under webdev than IIS. / comments

This is a little bit difficult to know what has occurred- will need to check several things. Firstly- can you run this within Visual Studio? Profiling tends to work better under webdev than IIS.

0 votes

Would you be able to send us the project? support@red-gate.com (please strip all exes and dlls out before sending). Please quote F43562 in the subject. / comments

Would you be able to send us the project?support@red-gate.com (please strip all exes and dlls out before sending). Please quote F43562 in the subject.

0 votes

This is some general advice about using {smartassembly} with Silverlight. You need to integrate directly the protection in the build process, so you dont have to re-create the .XAP: The DLL stored by Visual Studio in the .XAP will already be obfuscated. When creating your project with the GUI mode of {smartassembly}, the main assembly must be the assembly in the \obj\Release folder, and NOT the one in \bin\Release. The destination assembly can be anywhere as its just for the testing; we will overwrite the assembly in the batch mode. When the project is saved (e.g. in c:\temp\TestSilverlight.{sa}proj), you can either process it through the GUI or from the prompt using {smartassembly}.com, the command line version of {smartassembly}. Then, you can modify the .csproj (or .vbproj) file in order to directly add the protection in the build process. Basically, it: * Adds a reference to the assembly in the GAC (The "UsingTask" node) * Adds a flag in the "BeforeBuild" event to ensure that the Assembly is obfuscated only in Release mode (and not each time an assembly is compiled, which is done very often in the background in VS IDE) * Runs {smartassembly} in the "AfterCompile" to build the project and overwrite the assembly generated by Visual Studio with the one protected by {smartassembly}. If you run the project in Debug mode, nothing happens. If you run the project in Release mode, it will automatically obfuscated the assembly. If you need help on the edition your C# project, you can have a look here: (Its about ClickOnce but its very similar) http://www.smartassembly.com/download/H ... ckOnce.pdf You will need to do it for each DLL in your XAP which you want to protect. You also need to be aware that, as the format for baml files is not public, {smartassembly} cant re-create a new baml containing an obfuscated xaml file and thus need to keep the xaml files unchanged. To ensure that your xaml file will still work with the obfuscated assembly, {smartassembly} will exclude some members from the obfuscation/pruning but, in some cases, you may need to manually exclude other members called by Reflection from the xaml files. This can be done in {smartassembly} project or by using custom attributes directly in your code: http://www.smartassembly.com/download/H ... ibutes.pdf The protected assembly must be signed with the same Strong Name Key (SNK) in {smartassembly} than in Visual Studio, if any. If you want to merge a dependency using WPF with your main assembly, you need to be aware that, if the assembly-qualified name of a type in use in an xaml file, the WPF engine may no longer be able to bind the types from the xaml files with the types in your code (As, obviously, the assembly-qualified name of the types will change after the merging). / comments

This is some general advice about using {smartassembly} with Silverlight. You need to integrate directly the protection in the build process, so you dont have to re-create the .XAP: The DLL stored ...

0 votes

Searching through known issues - this has occurred in the past because of an obfuscated serialized object. / comments

Searching through known issues - this has occurred in the past because of an obfuscated serialized object.

0 votes

Smartassembly exception reporting cannot obtain the stack trace from another process. / comments

Smartassembly exception reporting cannot obtain the stack trace from another process.

0 votes

The problem is very likely that when your app pool runs under ANTS, it no longer has access rights to the database. Can you please ensure that the ANTS service runs as a user with sufficient permissions (i.e. the same as the usual app pool account). / comments

The problem is very likely that when your app pool runs under ANTS, it no longer has access rights to the database. Can you please ensure that the ANTS service runs as a user with sufficient permis...

0 votes

It should be publically available in January (sorry, can't be more specific). The version 5 license won't apply but if you have a current maintenance contact we will create a new code for you. / comments

It should be publically available in January (sorry, can't be more specific). The version 5 license won't apply but if you have a current maintenance contact we will create a new code for you.

0 votes

Thank you for the extra clarification- I am going to have to ask for help from one of our experts- please wait while I do this... / comments

Thank you for the extra clarification- I am going to have to ask for help from one of our experts- please wait while I do this...

0 votes

How can we help you today?

Chris.Allen

Comments