Tag Info

New answers tagged

1

I'm happy to inform you that IncrediBuild actually supports the distribution of .Net projects (both C++ and C#). You'll get this behavior out-of-the-box upon IncrediBuild's installation when building using IncrediBuild's menu under Visual Studio or the command line (make sure you have IncrediBuild's C# solution as part of your license - IncrediBuild's trial ...


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 ...


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 ...


0

You can do WinForms-like development quite easily in WPF. WPF was actually designed to be easy to use for WinForms developers. You don't have to do anything with DataBinding or MVVM, you can have everything in code-behind. Not that I agree with this approach. But if you leverage full power of WPF and do it properly, it will give you tons of productivity ...


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 ...


0

If you are interested in the "magic value" route, yet another way to solve this is to overload the purpose of the Lazy class. Although Lazy is intended to defer instantiation, nothing really prevents you from using like a Maybe or an Option. For instance: public static Lazy<TValue> GetValue<TValue, TKey>( this IDictionary<TKey, ...


0

I think what confuses you about EF is the database context. It allows you to query objects like a Repository and save changes in persistence like a Unit of Work. You have a lot of work done with EF database context. All you have to do is segregate the responsibilities by creating specific repositories and a unit of work that share the database context and ...


0

I generally don't expose my poco objects to the UI layer. Create a wrapper/domain objects layer that will transform the data of Dal layer. This way you can control the data going to the UI layer.


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 ...


0

I wrote an implementation of an enterprise service bus. We have a customer-facing web service API, a web service that drives the web-based user interface, at least a dozen different windows services that run on client machines, a half-dozen services that run on servers, along with three different databases (Couchbase, Elasticsearch, SQL). I made the ...


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 ...


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: ...


-1

Message Transmission Optimization Mechanism (MTOM) is a mechanism for transmitting large binary attachments with SOAP messages as raw bytes, allowing for smaller messages. please refer : http://msdn.microsoft.com/en-us/library/aa395209.aspx for more details.



Top 50 recent answers are included