Feb 09, 2017, 1:32 PM
Ext.NET 4 on Visual Studio 2010
If you have Visual Studio 2010 and checked out Ext.NET 4, you'll see that it no longer supports VS2010 (chapter one here).
But not all is lost! There's still ways to get Ext.NET up and running if you really can't afford to upgrade to any of the newer Visual Studio versions -- although we can't guarantee you everything is going to work, beginning with outdated libraries and infrastructure.
Before we can even think on upgrading, we need to check whether the NuGet extension for VS2010 is up-to-date. If not, and your version is too old, you won't be able to install Ext.NET package at all. It should not be too hard to upgrade NuGet extension though.
If you open the NuGet package manager dialog and there's an update, chances is that it will warn you on the dialog itself. But in the case you want to go directly to the point (or you just don't have the extension yet), you have to get to the Extension Manager dialog (Tools > Extensions Manager).
There you can either upgrade or install the NuGet extension thru the online gallery. You should have something like this in the end:
Now we can proceed with the new project and Ext.NET installation.
For the project, we are going to use the barest minimum, an empty Web Application. We have set it up via the File > New Project... menu like this:
Then we need to add the Ext.NET NuGet package. First open the NuGet package manager dialog for the project we just created:
Then, locate the Ext.NET package. There are other packages for MVC (and the corresponding MVC version) but we're going with just the WebForms one, for simplicity.
Once you start installation, it will check dependencies and ask you to accept. Please review the license agreements for the packages (the licenses are there for a reason, right?). If all good, accept the terms to proceed with the installation.
Then you should have Ext.NET installed and showing you its readme file.
All looking good, let's then open the example Ext.NET ASPX file for editing. On next post due to image amount limit per post. :)
But not all is lost! There's still ways to get Ext.NET up and running if you really can't afford to upgrade to any of the newer Visual Studio versions -- although we can't guarantee you everything is going to work, beginning with outdated libraries and infrastructure.
Before we can even think on upgrading, we need to check whether the NuGet extension for VS2010 is up-to-date. If not, and your version is too old, you won't be able to install Ext.NET package at all. It should not be too hard to upgrade NuGet extension though.
If you open the NuGet package manager dialog and there's an update, chances is that it will warn you on the dialog itself. But in the case you want to go directly to the point (or you just don't have the extension yet), you have to get to the Extension Manager dialog (Tools > Extensions Manager).
There you can either upgrade or install the NuGet extension thru the online gallery. You should have something like this in the end:
Now we can proceed with the new project and Ext.NET installation.
For the project, we are going to use the barest minimum, an empty Web Application. We have set it up via the File > New Project... menu like this:
Then we need to add the Ext.NET NuGet package. First open the NuGet package manager dialog for the project we just created:
Then, locate the Ext.NET package. There are other packages for MVC (and the corresponding MVC version) but we're going with just the WebForms one, for simplicity.
Once you start installation, it will check dependencies and ask you to accept. Please review the license agreements for the packages (the licenses are there for a reason, right?). If all good, accept the terms to proceed with the installation.
Then you should have Ext.NET installed and showing you its readme file.
All looking good, let's then open the example Ext.NET ASPX file for editing. On next post due to image amount limit per post. :)
Last edited by fabricio.murta; Feb 09, 2017 at 1:58 PM.