Hi there,
Any update on this? Not being able to modify the settings table in AZ is concerning, especially since it seems somehow code in my OnModelCreating is being ignored or overwritten. We are at the beginning of a large project where I'm sure other things in this section are going to be required.
Also, why is work properly in AspNetBoilderPlate but not AspNetZero is still confusing.
I don't seem to be seeing the exception anymore, so it looks like we are all set. Thanks!
Hi there,
Since it wasn't a bug, just a question, I originally posted it in StackExchange, per their request:
https://stackoverflow.com/questions/51390090/extend-size-of-settings-value-beyond-2-000-characters
It's very odd because I see the code being hit when I debug, but its completely ignored or overwritten by something in AspNetZero. It works perfectly in my ABP sample project.
ok so first of all, as I mentioned and the code above shows, I am trying to override the ABP Settings.Value property length so I dont have the ability to just 'set it as a string'.
I posted this problem to ABP a while ago and the solution they suggested, which works, is the above code I posted.
It does not work in ASPNETZERO however.
Simply pointing me to basic Microsoft EF documentation without taking the time to read my problem and then closing this question is not helpful.
How does that get me varchar(max)?
I need this to not have a fixed length. Was doing it successfully in Abp.
why does this work in Abp but not AZ?
Getting the same warning. At first I thought it may be because of my merge process but a clean download and build is causing the same thing.
I just set up our project to use IIS. It was a bit of a process but it's working no problem.
That should be it. To launch the Mvc project using IIS, within Visual studio change the Debug starting service from "IIS Express" to your new IIS profile.
Hope that helps! jasen
will try today.
we actually already are upgraded to 3.8.2
I'll try blowing away bin and obj files again today.
I mentioned in e-mail I couldn't respond here until my password was reset, sorry it was still considered abandoned.
The Route decorator worked fine as expected. We ended up using Swashbuckle and API versioning to give us a limited swagger file that we could publish as our API docs. So we have a "full" and "public" API now. The full is all inclusive and still includes all the ABP/AZ stuff. The "public" one is only showing API's that are decorated with GroupName="" We still unfortunately have to proxy out all our public API's that are dynamically generated, but it's not a huge deal. So, our proxy API looks something like this now:
[ApiExplorerSettings(GroupName = "public")]
[Route("/api/Components")]
public class ComponentsController : StatusCastControllerBase
{
private readonly IComponentsAppService _componentsAppService;
public ComponentsController(IComponentsAppService componentAppService)
{
_componentsAppService = componentAppService;
}
[HttpGet]
[RemoteService(IsMetadataEnabled = true)]
[Route("GetAll")]
public async Task<PagedResultDto<Components.Dtos.GetComponentForView>> GetAll(Components.Dtos.GetAllComponentsInput input)
{
return await _componentsAppService.GetAll(input);
}
}