Activity overview
Latest activity by JDHnz
Hi James,
yes, that is correct. We are already running our own custom web server as you have suggested. Unfortunately, both the error and feature usage reports are saved as encrypted reports on the web server before they are downloaded by the SA client, so there doesn't seem to be a way for me to write my own addition to the web service to find out how many error reports there are waiting to be downloaded.
Most of the code in behind the custom web server is obfuscated of course, so it's not much help in working out what I need to call to get the information I need. I can see that there is a GetReportCount() web method on the ReportingService class behind the Reporting.asmx web service file, but it looks like it is checking details of an established session, which makes me suspect that a call to the SecuredLogin() web method on the same class is required, but that requires licenseID and password parameters for which I don't know the necessary values. / comments
Hi James,
yes, that is correct. We are already running our own custom web server as you have suggested. Unfortunately, both the error and feature usage reports are saved as encrypted reports on the...
Yes, the SDK is where I found how to retrieve new reports by invoking "SmartAssembly.com /downloadnewreports" (see the DownloadNewReportsClick() event handler in the Database SDK sample).
I could write my own web service to check for the presence of files in the configured ReportsFolder, but as they are encrypted reports I can't differentiate the exception reports from the feature usage reports, so I couldn't get a count of only the exception reports waiting on the server.
Is there really no other way of finding out if there are error reports waiting to be downloaded from the web service? / comments
Yes, the SDK is where I found how to retrieve new reports by invoking "SmartAssembly.com /downloadnewreports" (see the DownloadNewReportsClick() event handler in the Database SDK sample).
I could w...
Querying SmartAssembly web service
Hi there,
We're putting the finishing touches on our winforms application as we get ready to release it, and I was wanting to have a little system tray app for myself that notified me when there we...
[bump] Anything? / comments
[bump] Anything?
Has any progress been made on getting SA to cope with this scenario? / comments
Has any progress been made on getting SA to cope with this scenario?
I have created a minimal project that reproduces the problem I have encountered. It can be downloaded from here.
You will notice that a click on the Throw Exception button on the "Splash" form, the first time it is opened, results in the standard SmartAssembly error window popping up, but a click on the Throw Exception menu item in the MDI or a click on the Throw Exception button on the Splash window after logging in and back out again, results in the default Windows Forms exception window. / comments
I have created a minimal project that reproduces the problem I have encountered. It can be downloaded from here.
You will notice that a click on the Throw Exception button on the "Splash" form, the...
james.davies wrote:
Or it could be related to multiple app domains. Are you using multiple app domains?
While I'm fairly certain that we're not using multiple app domains, we might be doing something a little different with the message loop from the standard Winforms app, by having multiple calls to System.Windows.Forms.Application.Run() for when we have different forms as the main window of the app at different stages.
Our app runs something like this:
Sub Main
fSplash = New frmSplash
fSplash.Show()
' program initialisation code goes here (open DB connection, etc.)
System.Windows.Forms.Application.Run(fSplash)
Do While fSplash.IsLoggedIn
fSplash = Nothing
fMDI = New frmMDI
System.Windows.Forms.Application.Run(fMDI)
If fMDI.IsExitingApp Then Exit Do
fMDI = Nothing
fSplash = New frmSplash
fSplash.Show()
System.Windows.Forms.Application.Run(fSplash)
Loop
End Sub
My experiments showed that any exceptions thrown before the call to System.Windows.Forms.Application.Run(fMDI) would be caught by the SA UnhandledException handler, but after that they would be dealt with by the default Winforms handler. / comments
james.davies wrote:
Or it could be related to multiple app domains. Are you using multiple app domains?
While I'm fairly certain that we're not using multiple app domains, we might be doing so...
james.davies wrote:
Hi,
Here are some ideas:
It could be a clash between your error handling code and the error handling code inserted by SmartAssembly. Is your code still implementing an unhandled exception handler ?
We did have a very basic one in the earlier stages of the migration, as a placeholder for when we were still considering doing our own error reporting system, but this has all been removed from the project now.
Or it could be related to multiple app domains. Are you using multiple app domains?
Not intentionally. Is there anything in the .NET framework classes used to support code migrated from VB6 that could be doing so behind the scenes?
Can you throw some simple exceptions elsewhere in your code ? Are any of these reported correctly ?
I just added one right at the beginning of the Main() method and it was handled correctly. I will try adding more around the area where it is not reporting them correctly to see if that provides any more clues as to what is going awry.
Is it possible you are using a build script which uses an older saproj that does not have error reporting turned on.
No, we're not using a build script yet. I'm still using the tools interactively at this stage. / comments
james.davies wrote:
Hi,
Here are some ideas:
It could be a clash between your error handling code and the error handling code inserted by SmartAssembly. Is your code still implementing an unh...
unhandled exception not caught by SA
Today is my first day at trying out using Smart Assembly, so I could potentially be doing something really silly, but if I am then I can't see it.
I have spent the past 30 months migrating our big ...
Can't say I agree with your analysis. In both of the cases, (1) where it is a new table also defined in the script, or (2) an existing table in the database, then the tables appear in the candidate lists where appropriate (with the new table identified using a "SQL" icon), but not for column lists. Refreshing the cache didn't help. The list of column candidates appears when expected for an INSERT or SELECT statement, but not for the ALTER TABLE or CREATE INDEX statements. / comments
Can't say I agree with your analysis. In both of the cases, (1) where it is a new table also defined in the script, or (2) an existing table in the database, then the tables appear in the candidat...