A menagerie of random thoughts and utterings

Logging feature in applications

, posted: 23-Jan-2009 10:41

In the past 6 months or so I have been working on a suite of applications inherited from somebody who has left the company. One of the issues is the fact that numerous assemblies are shared between quite a number of apps. By assemblies I don't mean the VS projects, but the built assemblies themselves. To complicate matters the source projects have gone ahead and changes have been made without careful recording of how they will affect the various dependencies. As a result we no longer have the source for these DLLs as when they were built as release version, without the debugging files. The whole thing is somewhat messy and makes debugging impossible.

This lead me to the subject matter. Should logging be a mandatory feature in every/most/some apps? If so, should it have multiple levels of detail configurable after deployment?

I'm sure these are basic questions that have been discussed long and hard in the software development world and I can probably google for the topic. Interested in what people have to say though...

Crystal Reports nightmare

, posted: 26-May-2006 16:53

Unfortunately I had to create some reports for a kind of Smart Client app. The report was to be deployed and used on several Tablet PCs. I had this bright idea of using "localhost" as datasource so it can be deployed with no extra configuration. That was the beginning of my nightmare...

The development was on VS.NET 2003, using the Crystal component that came standard with the IDE.

For some bizarre reason the report had no problems logging on to the local DB for local admin user. Anybody else (including domain admin) were rejected! Any attempts to provide even the correct credentials were rejected.

In the end I gave up and contacted Crystal folks to see if they could help. It was one of the most frustrating experience I've ever had with a tech support/helpdesk. Admittedly I have had helpful assistance from them before but this time it felt like chasing my own tail.

At last I found the culprit! Using localhost turned out to be a bad idea!! For yet another bizarre reason CR automatically create the connection to use Integrated Security, even when you specify the UserID/Password and left the Integrated Security option unticked. Any attempts to provide the credentials programatically were thoroughly ignored.

I had to create the report by specifying a server name, and later when it's loaded into the viewer I then changed it to "localhost" and pass in the appropriate credentials. That seemed to have done the trick! So there ya go.... hopefully someone will find this useful before they end up tearing their hair out like I almost did.

dpw's profile

Dany Wu
New Zealand