New answers tagged

0

Our client is reluctant to allow permissions ... As it their right. You have no mandate to be dictating the security settings that your client "has" to use. ... this has fixed the problem on our test environment Wrong! This has only masked the problem because the problem still exists at your client's site and, let's face it, that's the only ...


1

Well, Think about it this way : "What will happen if I need to use my WS somewhere else ?" From your first implementation I can already tell that you may have to do some copy/paste as time goes on, and you don't want that (DRY Principle). Another advantage to separate the communication is testing and updating. Working with partners is never an easy task ...


1

You have two options. Create seperate mywebsite.api and a mywebsite.app projects in your solution. Advantages Proper seperation of concerns. You can delploy updates to your api and your front end independently. Architecture of sites can be changed independently (i.e. you can update your api to run on asp.net 5 without affecting the website) Cleaner ...


1

It is hard to say from the level of detail you provide, what exactly is the case. When you are saying that has recently been converted from .NET2 to .NET4. this could mean different things: ranging from »The compiler was just a .NET4 compiler and compiled for that target« to »Hey, there are such niceties in terms of Parallel Programming. Let's rewrite ...



Top 50 recent answers are included