Hi,
Sorry I might be interpreting this wrong but the Lookup Table DTO's are causing the conflicts:
The below only happens once you link an object more than once.
System.InvalidOperationException: Conflicting schemaIds: Identical schemaIds detected for types Abp.Application.Services.Dto.PagedResultDto1[[BMS.Products.Dtos.ProductDepartmentLookupTableDto, BMS.Application.Shared, Version=5.0.0.0, Culture=neutral, PublicKeyToken=null]] and Abp.Application.Services.Dto.PagedResultDto1[BMS.DiscountGroups.Dtos.ProductDepartmentLookupTableDto]. See config settings - "CustomSchemaIds" for a workaround
at Swashbuckle.AspNetCore.SwaggerGen.SchemaIdManager.IdFor(Type type)
at Swashbuckle.AspNetCore.SwaggerGen.SchemaRegistry.CreateReferenceSchema(Type type, Queue1 referencedTypes) at Swashbuckle.AspNetCore.SwaggerGen.SchemaRegistry.GetOrRegister(Type type) at Swashbuckle.AspNetCore.SwaggerGen.SwaggerGenerator.CreateResponse(ApiResponseType apiResponseType, ISchemaRegistry schemaRegistry) at System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement](IEnumerable1 source, Func2 keySelector, Func2 elementSelector, IEqualityComparer1 comparer) at Swashbuckle.AspNetCore.SwaggerGen.SwaggerGenerator.CreateOperation(ApiDescription apiDescription, ISchemaRegistry schemaRegistry) at Swashbuckle.AspNetCore.SwaggerGen.SwaggerGenerator.CreatePathItem(IEnumerable1 apiDescriptions, ISchemaRegistry schemaRegistry)
at System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement](IEnumerable1 source, Func2 keySelector, Func2 elementSelector, IEqualityComparer1 comparer)
at Swashbuckle.AspNetCore.SwaggerGen.SwaggerGenerator.GetSwagger(String documentName, String host, String basePath, String[] schemes)
Hi,
I have no problem changing this on my side as you guys are already giving us so much and it is a wonderful project:
I don't know if this is also something that other people might find useful as a default for the RAD tool.
Due nature of the system that I am currently writing which is a full ERP/CRM/E-Commerce/Projects/ Production system I have a lot of links on certain tables which are always on other tables by default.
Currently, when you are generating the links between tables there is by default a property Id specified which can be changed naturally. At first, I did not notice the naming convention directly relates to the property and does not have an alternative "link" value of sort.
I encountered errors due to this hence why I am suggesting this, although it is not a train smash or anything, it is a nice to have and possibly something other people might like/agree on.
In the previous project when we linked tables we always referred to the naming convention as FK_TableName_LinkTableName_LinkeProperty.
Currently, WarehouseId is referenced in all tables where Warehouse is specified which create duplicates in the end.
In my case, it would be something like: FK_Products_ProductWarehouse_WarehouseId.
I don't know if there is a suggestion thread somewhere for things like this but here it is. If there is a place for suggestion please let me know where and ill remove the post here and drop it where required and future things as well.
Hi,
In normal circumstances, I would be able to but on this specific server, I am unable to remove(untick) it in Roles & Features.
I'll stick with this method in case the client needs to use WebDAV at some stage for something else.
Thank you.
Regards, Gideon Badenhorst
Funny enough, it is not that CORS is the problem. The main culprit, in this case, is WebDAV.
You need to configure the webconfig file to remove webdav module and webdav in order to fix things like posts being handled as puts and stuff like that. The below fixes the issue it seems. As I can't remove WebDAV from IIS, the only way is to remove it this way.
<system.webServer> <ins><modules runAllManagedModulesForAllRequests="true"> <remove name="WebDAVModule" /> </modules></ins> <handlers> <ins><remove name="WebDAV" /></ins> <add name="aspNetCore" path="" verb="" modules="AspNetCoreModule" resourceType="Unspecified" /> </handlers>
HI,
I have the logs on (stdout=true). I also have full access assigned to the deployment folders. However, I have not managed to get them working as of yet. They always give the error that they can't be created, no matter where I deploy them.
Warning: Could not create stdoutLogFile \?\C:\inetpub\BMS_API\logs\stdout_5720_20183832812.log, ErrorCode = -2147024891.
I have seen several posts regarding fixes for this but most of them relate to editing the csproj file as a "workaround". I would rather have the correct way to resolve such a scenario than a quick fix which has been around since Core 1.0.
Is there something else I am missing, I assume someone has had this with the ASP.Net Zero project at some point?
The thing that I don't understand about this whole scenario of CORS. 70% of my functionality is default methods generated with all the basics of the ASP Net Power tools and they work. But Delete and system related updates don't work. I tried updating the Visual settings now and I get CORS error when I save.
Hi,
Not sure if this is 100% the same scenario as I have just encountered today as well.
For me it was part of the setup that i did not do: To be specific it was this segment -> To start debugging Xamarin app you need to configure host settings. You can use either Web.Mvc or Web.Host to feed the Xamarin app. Open Windows Command Prompt. Go to the folder where your Web.Host or Web.Mvc csproj file is located. Then run the commands below to start hosting your Web Api.
SET ASPNETCORE_ENVIRONMENT=Development SET ASPNETCORE_URLS=http://*:22742 dotnet run
<a class="postlink" href="https://aspnetzero.com/Documents/Development-Guide-Xamarin#debugging-xamarin-app">https://aspnetzero.com/Documents/Develo ... amarin-app</a>
Also what was different was, my emulator was android 7.1 and my project was android 8. <- not sure if that can also lead to the same scenario.
Hope this is helpfull
@ismcagdas This is a live/deployed environment, not during debugging. From what I understand and could find, this "App_Data/Logs.txt" is only in debug mode.
Am I missing something, like another log location for live/deployed?
Hi,
I've deployed an initial version of a website and the problem i am experiencing now is a rather annoying one. How does CORS interact with the overall functions(Post/Put/Delete/etc) of ASP Net Zero?
I have no problems updateding, creating or viewing data but when I try to delete it blocks me with: products:1 Failed to load <a class="postlink" href="http://api">http://api</a>.{domain}.co.za/api/services/app/Products/Delete?Id=641: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://{domain}.co.za' is therefore not allowed access. The response had HTTP status code 405.
As far as I know I followed all the steps correctly when deploying including the config files with all the forward slashes etc.
I am using the latest version of Angular + Core.
Here is extracts from my config files: Code Config: "ServerRootAddress": "http://api.{domain}.co.za/", "ClientRootAddress": "http://{domain}.co.za/", "CorsOrigins": "http://{domain}.co.za,http://localhost:49152" Angular Config: "remoteServiceBaseUrl": "http://api.{domain}.co.za", "appBaseUrl": "http://{domain}.co.za",
Is there something I'm doing wrong here?
Any assistance would be greatly appreciated.
Hi,
The problem is mainly that there is about half of the PrimeNG functionality unavailable at the moment. Certain aspects that I have to use needs an upgrade to take place as it is only available in higher versions.
I would gladly leave things as is if I could but the functionality is a requirement for a specific segment of a project I am working on.
Hi,
I'll do so tomorrow. I'm just running on a very tight deadline and will create it once I am done.
Will include as much information as possible.
Thanks