Runtime exception when deploying Nopcommerce Website to Azure using Git and Continuous Integration

Hi support, I ran into this error when parsing a deployment to Azure, before embark in debugging, I hope you experienced ones, steer me in the right direction.
Locally test and retest work flawlessly, can successfully deploy via FTP, WebDeploy or Fillezilla, but going the way as the topic title infer, the following exception is thrown:


Server Error in '/' Application.

Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[NullReferenceException: Object reference not set to an instance of an object.]
   Nop.Core.Infrastructure.WebAppTypeFinder..ctor(NopConfig config) 
in c:\a\src\Libraries\Nop.Core\Infrastructure\WebAppTypeFinder.cs:27
   Nop.Core.Infrastructure.NopEngine.RegisterDependencies(NopConfig config) 
in c:\a\src\Libraries\Nop.Core\Infrastructure\NopEngine.cs:55
   Nop.Core.Infrastructure.NopEngine.Initialize(NopConfig config) 
in c:\a\src\Libraries\Nop.Core\Infrastructure\NopEngine.cs:92
   Nop.Core.Infrastructure.EngineContext.Initialize(Boolean forceRecreate) 
in c:\a\src\Libraries\Nop.Core\Infrastructure\EngineContext.cs:50
   Nop.Web.MvcApplication.Application_Start() +25
[HttpException (0x80004005): Object reference not set to an instance of an object.]
   System.Web.HttpApplicationFactory.EnsureAppStartCalledForIntegratedMode(HttpContext context, HttpApplication app) +12600621
   System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +175
   System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +304
   System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +404
   System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +475

[HttpException (0x80004005): Object reference not set to an instance of an object.]
   System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +12617668
   System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +159
   System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +12457285

Thank you
Jose
ehubcap

I dumped configuring the Git versioning with Continuous Delivery via VSO (Visual Studio Online) in favor of going the route of GitHub Remote repository.
The reason behind the switch is the fact that VSO builds and builds definitions are more finicky and seem to dislike compiling NopCommerce and its myriad of plugins, also the metered debugging doesn't inspire friendship to the system, Ok yes, there is "Monaco" that just landed so to speak, but debugging there while circumventing the (pay per compute) is for the pros at the moment.
In conclusion, if you want a version control mechanism that deliver, going thru Git-local-repo => GitHub-remote-repo=>Azure Website(staging) is the easy way