HTTP Error 500.30 - ASP.NET Core app failed to start

Common solutions to this issue:

Troubleshooting steps:

For more guidance on diagnosing and handling these errors, visit Troubleshoot ASP.NET Core on Azure App Service and IIS.

Jan 28, 2016

The 2016 Challenger and Charger SRT Hellcat models, the fastest, most powerful muscle cars to ever run the track*, got their stripes the old-fashioned way: with 650 lb.-ft. of torque. Now they finally get to wear them.
This January dealers began taking orders for SRT Hellcat-exclusive dual full-length carbon-fiber pattern stripes. A little car history for you: Racing stripes made their first appearance in the 1950s. They were primarily used to help spectators identify a particular racecar on the track and to also help the driver orient his ride after a spinout. The stripes fulfilled a third and slightly unexpected role of making cars look completely freaking awesome. Not surprisingly, pretenders and copycats lifted the design element. The British christened them “go-faster stripes.” That’s cute.
While Dodge SRT engineers have confirmed that dual exterior stripes take the aggressive appearance of the 2016 Challenger and 2016 Charger SRT Hellcats up a notch, they credited the 707-horsepower supercharged HEMI® V8 under the hood of these two monsters, and not the stripes, for everything in the speed department. We tend to believe them.
The icing on top of this burnt-rubber cupcake comes in a delicious flavor of Plum Crazy. In response to massive consumer demand, Dodge has extended the deadline for ordering the limited-edition, high-impact Plum Crazy exterior paint color through the end of January.
The SRT Hellcat dual stripes option is available now for a suggested MSRP of $995. When it comes to tricking out your SRT Hellcat in one of the Dodge brand’s most legendary high-impact hues, the clock is ticking.
* Based on NHRA certified ¼-mile testing, top speed and horsepower. Excludes non-mass production vehicles.

HTTP Error 500.30 - ASP.NET Core app failed to start

HTTP Error 500.30 - ASP.NET Core app failed to start

Common solutions to this issue:

Troubleshooting steps:

For more guidance on diagnosing and handling these errors, visit Troubleshoot ASP.NET Core on Azure App Service and IIS.