Thursday 22 October 2015

ASP.NET Tips #37 - Assume .NET problems are your fault, unless you have evidence to the contrary

It's tempting to blame system code, third party libraries, or even the .NET framework itself when there's a problem. But it's almost always the case that your application is misusing other people's code, so make sure you have really good evidence that a problem is elsewhere before blaming someone else.

Besides that, there are some common mistakes that unavoidable:

  1. Create new ASP.NET 4.5 VS project, but still reusing some .NET 2.0 class library (other people's code) which is not fully optimized for .NET 4.5 environment.
  2. Compiled VS project in 32-bit platform, but deploy and execute on 64-bit IIS Server. If you really want to use 32-bit 3rd party component libraries, always remember to set "Enabled 32-Bit Applications" to TRUE in IIS AppPool.
  3. About best practices, always use 64-bit 3rd party components (supported async/await) in any VS Project (Platform: Any CPU) during DEV -> UAT -> PROD stage to achieve great system performance and maximize server resources utilization.

No comments :

Post a Comment