Fixed by commenting :
// options.PlugInSources.AddFolder(Path.Combine(_hostingEnvironment.ContentRootPath, "Plugins"));
in startup.cs
I did exactly the way it's describe in the document :
<a class="postlink" href="https://aspnetzero.com/Documents/Step-by-step-publish-to-azure-angular">https://aspnetzero.com/Documents/Step-b ... re-angular</a>
Works like a charm.. Thank you so much.
<cite>Kythor: </cite> Now I found this: <a class="postlink" href="https://stapp.space/run-angular-cli-react-cli-aurelia-or-vue-cli-build-in-vsts/">https://stapp.space/run-angular-cli-rea ... d-in-vsts/</a>
So instead of npm, i added a "command line" task with Tool: $(Build.SourcesDirectory)\node_modules.bin\ng.cmd Arguments: build -prod
But when executing the build i get this error: 'D:\a\1\s\node_modules.bin\ng.cmd' is not recognized as an internal or external command, operable program or batch file. Process completed with exit code 1.
However, if I look in my local folder, after using Yarn, the node_modules, folder is present, and there is ng.cmd. Should I just add node_modules in my source control?
I used this method and I was able to deploy Aspnetboilerplate code but not AspnetZero code
I am having the same issue. I tried the above way but doesn't work. Please advise
Can i get a response on this?
Hi -
While debugging the source code for ABP we found this :
Abp Ticket : <a class="postlink" href="https://github.com/aspnetboilerplate/aspnetboilerplate/issues/1617">https://github.com/aspnetboilerplate/as ... ssues/1617</a> Blame : <a class="postlink" href="https://github.com/aspnetboilerplate/aspnetboilerplate/blame/6076a126f975ea1721348f24c89ed7b44e9f2d6e/src/Abp.EntityFramework/EntityFramework/AbpDbContext.cs">https://github.com/aspnetboilerplate/as ... Context.cs</a> Source file : <a class="postlink" href="https://github.com/aspnetboilerplate/aspnetboilerplate/issues/1617">https://github.com/aspnetboilerplate/as ... ssues/1617</a>
You are reloading befoire doing a soft delete :
softDeleteEntry.Reload();
This is causing a select query to fire before deletion. So when we delete 3000 records it fires 3000 select statements and then 3000 update statements to delete the records.
I don't see the need of Reload for everyone, can we come up with a different solution ?
Thanks, Partha
I appreciate the fix you made. I am just hoping if the response time could be little faster. It took almost 5-6 days to identify and fix the issue.
This is a major bug if anyone is using multi database and multi tenancy.
I just sent you an email.
This is the same string that's being encrypted differently before and after upgrade.
