Tag Info

Hot answers tagged

5

You are both right. You don't want to lose the stack trace, but you may want to catch the lower level exception. Don't wrap the exception if it isn't adding information. I would call your ExceptionManager and TreatException a bit of a code smell - they are trying too hard to centralize exception handling. To re throw without losing the stack trace: ...


3

WPF has fantastic data binding. XAML is a wonderful declarative syntax for describing component layout. WPF/XAML excels at data-driven GUI. I see no technical benefit of using WinForms over WPF/XAML. However WPF/XAML will require a recent version of Visual Studio and a time investment to learn the new API. I strongly recommend writing XAML by hand rather ...


2

You are right, DAL reference should NOT exist in the UI project. You should instead create DTO objects for sending/recieving data to your BLL. It can be a separate project called DTOs or can be included in the BLL by creating specific folders like Customer and placing its facade classes along with the DTOs in that folder. BLL will be responsible for mapping ...


1

This screams out for a Log4Net custom appender. You could write your own, have it check the active item to determine whether to log or not, and log to a per-item memory buffer.


1

Solving this problem is one of those situations where using a data abstraction layer (DAL) in your webservice might help you. In your DAL on the server component, realising that there is a performance issue, you could replace the DAL code which writes directly to the database with one that implements a write cache. That should allow the system to handle ...


1

Looking at MSDN today, one can see that the MSDN documentation page for SortedDictionary<TKey, TValue>, SortedDictionary<TKey, TValue> does implement IReadOnlyDictionary<TKey, TValue>. According to the internet archive, that was not the case on November 14th, 2013. Given that information, it is likely that it was simply an oversight from ...


1

First off, having a catch block which only rethrows the exception is usually useless. But, the only real world scenario i can think of which makes sense to use throw ex instead of throw is if you're developing some sort of third party library which you by all means dont want anyone in the outter scope who's using your code to see the full stacktrace. Im not ...



Only top voted, non community-wiki answers of a minimum length are eligible