Hey guys in this video we'll take a quick look at package management.
No I would have mentioned before in the earlier times and we're looking at what comes with the project.
But now we get all of these bootstrap files and all of these script files decor and so on.
I would have mentioned that they're not necessarily always at the latest versions.
Right.
Because as they build on it to get version one point one zero dot one and then one two as if it's offensive.
The easiest way or the the the way that you would probably think about it naturally to upgrade these
files would be to go and get the physical files and come back and replace them here in the project and
that would be fine.
That would be understandable.
But then Visual Studio kind of tries to make it easier for you by giving you what they call a new get
package management so if you right click your project or your exec references then you'd see that they
have this thing called managed.
You get packages and when you put that it opens up a nice menu section where it's listing out all the
Installed Packages all of the possible updates and also allowing you to browse.
So there are times when what comes out of the box of Visual Studio might not be adequate for what you
want to do.
And so they have an open source community where they allow people to contribute solutions.
And so you can actually browse all of those solutions right here and you can download and units you
can get adopters for my school database and even bootstrap everything that you might need.
It's somewhere here.
So you can always just search if you know exactly what you want and you can actually just click it and
view more details as to the version and you can select to exactly what version.
So it's a very powerful selection and package management tool.
I'm going to go over to updates because we can see that we have thirty four pending updates so as at
the time of this regarding MVC five was kind of being phased though.
So it's kind of behind but a lot of these things all out of the box at the time were the latest.
No they're not the latest.
So new gates is allowing me to say okay I can update and let's look at bootstrap.
I warned about updating bootstrap because if I did bootstrap right here I'm moving from version 3.0
to Version 4 and there are quite a few changes in the code for bootstrap between 3 and 4.
So a big jump like that would cause me itself to do a lot of regression testing and changes and all
over the place.
Right.
So for the purpose of this course I will not updated to Version 4.0.
All right.
But then as you go along we see that query we've got this at version 1 it's not version three point
four and the other G core of libraries are quite farther ahead than we are right now.
You see that MVC libraries.
So it's not only for JavaScript and see us as files but also deals and deal those are listed on the
references sections all of these things that give it the actual functionality all of those things can
be updated using new gets.
So I'm going to focus on me in the the script files because sometimes when you did the deal those things
just break things stop working off compatibility issues and all sorts of things.
So I'm just going to keep it simple.
And I'm just into updates.
Anything that is javascript.
So here I know that this this is a javascript file all right.
Web Greece it's made for optimizing I'll use that also I'll take Newton Jesus son of a modernizer.
You'll see the query validation and the G query and please note if you're going to upgrade any J Cary
doc file please I'll be at the G.
Query Base File I've run into problems in the past with that thinking that oh I don't need the data
to where but the other things I can update.
So those things can be updated if I'll be a bootstrap then it would be the census file and the script
file associated with it.
But once again I will be moving from and I'll leave everything else as is of course you can.
You can always rule back so if you tried to update these Microsoft dots dependencies or ideals from
version to Verizon and something bricks you can always just take note of what version worked and then
you can just rule box so you can uninstall or you can see what is the version you want in the selected
like that.
And that just click updates and it will install that specific version for you.
So I want the latest one for this one and then just put that back.
And then once you're finished you know picking and choosing and this same procedure applies to when
you're browsing and trying to install you just select the one you want and then you can just be installed.
This would be installed as a so beats someone to go ahead and update these.
So my problem to do in this process to say that oh there is a to make these updates.
And are you sure you want to continue I just click Okay then you accept a license agreements that come
your way
all right.
And we're done.
So you would see that you got a few more ticks because changes had to be made and the new get it engine
issue in that we have fewer updates pending because you know everything else is art and it leads us
so we can just close that window.
What I want to point I'll do also is I will once again read tweaks here and the packages that config
file is actually like tracking all of the packages that's our in our project.
If we take a look in the scripts for that we see that we have some new files.
So when we get a new file because of our source control engine tracking all the changes we get this
plus science so get knows that this is a new file.
It was never there and the neurotic means that these were modified.
Right.
So we got rid of the old files and brought in the new files and we didn't do any updates to our script
to our assistance.
So there are no changes there.
Of course if I submitted bootstrap then you would see signs there for the brand new files.
All right.
So once all of this is done we can just go ahead and control shift and b to do a build and the build
was successful.
I will also just go ahead and check in this school outside of the school and comets.
So once again because we have its own source control no we're tracking every change that we make so
we can just see updated some script files.
And did you the three versions so that should be descriptive enough and then we can assume it's all
and sync.
So once we do with that what it does is commit the changes locally and then it just pushes them to get
hub automatically so that we don't have to get involved with a second step once you come it's all unseen.
And there we go successfully synchronize.
And once again if we just take a look at Toba we just refresh then we'll see we have a comet.
All right.
And by clicking comments we can see all of the changes when they were made and what they entail.
All right so that's where your comments come in handy.
And then if you want that specific version you can just click it and it was so you.
What was done.
Can we just froze the files to get that specific version of files.
So if anything breaks then we can just roll back to before making those you get updates.