I'm using jgGrid 3.5 in my ASP.NET application. I would like to upgrade it to the new 3.6.
Is it enough just to replace the jqGrid JS file? Or are there any other changes I need to make in my code?
Now that 3.6 has been officially released the upgrade is easy - just drop the files from the js and css directories into your application. Of course you should then re-test your app to make sure nothing was changed/broken, just in case...
I just replaced, dev files from latest:
http://github.com/tonytomov/jqGrid/commits/jqgrid36
be aware of file: jquery.jqGrid.js which loads modules.
besides, jQgrid uses jQuery 1.3.2 + jQuery UI 1.7.2
Related
So I recently update from bootstrap 2 to bootstrap 4. I then changed the syntax, grids and such. The website was running/building fine in debug, however, when it comes to release, it won't work. It can build without errors, but when I run it, it seems like the site has the new syntax and classes (the code running is the one i changed) but bootstrap is still at v.2. I checked multiple times, there are no bootstrap 2 files left, nor any cdn references. I can see it still is running bootstrap 2 by changing classes from col-12 to, say span12. It works fine in debug, but not in release. Any clue why ?
Also, the site is running Asp.NET Core MVC Razor.
I think you might have a bundle-ing configuration issue.
Please verify your bundle configuration (App_Start\BundleConfig.cs) and the web.config settings and pertinent web.config transform.
You can find documentation on how to configure your bundles here : Bundling and Minification (assuming you're not using ASP.NET Core)
For ASP.NET Core it a bit more complicated because you can have multiple ways of doing the budleing. Documentation for it can be found here: Bundle and minifiy static assets in ASP.NET Core.
However, I think that is pretty probable that the production version of your app is still targeting the old Bootstrap version because of the bundle-ing configuration
I am using the latest visualstudio that comes with an older version of bootstrap 3 (when I choose the application template).
I tried to manually copy the lib files in the root folder of the new bootstrap 4 and the intellisense does not recognize it. Also the styles are not applied.
I tried installing the bootstrap package 4 (but it says incompatible) but nothing happen.
Which are the steps to have a fully working version of the new bootstrap on VS?
There's an older question on StackOverflow which could contain the answer to your question.
If you didn't do already, give it a try: Can you make visual studio scaffold etc. with bootstrap 4 in .NET MVC templates?
Maximo Anywhere 7.5.2.1 is shipped with the dojo version 1.7.8
I wanted to use some of the features available in dojo 1.10.x.
I tried replacing the www directory with new version of the dojo.
But it did not help.
Actually we use 1.9.3 dojo with that level of Anywhere. You should be able to replace the www subdirectory under the MaximoAnywhere project and it should pickup the new dojo, but one warning. We haven't tested on these later dojo levels, and #2 the dojo files will be much larger and might slow performance down unless you choose to use the compressed ones.
We are currently running bootstrap 2.3 in our application of over 400 html files. We decided the best way to upgrade to twitter bootstrap 3.0 without having to change all of our html files would be to include a .less file that references all the changes from 2.3 to 3.0. For Example: span6 in 3.0 is now col-md-6. Does anyone have a file that embeds all the old properties into a .less file that we could reference?
Actually, changing over isn't that bad. I have done this on a couple sites using find/sed (I'm on a Mac) by simply updating the old classes to the new. It will get the bulk of the upgrade done quickly.
Use this page for reference on which classes you need to update: http://upgrade-bootstrap.bootply.com/
Situation
I am working on an ASP.NET Web Forms project that was generated using the default Visual Studio 2012 project template. I have since then used NuGet to install jQuery UI version 1.10.0.
I need to update to jQuery UI 1.10.1 because there is a bug fix I need. According to the website, 1.10.1 is the current stable version. However, there is not a NuGet package available for this version!
I don't know why the NuGet package would lag behind the latest available stable release from the jQuery UI team on their website. (Yes, I realize there is probably a different team managing the nuget package itself... but it still seems like this needs to be kept up to date.... or the value of installing jQuery via NuGet is very limited.)
Question
How do I update jQuery UI (installed as a NuGet package) manually to 1.10.1 on my project?
I have already downloaded the latest 1.10.1 javascript files. Now.... when I look inside my ASP.NET Web Forms project, I see in the following files in the Scripts folder:
So what should I do here... delete the following two files?
jquery-ui-1.10.0.js
jquery-ui-1.10.0.min.js
...and replace with these new files?
jquery-ui-1.10.1.js
jquery-ui-1.10.1.min.js
This doesn't seem like it would work.
The way jQuery is being include in my masterpage (from the default template generated by Visual Studio 2012) is like this:
That JS bundle you see above, called "jquery.ui.combined" is auto-magically generated by some kind of hidden code. Go ahead and look through your project... you won't find anywhere obvious this bundle is defined. So if I add the latest JS files... it seems I have no way to define that they get used or bundled at all. They aren't the version that the NuGet package logic/code would be expecting!!!
Any ideas?
Another potential problem
When I downloaded jQuery UI 1.10.1, it also came with jQuery Core 1.9.1. As you will see above in my Scripts folder, it appears as if jQuery UI 1.10.0 goes hand-in-hand with jQuery Core 1.9.0. If I update jQuery UI..... do I also need to update to the matching jQuery Core as well? (These are separate NuGet packages)
Please answer this specifically
I would like for the answer to explain how to manually update the version of jQuery UI installed from NuGet package.... on an ASP.NET Web Forms project.
I think this would be useful so that in the future a developer can pull down the latest bug fixes as soon as they are included in a stable release on the jQuery UI website.... without needing to wait for the package to show up on the NuGet feed.
The jQuery UI team hasn't uploaded the version 1.10.1 for their package. I'm afraid you just have to wait until they release it.
If you can't wait, you can uninstall the current version of jQuery UI first, and then manually add the script files of version 1.10.1 into your project.
Work-around... although it seems like a bad approach....
I just opened up these files....
jquery-ui-1.10.0.js
jquery-ui-1.10.0.min.js
...and replaced the contents with the contents from these files:
jquery-ui-1.10.1.js
jquery-ui-1.10.1.min.js
I left the file names the same as they were. So even though the JavaScript files are named as version "1.10.0".... they are actually holding the code for version "1.10.1".
One of the reasons I think this might be a terrible idea
What happens if some other developer attempts to pull down my code from source control... and they use NuGet Package Manager to restore the packages they did not have yet. Wouldn't it pull jQuery UI nuget package and replace the JavaScript files I have modified with the ones from the nuget package? Then the page would start exhibiting the buggy behavior again, and no one would know why.
At the very least.... for now I can continue development with the bug fixed! It was very annoying... the overlay was appearing on top of the dialog and I couldn't interact with the page. Here is the bug that was fixed: http://bugs.jqueryui.com/ticket/8984
Go To : Visual Studio -> Tools => Library Package => And Package Manager Setting
Window opens Having Options as in Screenshot
Click On Add (+) Button At Right Top And Inside Source Browser To Your Folder Location of Whatever Package of Nuget You HAve. Name is Whatever You Want And Press Ok
You Can See Now Your Package Into Extensions And Updates Window
To Install In Current Project
use Package Manager console : Install-Package ANd your package name