I'm sleepy and it's all .NET Core's fault!
-
So I decided to upgrade a .NET Core 2.1 project to a .NET Core 2.2 project, after all what harm can it do? A LOT APPARENTLY! First, the build breaks. Read some Scott Hanselman blog and I need to use the .NET Core Tool Installer in my build to install the .NET Core 2.2.100 SDK. Done and on to Azure! Except the site went down... Turn on all logging I can find, but nothing! I turn on detailed information in the browser in the web config, because I had absolutely nothing to go on (at this point the whole world can read my errors). And there it is, a nice error "Handler "aspNetCore" has a bad module "AspNetCoreModuleV2" in its module list" Do some additional reading and I can't make any sense of it. Decide to try a completely new ASP.NET Core 2.2 project and immediately release it to Azure, same error. WTF MICROSOFT IF EVEN YOUR DEFAULT TEMPLATE DOESN'T WORK HOW AM I SUPPOSED TO MAKE IT WORK!? :mad::mad::mad: I made the only fix I could find... Revert to .NET Core 2.1... :sigh: (I just found out the "old" handler is AspNetCoreModule, perhaps it would've worked if I used that with 2.2?) That's working to throw your work down the drain :sigh: Usually, I wouldn't mind all that much, except I wanted to go to bed about an hour ago :sigh: At least the site is up and running again X|
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
So I decided to upgrade a .NET Core 2.1 project to a .NET Core 2.2 project, after all what harm can it do? A LOT APPARENTLY! First, the build breaks. Read some Scott Hanselman blog and I need to use the .NET Core Tool Installer in my build to install the .NET Core 2.2.100 SDK. Done and on to Azure! Except the site went down... Turn on all logging I can find, but nothing! I turn on detailed information in the browser in the web config, because I had absolutely nothing to go on (at this point the whole world can read my errors). And there it is, a nice error "Handler "aspNetCore" has a bad module "AspNetCoreModuleV2" in its module list" Do some additional reading and I can't make any sense of it. Decide to try a completely new ASP.NET Core 2.2 project and immediately release it to Azure, same error. WTF MICROSOFT IF EVEN YOUR DEFAULT TEMPLATE DOESN'T WORK HOW AM I SUPPOSED TO MAKE IT WORK!? :mad::mad::mad: I made the only fix I could find... Revert to .NET Core 2.1... :sigh: (I just found out the "old" handler is AspNetCoreModule, perhaps it would've worked if I used that with 2.2?) That's working to throw your work down the drain :sigh: Usually, I wouldn't mind all that much, except I wanted to go to bed about an hour ago :sigh: At least the site is up and running again X|
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
Damn you, .NET Core!! :omg: :~ :laugh:
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
-
So I decided to upgrade a .NET Core 2.1 project to a .NET Core 2.2 project, after all what harm can it do? A LOT APPARENTLY! First, the build breaks. Read some Scott Hanselman blog and I need to use the .NET Core Tool Installer in my build to install the .NET Core 2.2.100 SDK. Done and on to Azure! Except the site went down... Turn on all logging I can find, but nothing! I turn on detailed information in the browser in the web config, because I had absolutely nothing to go on (at this point the whole world can read my errors). And there it is, a nice error "Handler "aspNetCore" has a bad module "AspNetCoreModuleV2" in its module list" Do some additional reading and I can't make any sense of it. Decide to try a completely new ASP.NET Core 2.2 project and immediately release it to Azure, same error. WTF MICROSOFT IF EVEN YOUR DEFAULT TEMPLATE DOESN'T WORK HOW AM I SUPPOSED TO MAKE IT WORK!? :mad::mad::mad: I made the only fix I could find... Revert to .NET Core 2.1... :sigh: (I just found out the "old" handler is AspNetCoreModule, perhaps it would've worked if I used that with 2.2?) That's working to throw your work down the drain :sigh: Usually, I wouldn't mind all that much, except I wanted to go to bed about an hour ago :sigh: At least the site is up and running again X|
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
So I decided to upgrade a .NET Core 2.1 project to a .NET Core 2.2 project, after all what harm can it do? A LOT APPARENTLY! First, the build breaks. Read some Scott Hanselman blog and I need to use the .NET Core Tool Installer in my build to install the .NET Core 2.2.100 SDK. Done and on to Azure! Except the site went down... Turn on all logging I can find, but nothing! I turn on detailed information in the browser in the web config, because I had absolutely nothing to go on (at this point the whole world can read my errors). And there it is, a nice error "Handler "aspNetCore" has a bad module "AspNetCoreModuleV2" in its module list" Do some additional reading and I can't make any sense of it. Decide to try a completely new ASP.NET Core 2.2 project and immediately release it to Azure, same error. WTF MICROSOFT IF EVEN YOUR DEFAULT TEMPLATE DOESN'T WORK HOW AM I SUPPOSED TO MAKE IT WORK!? :mad::mad::mad: I made the only fix I could find... Revert to .NET Core 2.1... :sigh: (I just found out the "old" handler is AspNetCoreModule, perhaps it would've worked if I used that with 2.2?) That's working to throw your work down the drain :sigh: Usually, I wouldn't mind all that much, except I wanted to go to bed about an hour ago :sigh: At least the site is up and running again X|
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
MS is putting out a lot of rubbish lately. I was trying to get my feet wet in UWP yesterday. The default Class library and Application projects wouldn't even compile properly at first. It would give me the most obscure compilation errors and send me off to a googling spree. Had to turn off Native compilation, randomly updated some nuget references, did some random nuget restore commands, and finally got these very basic projects compiling. I'm seriously starting considering jumping ship.
Wout
-
Lesson learned: Do not upgrade to newer version before going to bed. ;P
Vincent Maverick Durano wrote:
Lesson learned: Do not upgrade to newer version before going to bed. ;-P
FTFY ;)
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
MS is putting out a lot of rubbish lately. I was trying to get my feet wet in UWP yesterday. The default Class library and Application projects wouldn't even compile properly at first. It would give me the most obscure compilation errors and send me off to a googling spree. Had to turn off Native compilation, randomly updated some nuget references, did some random nuget restore commands, and finally got these very basic projects compiling. I'm seriously starting considering jumping ship.
Wout
Yeah, or the infamous Windows October update :wtf:
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
So I decided to upgrade a .NET Core 2.1 project to a .NET Core 2.2 project, after all what harm can it do? A LOT APPARENTLY! First, the build breaks. Read some Scott Hanselman blog and I need to use the .NET Core Tool Installer in my build to install the .NET Core 2.2.100 SDK. Done and on to Azure! Except the site went down... Turn on all logging I can find, but nothing! I turn on detailed information in the browser in the web config, because I had absolutely nothing to go on (at this point the whole world can read my errors). And there it is, a nice error "Handler "aspNetCore" has a bad module "AspNetCoreModuleV2" in its module list" Do some additional reading and I can't make any sense of it. Decide to try a completely new ASP.NET Core 2.2 project and immediately release it to Azure, same error. WTF MICROSOFT IF EVEN YOUR DEFAULT TEMPLATE DOESN'T WORK HOW AM I SUPPOSED TO MAKE IT WORK!? :mad::mad::mad: I made the only fix I could find... Revert to .NET Core 2.1... :sigh: (I just found out the "old" handler is AspNetCoreModule, perhaps it would've worked if I used that with 2.2?) That's working to throw your work down the drain :sigh: Usually, I wouldn't mind all that much, except I wanted to go to bed about an hour ago :sigh: At least the site is up and running again X|
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
Sander Rossel wrote:
WTF MICROSOFT IF EVEN YOUR DEFAULT TEMPLATE DOESN'T WORK HOW AM I SUPPOSED TO MAKE IT WORK
This has been, 100%, my experience with recent templates for .NET Core within Visual Studio. I keep thinking that I clearly must be pressing that "next" button wrong or something, but they just don't work.
cheers Chris Maunder
-
Sander Rossel wrote:
WTF MICROSOFT IF EVEN YOUR DEFAULT TEMPLATE DOESN'T WORK HOW AM I SUPPOSED TO MAKE IT WORK
This has been, 100%, my experience with recent templates for .NET Core within Visual Studio. I keep thinking that I clearly must be pressing that "next" button wrong or something, but they just don't work.
cheers Chris Maunder
I rarely have that problem, they work most of the time, although I guess I've only used Web API lately. I am missing a lot of .NET Core templates though (like Azure WebJobs or Functions). And the templates they do have are often grossly outdated. For example, I know their templates still used Bower long after Bower was considered obsolete (even by Bower's creator himself).
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
