I googled this until my eyes bled. I can't find what's causing it to save my life.
I'm using MVC4 with KendoUI HTML5 Framework; one of the 2015 editions. Everything's .min so I can't find the exact version.
On development, Kendo UI icons show fine.
On a VM I created to test deployments, Kendo UI icons show fine.
On the customer's network in production, Kendo UI icons do not show.
On the customer's network, you can navigate to the location of the icon sprite file successfully (no 404 error)
Bootstrap icons show normally in all cases. It's only the Kendo UI icons.
Dev means there's no inherent problem with the icons or CSS. The VM deployment working fine means it is most likely not an MVC bundling problem--I'm using the following solution for the bundling issue.
.Include("~/Content/kendo/kendo.bootstrap.min.css", new CssRewriteUrlTransform())
I have absolutely no idea what is different on my customer's network that causes KendoUI icons not to display. I'm baffled, and--as always--unbelievably grateful for any help you all can give.
For a start, you can disable bundling on production, to see if it is related to the problem.
On the other hand, with bundling enabled, there should be some 404 error in the browser console when the sprite file doesn't load - I suggest checkng what the request URL is in that case, and compare it with the working URL when you access the sprite file directly.
Also check this thread that may be applicable:
CssRewriteUrlTransform with or without virtual directory
In my case the icons were not copied over to production. I copied the kendo sub folder from contents folder to the corresponding folder in production and that solved it. Visual Studio 2010 MVC 3. No bundling used.
Related
I'm working on an ASP.net web app. I needed to make some changes to the CSS, but I ended up having to jump thru some hoops because the previous developer who worked on the app had minified all the CSS files in the source repo.
I decided to make things easier for myself in the future by setting up ASP.net bundling and minification. It turns out that for some reason, ASP.net throws errors when trying to minify CSS for Bootstrap 3.3.5, Kendo UI v2017.2.504 (specifically kendo.common-material.css), and Material Dashboard Pro v1.1.0. I get the error Minification Failed. Returning unminified contents.
I tried minifying these files with cssminifier.com and they appear to work fine, so I'm at a loss to explain why I get an error when minifying with ASP.net.
I'm trying to develop a real estate web app. I downloaded html/css theme from envato and they look great locally... not so much on my express server (running on my host machine).
I get this error
As soon as I take out
"var bootstrap = require('bootstrap');"
my website loads but website layout is off. Anyone else experience this problem before?
Require is a built-in function for Node.js to load modules. See What is this Javascript "require"? for more info about require.
But in short when you remove var bootstrap = require('bootstrap'), you are not allowing your code to access the bootstrap module thus removing the bootstrap styling for the app.
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
If you create a new ASP.NET Core Web Application in Visual Studio 2015 and run the stock standard template app, all the tags (title, link,meta) that have been added to the head tag are rendered in the body? Why is this happening?
This seems to be an issue caused by having Browser link enabled.
I am not sure if this is an issue with the latest version .NET Core or if it is intentional.
#jar, have you tried it on a different machine or tried different browsers? My quick answer would be "no, I haven't seen this happening" and in response to #Daxxy's observation on Browser Link: "I don't see it happening with Browser Link either".
Long answer, with screenshots:
I haven't noticed this behavior before, so I installed RC2 on a laptop that I'm currently on, which didn't have RC2 installed it before. I can verify that I do not see the observations that you are experiencing.
Here's my _Layout.cshtml for the standard RC2 web template project:
Note the meta tags and title tag within the head region.
Now, here's the browser source that reflects the same thing that's in the source code.
To test out #Daxxy's observation, here's my toolbar menu that shows that Browser Link is enabled:
Finally, here's a screenshot that shows my Browser Link Dashboard verifying 1 connection to Edge.
If you're still facing this issue on more than one machine with more than one browser, make sure you contact the ASP .NET team with your observations, to check if this is some sort of intentional behavior or a bug.
My team and I are currently developing an application for both Android and iOS using ASP.NET MVC 4, HTML5, and PhoneGap. The development works perfectly fine; however, one question remains unanswered: What is the recommended approach to generate the three files PhoneGap needs (one HTML page, one JavaScript file, and one CSS stylesheet) from our MVC solution?
Would you recommend using a Razor template-based approach? Or would you simply automatically copy the output HTML source after each build? Or would you suggest something completely else?
This morning, we decided to let ASP.NET MVC render a single view containing all our application's HTML which references several JavaScript files and CSS stylesheets. We then automatically grab the rendered HTML source and copy an index.html into a certain export folder on our local machine. That folder is ready to be deployed because it contains only one HTML file and additional JavaScript and CSS resources – exactly what PhoneGap expects.