Delete uploaded files in Blazor WebAssembly?

Question

Delete uploaded files in Blazor WebAssembly?

Daniel Avadanei 41

I have asked a question here:
Link
I winder if you guys had this issue before and how did you fixed it or do you know any work around ?

Anonymous

2021-12-28T02:12:19.967+00:00

Hi @Daniel Avadanei ,

Can you explain more details about the product.FileMapper? Is it a repository service, global variable or a DbContext? From your code, you have stored the upload file in the product.FileMapper, before deleting the upload file, you should check whether you could get all the upload file via the product.FileMapper and fileguid is correct. Try to set a break point to check it.

Best regards,
Dillion
Daniel Avadanei 41 Reputation points

2021-12-28T08:23:22.537+00:00
Hi @Anonymous ,

FileMapper is just a class that I made that I use to map some details about the file and then send it to the server. This is the class :

public class FileMapper { public int MediaTypeID { get; set; } public int ResourceID { get; set; } public Guid ResourceGuid { get; set; } public string ContentType { get; set; } public int CRUD { get; set; } }

This instance of this class is created per each file that I upload in front-end, and it serves one purpouse, to map some details about the file. The fileguid is correct I checked it with a breakpoint.

There is an explanation on StackOverflow why this issue appears:

On re-add new files all previously created objects belonging to previous files aren't saved. Meantime the index starts with unsaved objects that no longer exist. Saving files at each selection step gives an correct index.

There is also a screenshot of the issue:

https://i.stack.imgur.com/TZYZJ.png

I'm not sure how I could use this information to solve my problem.
Anonymous

2021-12-29T05:41:23.133+00:00

Hi @Daniel Avadanei ,

Where do you store the uploaded files? In memory or database? Based on the provide code, it is hard to reproduce the problem, I suggest you could create a simple sample to reproduce the problem, and share it via Github or Onedrive, then, it might easier for us to help you fix the problem.

Best regards,
Dillion