Comments
Sort by recent activity
Hi,
I gather that my colleague James has already sent you this answer by email, but for the benefit of anyone else who wants to know:
These instructions assume that you are using an .mdb file to store reports.
Before you start, please note that modifying the SmartAssembly database.mdb file is unsupported. We recommend that you just use the Filter by project and Filter by build filters to ignore test usage reports, instead of following the procedure below.
1. Open %ProgramData%\Red Gate\SmartAssembly\database.mdb in Microsoft Access.
(If you are using Windows XP, open %ProgramFiles%\Red Gate\SmartAssembly 6\database.mdb)
2. When prompted for the password, enter 7f465a1c156d4d57
3. Delete all of the rows in the FeatureReports table. / comments
Hi,
I gather that my colleague James has already sent you this answer by email, but for the benefit of anyone else who wants to know:
These instructions assume that you are using an .mdb file to st...
Hi Al,
I can confirm that this is intentional. We started hashing the host IP address in SmartAssembly 6, which introduced Feature Usage Reporting.
We hash the host IP address to help protect the privacy of your users: it makes it difficult to link a user's feature usage reports to an error report, which might contain the user's email address, for example.
To achieve this, Automated Error Reporting and Feature Usage Reporting use different salts when creating the hash.
If your users have static IP addresses, which you know, you can calculate the hash of their IP address. This should help you discover where error reports have come from. The SDK in SmartAssembly Professional contains a DLL called SmartAssembly.SDK.dll. One of the Helpers in that DLL is the method HashAddress(str ipAddr, bool featureReporting). So, to determine the hash of the IP address 123.123.123.123 used in Error Reports, call: HashAddress("123.123.123.123", false);
Naturally, we do not provide a method for reversing the hash, and the algorithm used is deliberately designed to take a long time to reverse.
Dom. / comments
Hi Al,
I can confirm that this is intentional. We started hashing the host IP address in SmartAssembly 6, which introduced Feature Usage Reporting.
We hash the host IP address to help protect the p...
It's probably worth adding that we do keep documentation for older versions of our products online, too.
For SmartAssembly, see http://www.red-gate.com/supportcenter/Content?p=SmartAssembly&c=SmartAssembly/old_help.htm.
For other products, go to the documentation for the current version, then click 'Topics for other versions of product'. / comments
It's probably worth adding that we do keep documentation for older versions of our products online, too.
For SmartAssembly, see http://www.red-gate.com/supportcenter/Content?p=SmartAssembly&c=Smart...
This happens with Internet Explorer 6, because IE6 does not support two features used in the HTML export.
Images are not displayed, because IE6 does not support base64-encoded inline images. There is no workaround for this.
The tree will not expand, because IE 6 does not support the 'table-row' value of the display property, which is used in the JavaScript.
There is a workaround for this: In the HTML file's source, replace all occurrences oftable-row with block. You will now be able to expand the tree by clicking on the red crosses. / comments
This happens with Internet Explorer 6, because IE6 does not support two features used in the HTML export.
Images are not displayed, because IE6 does not support base64-encoded inline images. There ...
Hi Alexandru,
I am currently in the process of rewriting this part of the documentation. Sorry it is a bit unclear at present.
Silverlight applications can either be in-browser, or out-of-browser. You choose which type of Silverlight application you want to build in the Visual Studio project.
The settings you enter in ANTS Performance Profiler depend on the type of Silverlight application that you are profiling.
If your Silverlight 4 application is a Silverlight out-of-browser application, you are correct:
(1) For the Silverlight application URL, enter the file path to the XAP file.
(2) Your Silverlight application launches inside sllauncher.exe (the out-of-browser launcher) automatically. You do not need to run sllauncher.exe separately.
This will not work if your Silverlight application is an in-browser application.
If your Silverlight 4 application is a Silverlight in-browser application, you need the Silverlight plugin in Internet Explorer. To profile the application:
(1) Close all running instances of Internet Explorer.
(2) For the Silverlight application URL, enter either:
* the file path to the HTML page that embeds the Silverlight application or
* the localhost URL of the HTML or ASPX page that embeds the Silverlight application (eg: http://localhost/test/test.aspx)
(3) Internet Explorer starts and loads your Silverlight application automatically.
This will not work if your application is a Silverlight out-of-browser application.
From your post, it sounds like your application has been built as a Silverlight out-of-browser application. If so, to profile it by specifying the address on the server, you need to rebuild it as a Silverlight in-browser application first.
I hope this helps,
Dom. / comments
Hi Alexandru,
I am currently in the process of rewriting this part of the documentation. Sorry it is a bit unclear at present.
Silverlight applications can either be in-browser, or out-of-browser. ...
Hi,
The instructions for integrating SmartAssembly with MSBuild are at http://www.red-gate.com/supportcenter/C ... 210451.htm / comments
Hi,
The instructions for integrating SmartAssembly with MSBuild are at http://www.red-gate.com/supportcenter/C ... 210451.htm
Hi,
By default, SmartAssembly uses Windows authentication to connect to the database. Using SQL Server Management Studio, check that the user account under which SmartAssembly runs can connect to the SmartAssembly database on the SQL server.
If you need to use SQL authentication to connect to the database, instructions are at http://www.red-gate.com/supportcenter/C ... 210448.htm / comments
Hi,
By default, SmartAssembly uses Windows authentication to connect to the database. Using SQL Server Management Studio, check that the user account under which SmartAssembly runs can connect to t...
Hi,
To use command line profiling, you need to use Profile.exe, not RedGate.Profiler.UI.exe / comments
Hi,
To use command line profiling, you need to use Profile.exe, not RedGate.Profiler.UI.exe
Hi Richard,
You are correct in saying that you have to run the profiler while you take the snapshots. You might be able to reduce the profiler's overhead slightly by turning off the 'monitor disposal of objects' option while profiling, however, and by recording as few performance counters as possible.
On your other question, you can take the snapshots and then analyze the data later. When you have finished profiling your application, in ANTS Memory Profiler, go to the File menu and click Save Profiler Results... You can then use the Open Profiler Results... menu option to open the results later, when your application is not running.
Hope that helps, / comments
Hi Richard,
You are correct in saying that you have to run the profiler while you take the snapshots. You might be able to reduce the profiler's overhead slightly by turning off the 'monitor dispo...
In case anyone else is having problems when using the TakeSnapshot() method, I have put a PDF containing the draft help for this feature at http://downloads.red-gate.com/HelpPDF/ANTS_Memory_Profiler/AMP7EAP_TakeSnapshot.pdf / comments
In case anyone else is having problems when using the TakeSnapshot() method, I have put a PDF containing the draft help for this feature at http://downloads.red-gate.com/HelpPDF/ANTS_Memory_Profile...