Hi, I'm using IE 9 and all of the framing of controls, etc. are showing up fine, but what's not showing are all of the images.
So the HTML Editor doesn't show images on the toolbar, the validator doesn't show the image on an error (even though there is space for it etc.)
I left the images in the sub folder under the css as per the instructions but they don't seem to be referencing correctly.
What am I doing wrong?
Hi,Can you please provide us with a simple HTML page on which you are able to reproduce the problem?It sounds like a general issue that might be caused by either one of the following:
Of course, I could be way off track with my suspicions, but such a general issue is often caused by a general miss-configuration.Alternatively, if possible can you post a screenshot of what the Network tab of IE9's DevTools is showing? (That tab should tell you if there are images that weren't found)Something like:
Firefox's FireBug has a much better Network tab, so if possible provide us with a screenshot of it instead.Thank you in advance! Every piece of infromation that you give us will help us solve this mystery.Cheers!Borislav
The problem is using mvc.net 4's bundles... It breaks the pathing... which is fine for the infrastructure images because you can just put them in an images folder in the same root as the bundle...
But for themes it's a problem because there isn't a unique name for the themes so you have to choose one or the other...
Suggestions other than editing the css files every time a new version comes out?
Hello,
The Infragistics Loader resolves all the Infragistics resources (styles and scripts) for you. You just need to provide the path to required CSS and JavaScript files and declare which resources the loader will fetch for the page. You can change the CSS and script path based on your project folder structure. Refer to the link below that will give you more details on this:
<http://help.infragistics.com/NetAdvantage/jQuery/2012.1/CLR4.0?page=Deployment_Guide_JavaScript_Resouces.html>
I hope this helps.
It works, but the problem is that it doesn't solve what bundling does. There are still numerous requests going over the wire for these separate resources. (in fact one more than without the loader.)
Hmmmm .... all of this bundling and "fake resource requests" sounds fishy.Personally I'm still an MVC4 noob, so can you please send me a sample (MVC4) project where we can reproduce the problem? Thanks in advance!
I am just following up to see if you need any assistance with this matter.
Thank you for the additional details. I have reviewed the link provided. Based on link provided I understand ASP.NET MVC is Beta version. I have logged a feature request regarding “Bundling and Minification support for igLoader. The feature request number is PI12060011.
We value your input, and our philosophy is to enhance our toolset based on customer feedback. If you would like to follow up on your feature request at a later point, you may contact Developer Support management via email. Please include the reference number of your feature request (PI12060011) in the subject and body of your email message.
You can reach Developer Support management through the following email address: dsmanager@infragistics.com.
Here's the official entry from The Gu: http://weblogs.asp.net/scottgu/archive/2012/02/19/asp-net-mvc-4-beta.aspx
Here is a deep dive: http://codebetter.com/johnvpetersen/2012/03/06/asp-net-mvc-4-beta-bundling-and-minification-dymystified/
Basically you register your static script and css files programatically, then mvc.net goes and minifies (if you tell it to) and bundles all of the scripts that you specify into a single file.
This accomplishes 3 purposes:
1. By minifying it shrinks the files. Obviously Infragistics is already minified however it's all of the others that matter.
2. It obviscates the code significantly.
3. It eliminates n-1 number of http requests thus speeding up page load.
Further with a little work you can make it serve these files from a sub domain thus eliminating the overhead of cookies being sent with the request when not required and do so automatically. (semi-CDN-like)