0

The problem I was initially trying to solve is explained in this post.

tl;dr: multilingual website, redirecting to translated .cshtml views depending on the language.

Azure was treating the view re-routing differently in the case of Home/Index, so I made patch to solve that (see own-answer in previous post).

Current problem: I thought it was solved, but it was just because the css was cached. Now it is a mess, that is to say: the routing of the css elements seems to have changed after deploying to Azure. Again: this can not be reproduced in localhost.

Anybody has any idea about how to deal with this seemingly undebuggable differences between localhost tests and Azure?

Improve this question
3
  • 1
    Do you use bundles? Are the CSS files not retrieved at all or are the URLs in the CSS files wrong? Commented Feb 5, 2016 at 13:50
  • @Markus These are the console errors after deployment: i.imgur.com/WSPSqkM.png . Commented Feb 5, 2016 at 13:55
  • 1
    The errors might be related to bundling. The bad thing is, that bundles are usually disabled when debugging so that errors will appear only in a release build. In order to activate bundling also in the debug version, see this post: stackoverflow.com/a/16030958/642579 This should help in finding the reason. Commented Feb 5, 2016 at 16:16
Load 6 more related questions Show fewer related questions

0

Reset to default

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.