|
Apr
16 |
|
asked | REST architecture using and organising DTO's |
|
Mar
4 |
|
awarded | Popular Question |
|
Feb
21 |
|
comment |
MVC 4 Web Api Extend ApiController That fixed it! I wouldn't have thought it would have matched on the method though as the signature did not conform to the Get/Post/Put/Delete etc. |
|
Feb
21 |
|
accepted | MVC 4 Web Api Extend ApiController |
|
Feb
21 |
|
comment |
MVC 4 Web Api Extend ApiController No, this is a fresh project and I only have 1 controller so far (besides the ExtendedController). I'm wondering if because the inheritance chain is 3 levels deep that it might be the cause, some internal reflection thats been tripped up. |
|
Feb
21 |
|
asked | MVC 4 Web Api Extend ApiController |
|
Feb
13 |
|
awarded | Popular Question |
|
Feb
12 |
|
comment |
Provide limited API externally as DLL This is what I mean though, we'll basically have to create a 3rd dll with a copy of the code that we want to distribute and containing nothing that don't want to distribute. Effectively meaning we'll have duplicate code :s Not sure how I feel about that. |
|
Feb
12 |
|
comment |
Provide limited API externally as DLL Yes but we can live with them decompiling the limited functionality we want to provide, but if they could decompile the full library then that's another matter. A more granular codebase would probably be a better solution I guess. |
|
Feb
12 |
|
comment |
Provide limited API externally as DLL The issue surrounds more if someone took the core dll and decompiled it. I suppose it will just need to be a copy of the functionality that we're providing. |
|
Feb
12 |
|
comment |
Provide limited API externally as DLL Yes, basically we need to provide a subset of functionality externally without exposing any core mechanisms. Even if we could somehow "merge" the core dll into a wrapper it could still be decompiled. |
|
Feb
12 |
|
comment |
Provide limited API externally as DLL Does this require the original core library to have been built with this in mind? |
|
Feb
12 |
|
comment |
Provide limited API externally as DLL This would require you to include the core DLL in the files you pass across or .Net would throw a not found exception. |
|
Feb
12 |
|
asked | Provide limited API externally as DLL |
|
Jan
28 |
|
comment |
Generic collection mapping using reflection I don't need catch all functionality I just need something to cover most instances. So if IEnumerable<T>, ICollection<T> or IList<T> are passed then I can just return a list. What I am trying to cater to is the potential for custom collections but all I want to enforce is that thet at some stage implement IEnumerable. I could take that a level up to be ICollection. |
|
Jan
28 |
|
comment |
Generic collection mapping using reflection @poke The latter, I want to take an empty IEnumerable and populate it with more values. Realistically speaking you'd pass the Type that is IEnumerable and I'll create a populated instance of it with the values. |
|
Jan
28 |
|
asked | Generic collection mapping using reflection |
|
Jan
14 |
|
comment |
Map flattened strings to list I'm looking to create a simple layer of action focused DTO's that map to model objects. For the most part the mappings will be simple enough so what is the best practice regarding writing resolvers, would it be applicable to my problem or would I use it for a more complicated mapping? |
|
Jan
14 |
|
accepted | Map flattened strings to list |
|
Jan
14 |
|
comment |
Map flattened strings to list Thank you very much! Will accept your answer in 5 mins when it lets me. |
