New answers tagged

3

In my opinion this is a No-No. There are plenty reasons but from the top of my head, it violates the separation of concerns rule. Resx files are for storing your resources, which are static assets, used mostly for localization/internationalization and have nothing to do with your application's flow; while configuration has a significant impact to how your ...


-2

Put it on the server. It's faster to write and more secure


2

Is it significantly easier, faster, better for testing and management, etc. to write the code in C# on the server than in JS on the client? It depends entirely on your Developmental ecosystem. If you write and test lots of JavaScript code, then there might be some gain in doing so. If, however, you spend all your time cutting server-side, C# code and ...


3

From my painful experience, the more of deployment process is being done manually, the bigger trouble you'll get into. And both your current steps require heavy manual effort. Here are my recommendations: 1. Use VS Publish functionality as your bare minimum First step toward having automated deployment process is, as you are aware of, using Publish ...


0

I think you're going down the right path. I'm not sure I'd use nullable/optional fields though. In my mind, NULL means "unknown", not "ANY". Using your example data you could create a table DocID Org Dept Posn 1 X 1 any 1 X 1 A // redundant, due to the record above 1 X any A 1 ...


0

WEB Api requests are Stateless & Synchronous. that means they don't maintain an open connection/state and will timeout after a while. When your API sends a message to the windows service and then subscribe to events coming back, it will be subject to the how long the HTTP connection will be held open by the API client. I can think of some better ...



Top 50 recent answers are included