Updating this...
When I copy/paste the clockface.css into the css for my dashboard widget, it displays correctly. This gets me going, but I'm looking for advice on how to do things more neatly - I don't want to copy/paste this .css to individual page style sheets.
Wow! Cool.
Thanks so much. Just updated and tried it out, and everything works. Great job.
By the way, this RAD tool is the reason I purchased ASPNetZero instead of building on ABPBoilerplate. Both the RAD tool itself and also the other features in ASPNetZero are well worth the price, but it was the RAD tool that sold me.
I know this is closed two years ago, but for those (like me) finding this solution from a search...
The solution above did not work for me, and I was also reluctant to edit the ModalManager.js in case a future upgrade of ASPNETZERO reverted my change.
So I did this in my CreateOrEditModal.js file, in the "this.init" function, right after invoking summernote():
$('.note-editing-area').keydown(function (e) { if (e.which === 13) { e.stopPropagation(); } });
Because SummerNote uses the note-editing-area class for its text input box.
It's up! Version 8.0 with Core 3.0 support is available for download.
I just downloaded the v8.0 project and all went smoothly. Thanks team, I've been waiting for this so that I can add my OData support!
On further searching I found this fiddle: https://dotnetfiddle.net/1ganYd, which gave me the pieces that seem to work, no installation packages required!
I have everything in the .html file at the moment and the calendar appears, so now I'll put everything in the right places.
Leaving this here in case anyone else needs it.
Perfect! Thank you.
Angular wasn't what I needed - I'm creating a data transfer client, not a UI. But in the article you linked to, this was precisely what I hoped for:
AbpAspNetCore().DefaultWrapResultAttribute.WrapOnSuccess = false;
This is now resolved.
The errors arose because none of the minified .js files were on the app service. I'm guessing that's what NPM does, but i don't know why I wasn't getting them deployed.
In the end I found that, although I thought it not relevant, I had some differences in my pipeline from the configuration in https://docs.aspnetzero.com/en/aspnet-core-mvc/latest/Setting-Up-an-Azure-Pipeline-Mvc-Core
When I went back and set mine up precisely as that document recommends it works.
I had used the Pipeline created by Visual Studio "Configure Continuous Depoyment", and adapted it. It uses different tools for the build and test, so there must be some difference there.
tl;dr: it's resolved.
This one is resolved now.
I updated Microsoft.NET.Test.Sdk to 16.3.0 (from 16.2.0). This changed the error messages, which led me to the solution. The wildcard selection of DLLs in the Azure test selection picks up xUint DLLs as well. Changing the selection is the solution, which I learned from this advice https://xunit.net/docs/getting-test-results-in-azure-devops
I found that I could not figure out what all the exclusions would need to be (The ones listed in that website didn't seem sufficient), so instead I explicitly specified the MyProjectTests.dll file without a wildcard.
Unit tests now run in Azure.