Going through the series. Top notch. I'm also getting back up to speed on my C# skills after having to deal with some legacy software for a while (vintage VB6) for a client, who thankfully has decided to announce an end of life to the product. In that regards, just seeing the code walk-throughs in these videos brings back those basic concepts and is a great refresher course in an of itself. On to part 5 of the series.
Great class as always Tim. I've also noticed the display bug on the NuGetPackages screen. It always start on the second item. A lot of times I spent seconds looking for the package and it the screen was just trolling me. Thanks Tim!
I dislike it for most cases. It causes a significant increase in database size, backup size (and timing), and more. Besides, files don't usually have the same backup requirements as the rest of your data.
Hi Tim, i apologize if you answered this in the video but i could not find it anywhere. Where would you recommend storing the actual image files in production? Is it okay to store them in wwwroot, say if youre deploying on azure? Or is that even possible? Im in the process of trying to figure this all out(im a noob). Thanks for all you do.
Glad you figured it out. Yeah, I prefer to store them away from wwwroot because if I deploy a new version of the website, I can't delete everything that currently exists. That may not seem like a big deal, but what it leads to is orphaned files that still exist but are no longer used (potential security hazard). Plus, it also limits you to only one server. If you decided to scale out (multiple web servers), you would have to replicate those images to every site copy. That's messy. Storing them in someplace like a blob container is a much more flexible solution.
Great tutorial. I am a subscriber on your IAmTimCorey site, however, I'm not finding the full series, would you be able to help me out with finding that?
If you look at the playlists on this channel, you will see all of my free courses. Here is this specific one: th-cam.com/play/PLLWMQd6PeGY2yqBcxsKvsNHplMrGa-SeK.html
i hope you explain single database vs multiple node cluster how enterprises work with SQL failover cluster, how connection string look like in application layer
This is how to map for example to look for another location outside server folder (wwwroot): In Program.cs / Startup.cs (depending on .net version) add under app.UseStaticFiles() this code : app.UseStaticFiles(new StaticFileOptions { FileProvider = new PhysicalFileProvider(@"E:\images"), RequestPath = "/images" });
thanks again, but a question though: wouldn't it be more convenient to have enums like Microsoft.Data.CommandType.StoredProcedure and Microsoft.Data.ConnectionState.Open instead of System.Data ...?
@@IAmTimCorey Yes i Know, but i would expect to use for example Microsoft.Data.CommandType.StoredProcedure instead of System.Data.CommandType.StoredProcedure since we use now: microsoft.data.sqlclient
I enjoy very much your videos and learn a lot from them, but you stopped sending me the source codes. Is there a reason, a limitation or something else?
The title doesn't relate to the content or is misleading as at no point are you uploading to SQL? Yes, I understand in majority of cases its inefficient to upload into the database but I was expecting this video to go through that exact process. As a side note, have you looked into the SQL Filestream option for handling BLOB files instead of the traditional method of storing file binary data within a table.
The title is "Capturing Uploaded Files in SQL". That's what we are doing. We are identifying where the files are and then storing that information. I didn't say "Uploading Files to SQL" because that's not what we are doing. I know, it is a subtle difference, but it is an important one. Yes, I've seen and used the Filestream option, but I do not use it in almost any case. It is almost always a bad idea. Here is a video with more of my thoughts on the topic: th-cam.com/video/XnNbizvb1uM/w-d-xo.htmlsi=Tro-t_uPG9VJ5oGR
Going through the series. Top notch. I'm also getting back up to speed on my C# skills after having to deal with some legacy software for a while (vintage VB6) for a client, who thankfully has decided to announce an end of life to the product. In that regards, just seeing the code walk-throughs in these videos brings back those basic concepts and is a great refresher course in an of itself. On to part 5 of the series.
I’m glad they are helpful.
Great class as always Tim.
I've also noticed the display bug on the NuGetPackages screen. It always start on the second item. A lot of times I spent seconds looking for the package and it the screen was just trolling me. Thanks Tim!
You are welcome.
Hi,Tim
great stuff 👍
I was wondering what are your thoughts on using FILESTREAM in SQL SERVER for handling uploads, and would you recommend using it?
I dislike it for most cases. It causes a significant increase in database size, backup size (and timing), and more. Besides, files don't usually have the same backup requirements as the rest of your data.
Hi Tim, i apologize if you answered this in the video but i could not find it anywhere. Where would you recommend storing the actual image files in production? Is it okay to store them in wwwroot, say if youre deploying on azure? Or is that even possible? Im in the process of trying to figure this all out(im a noob). Thanks for all you do.
Disregard this message. After doing a bit of research I found that blob container is what i was looking for.
Glad you figured it out. Yeah, I prefer to store them away from wwwroot because if I deploy a new version of the website, I can't delete everything that currently exists. That may not seem like a big deal, but what it leads to is orphaned files that still exist but are no longer used (potential security hazard). Plus, it also limits you to only one server. If you decided to scale out (multiple web servers), you would have to replicate those images to every site copy. That's messy. Storing them in someplace like a blob container is a much more flexible solution.
Great tutorial. I am a subscriber on your IAmTimCorey site, however, I'm not finding the full series, would you be able to help me out with finding that?
If you look at the playlists on this channel, you will see all of my free courses. Here is this specific one: th-cam.com/play/PLLWMQd6PeGY2yqBcxsKvsNHplMrGa-SeK.html
Hey Tim, Could you please put a video together to show how to upload files to a SharePoint site. Thank you
Thanks for the suggestion. Please add it to the list on the suggestion site so others can vote on it as well: suggestions.iamtimcorey.com/
i hope you explain single database vs multiple node cluster how enterprises work with SQL failover cluster, how connection string look like in application layer
If I want the table & submission form to be on separate components, will I have to make the list a global variable? If so, how?
Don't use a global variable. Store the data in the database and then add to it with the next form. Or pass the data between components.
Hi Tim,
How can I use : D:\\Temp\\Storage on production server ?
Most of shared hosting only allow access to wwwroot.
Thanks
This is how to map for example to look for another location outside server folder (wwwroot):
In Program.cs / Startup.cs (depending on .net version) add under app.UseStaticFiles() this code :
app.UseStaticFiles(new StaticFileOptions
{
FileProvider = new PhysicalFileProvider(@"E:\images"),
RequestPath = "/images"
});
Thanks!
You are welcome.
thanks again, but a question though:
wouldn't it be more convenient to have enums like Microsoft.Data.CommandType.StoredProcedure and Microsoft.Data.ConnectionState.Open instead of System.Data ...?
I'm not sure what you are asking. System.Data is a namespace and couldn't be an enum.
@@IAmTimCorey Yes i Know, but i would expect to use for example Microsoft.Data.CommandType.StoredProcedure instead of System.Data.CommandType.StoredProcedure since we use now: microsoft.data.sqlclient
Add Nuget glitch of showing the list starting at second row happens to me too. Have not changed font sizes. Also happens for other searches.
Yeah, it appears to be a global issue.
How about capturing multiple files upload in SQL?
You do it the same way, just in a loop.
I enjoy very much your videos and learn a lot from them, but you stopped sending me the source codes. Is there a reason, a limitation or something else?
I'm working on a bug with the system right now. Your email should come through once it is fixed.
Do you have a free course on Blazor?
where is it?
You are one a small one right now. Also, the Suggestion Site playlist is another that uses Blazor. I also have Blazor videos on this channel as well.
@@IAmTimCorey Do a live stream about htmlx and how to use it with blazor and how it will be its future. Would you replace React?
The title doesn't relate to the content or is misleading as at no point are you uploading to SQL? Yes, I understand in majority of cases its inefficient to upload into the database but I was expecting this video to go through that exact process. As a side note, have you looked into the SQL Filestream option for handling BLOB files instead of the traditional method of storing file binary data within a table.
The title is "Capturing Uploaded Files in SQL". That's what we are doing. We are identifying where the files are and then storing that information. I didn't say "Uploading Files to SQL" because that's not what we are doing. I know, it is a subtle difference, but it is an important one. Yes, I've seen and used the Filestream option, but I do not use it in almost any case. It is almost always a bad idea. Here is a video with more of my thoughts on the topic: th-cam.com/video/XnNbizvb1uM/w-d-xo.htmlsi=Tro-t_uPG9VJ5oGR