Tag Info

New answers tagged

2

As you've found out, code works fine regardless of which file you put it in. So it comes down to organization... where will you put things? What I've found is that any departure from the "standard" conventions makes it very difficult to navigate through a code base of any significant size. You say you have this little helper class, but where the hell is ...


1

In general, the idea of one Class or Module per file is something I first noticed in Java (I believe it is/was a requirement there). C# has continued this as a suggestion, and VB.NET probably now has the same suggestion somewhere. However, as the VB.NET designers decided you can only have extension methods in Modules, you've provided an example where it ...


1

I have integrated with a team that used a pure desktop application with the server meaning the "database" - for them it made complete sense to have a client side log because that is where all the code was executed. There was no other way to debug an issue if it ever occurred. In terms of "what" to log - it is subjective and based pure on what you will need ...


0

Every code which is complicated enough that it won't be straigtforward to debug should create logs. The fact that it's running on client side is irrelevant. You can skip logging if: You are not expecting to support the application, that is you are developing a prototype or abandonware. The logic is extremely simple and consists of 1:1 mapping of server ...


1

Dealing with COM onjects is almost the canonical reason for setting Option Strict to off, or using the C# equivalent dynamic. Late binding means that you loose the help of the compiler in getting things right, if you are fighting the compiler more than it is helping you, it is quite reasonable to just say "I know what I am doing". I would recommend ...


0

My apologies but a muse came along and I have an answer to my own question which I wanted to post here in case it helps someone else. However, if you have any other ideas of how to do this then please share. Updated Code: Dim TransactionItems As New DataSet TransactionItems.ReadXml(TransactionID) ' still passed into this code by user selection ...


1

In the distant past, I would have suggested using the registry (as opposed to an INI file). These days, I would lean toward file-based storage of settings and configuration. The user-changeable parts of the settings should be persisted using the Isolated Storage API.


4

A good starting point is Jeff Atwood's article: Was The Windows Registry a Good Idea? It gives a lot of good reasons not to use the registry. Among them: The registry is a single point of failure. That's why every single registry editing tip you'll ever find starts with a big fat screaming disclaimer about how you can break your computer with ...


2

I would suggest that the Windows Registry is best left to Windows itself to play with. Parts of it are inaccessible to regular users. Parts of it are inaccessible to certain types of application (32-bit processes running on 64-bit versions of Windows). It's a completely proprietary storage mechanism, which can change, without warning, with any upgrade ...



Top 50 recent answers are included