Have not heard back on this issue, from the team. Do u agree with the AI answer?
in the past the update tool only updates the backend. i want to see the an ootb solution for frontend, trouble shooting and what happens if we want to create a new site? the abp update only affected the backend
so i do not need to change this line: installdir_update="${installdir}/Update.exe"
I read the article. that is what I am doing. it works great if you just send a file to the endpoint. if you send more than just a file, it does not work. that is why u need to add the special binder
Configure(options =>
{ options.ConventionalControllers.FormBodyBindingIgnoredTypes.Add(typeof(AssessmentPreviewFixedFileDto));
});
I will try stringify'ing the other parameters, and deserialize on the server. maybe that will work.
this what was generated by abp when i did generate proxies:
filePreview2 = (source: AssessmentPreviewFixedFileDto, config?: Partial<Rest.Config>) =>
this.restService.request<any, AssessmentFilePreviewDto>({
method: 'GET',
url: '/api/app/assessment-parents/preview-2',
params: { columns: source.columns },
body: source.content,
},
{ apiName: this.apiName,...config });
this is: AssessmentPreviewFixedFileDto
export interface AssessmentPreviewFixedFileDto { content: IRemoteStreamContent; columns: AssessmentFileColumnDto[];}
public class AssessmentFileColumnDto
{
public string ColumnName { get; set; }
public int From { get; set; }
public int To { get; set; }
}
also if it helps, the example i sent above is sending of the file stream and extra data as 2 different properties to the endpoint.
This code base is using sends only one property containing the stream and the extra data i get a similar error
this the Service method
public async Task<AssessmentFilePreviewDto> FilePreview2Async(AssessmentPreviewFixedFileDto source)
{
using var reader = new StreamReader(source.Content.GetStream());
var text = await reader.ReadToEndAsync();
// Get columns
var columns = source.Columns;
var filePreview = new AssessmentFilePreviewDto
{
Content = text.Trim('\0')
};
return filePreview;
}
public class AssessmentPreviewFixedFileDto
{
public IRemoteStreamContent Content { get; set; }
public List<AssessmentFileColumnDto> Columns { get; set; }
}
here's the special form binding
Configure<AbpAspNetCoreMvcOptions>(options =>
{ options.ConventionalControllers.FormBodyBindingIgnoredTypes.Add(typeof(AssessmentPreviewFixedFileDto));
});
previewFile(fileDto: AssessmentFileDto): void {
this.parentService
.filePreview2({
content: fileDto as any,
columns: [{ columnName: 'Col', from: 1, to: 3 }],
})
.subscribe(res => {
const file = res.content;
const csv = this.fileHelperService.parseCsv(
file,
this.parentHelperService.getDelimiter(fileDto['delimiter']),
);
this.csvFile = {
headers: csv.meta.fields,
rows: csv.data,
errors: csv.errors,
};
this.isPreviewing = true;
});
}
proxy
filePreview2 = (source: AssessmentPreviewFixedFileDto, config?: Partial<Rest.Config>) =>
this.restService.request<any, AssessmentFilePreviewDto>({
method: 'GET',
url: '/api/app/assessment-parents/preview-2',
params: { columns: source.columns },
body: source.content,
},
{ apiName: this.apiName,...config });
if u want i can share all the code, i still have ur email. or i can do something online w/ u. or if u have something u want me to try, i am willing to try out
I would like to know the answer on this question. But in truth I am using a work-around, So whenever I can get an answer will be good. We do have another ticket that is more pressing, and any attention that can be given to it, even though my ticket might take longer to resolve would be good: https://abp.io/support/questions/9225/401-on-ABP-API-Using-External-OpenID-Access-Token-Works-from-Browser-and-Swagger
I might have found something that works
I changed the Entity to inherit from Entity<long>
added
[NotMapped]
public override long Id
{
get { return 0; }
protected set { }
}
change the repo to public class EfCoreEdRepository : EfCoreRepository<DataDbContext, Ed>
we cannot update to .net 9, because of contract reasons. can we simply update the front-end to 9.1 without any bad side affects? we did update to 9.0.4 to get rid of the console errors for the for loop tracking issues