Uploading Files to Blazor - The Blazor File Upload Mini Course 

Thanks!

Fantastic!

You are welcome.

You are welcome.

You're welcome!

Glad you like them!

Glad I could help!

Thank You!

You are welcome.

You are welcome.

You're welcome.

Yes, it is a good thing. Use the best option for the specific task. With that being said, don't go crazy. Otherwise, it will be harder to understand what is happening when going through the code.

Check for errors. If there aren't any, walk through your code and see if you can figure out why.

Just add *accept=".jpg,.png,.jpeg"* to the InputFile item.

@@IAmTimCorey That's exactly what I have.. But I found why.. Did it on other PC. It works fine in Windows 10 but doesn't in Windows 11. I guess MS modified Open Dialog in Win 11 and broke this functionality! :(

I've got videos on Blazor WASM on this channel. Do you mean specifically file uploading or just WASM in general?

@@IAmTimCorey File Uploading in WASM ! Thanks alot!

@@IAmTimCorey I too would like to see file uploading for WASM. Great video.

I'm not sure what the issue is. The code does work, so maybe check to see what is different or step through the code to see what it could be.

@@IAmTimCorey Sir Thanks, I am making a little mistake. Now working fine for all types of files

Glad it was helpful!

Downloading files is coming, although just from our own server. Adding Azure storage won't be much different, though.

I already have videos on that topic: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-j3S3aI8nMeE.html and ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-wyoCxzRLUsQ.html

This approach is just fine for a lot of situations. The best practices in this case don't apply to all situations.

I get what you are saying, but usually the need for one exit point is because your code is doing too much. That's the underlying problem. Making just one exit point is just putting a band-aid on the real problem.

@@IAmTimCorey It's not so much that it's doing so much, they are more flexible. My routines are short and narrow in focus. If they get too long I refactor them into multiple routines. But in my experience, multiple exit points ultimately create what I call spaghetti code. With one exit point I can look at a glance what the input is expected to look like and what the output is expected. With multiple exit codes it isn't as clear. If I want to change the code where something always runs it is more complicated because of early exits - even Microsoft allows for this concept in the Try statement - you can catch a problem, go to the exception, but regardless Finally executes. One entry - one exit - always. Far more straight foward, in my opinion.

Thanks for sharing! You will need to grant the user that is running your application permissions to that folder as well. Just mapping it won't be enough.

The issue with this is that it relies on user input unless you only allow dropdown values. If you only allow dropdown values, you then are subject to repetition. How many white Ford F150s from 2019 are out there? A TON. So now you are relying on the UserId to be the unique part. However, what if the user was a small business and they bought two white F150s at the same time. Now they want to sell them both. Now you have either duplicates or you have to add an additional factor to the file name. Trying to come up with unique names that are meaningful and also stand up to production-scale issues is really hard.

@@IAmTimCorey In the scenario given the user would have to put in information - his contact info, description of what he/she is selling, etc.. anyway. Making the upload of the images takes advantage of the information they have to enter anyway. Part of behind the scenes could be a sales id to be included in the file name connecting it with that specific sale item - I didn't think of that during the example. There would be multiple pictures as photos of front, side, engine, etc would be uploaded - this is handled by the seq # at the end. You are right that coming up with unique names that are meaningful can be difficult - but with a little thought and planning it can usually be accomplished. The more you can make your tables, rows, columns, code and even uploads be self documenting, the better off you are, in my experience. While I understand the issue you bring up in depending on user input (in the above example you can do most of it using drop down boxes - but that isn't always the case).

@@IAmTimCorey You could simplify the example by basically using the transaction key as being the main naming criteria. In the example I gave most likely there'd be a sales item id as the primary key. image-pk-seq#.jpg where pk is the primary key.