Why differences the user interfaces, such as textbox, button, etc... between developing stage on local machine and IIS?When I'm developing with ASP.NET MVC 4 on my local machine, the user interface like below :
After I uploaded to server
How can solve this case? Please
Chances are that because one is rendering in the "localhost" domain that it is using IE's Compatibility View by default because it is considered to be an "intranet" zone. And the other is likely rendering from something that is considered to be in an "Internet" zone, so no Compatibility View by default.
Related
As the title suggests, we are tasked with running a custom .NET MVC application in a virtual directory under the client's Orchard CMS installation. Now, I've successfully done this type of thing in the past with two custom .NET MVC applications, but never with Orchard. Orchard does some unique things behind the scenes, so I do not believe it would be possible.
Two things:
1. I can't build a new Orchard instance from source.
2. It must be a virtual directory on the same domain for SEO purposes. Running the site on a subdomain is bad for Google rankings. Therefore http://www.example.com/myportal is good, whereas http://myportal.example.com is really bad.
Yes you can. While this isn't specific to Orchard, you're likely going to run into some issues with web config inheritance. Depending on the individual scenarios you face (such as shared assemblies but different versions...duplicate config nodes etc) you should be able to search around on stackoverflow and resolve those easily though.
Resource: Virtual directory inside Orchard web application
I was looking at the Kendo Grid local virtualization demo page and I noticed that the demo didn't include an example of an Asp.Net MVC server wrapper. Does that mean that there isn't one for the local virtualization mode of the grid?
Does that mean that there isn't one for the local virtualization mode of the grid?
In the local version, as the name implies, there's no need for a server. The data is stored inside a javascript variable and lives only on the client. I don't understand what server side wrapper are you asking about. All you need is a server that will send the correct markup to the client. From this moment on everything happens locally.
Is ASP.NET MVC intranet application intented only to be used as a Windows-domain based application or there's a possiblity to run it inside a workgroup?
Thanks!
The word Intranet has no correlation with any network operating system (Windows Domain, Workgroup, etc). How you build your web based application (using any language) is indifferent to who can access it. So to answer your direct question, you can use ASP.Net MVC to build a website that can be accessed by anyone on a local network if you configure the website and/or hosting environment (IIS) in that manner.
MVC (Model View Controler) is a way to develop application (web + desktop) and can be used as Windows-domain App or inside a workgorup or without of both
is it possible to deploy asp.net MVC site on windows AZURE platform? I understand we can deploy a WCF service, but what about full site? Will it work? Will it scale (i.e. load balance)?
We're having a project to develop - a donation site, which will be advertised a lot and will receive a lot of traffic. I do want to try AZURE, but is it possible for AZURE to run the full asp.net mvc site?
Yes - you just need to make sure that MVC dlls are copied to bin folder and MVC project is added as a web role.
Here's a tutorial.
Also take a look here:
MVCCloudService
PS. Remember about Azure prices.
As others mentioned, MVC2 sites are totally OK for Azure. Your second question: will it scale (auto-balance) needs more explanation:
If you have more then one compute instance (VM) allocated to your application, MVC2 site will auto-balance provided you haven't made any mistakes with keeping session-information inside the URLs.
However, if you want to automatically adjust the number of compute instances per load on the site, you will either have to write the scaling logic yourself (check this site to get started http://convective.wordpress.com/2010/10/12/autoscaling-in-windows-azure/ ) or use a third-party scaling engine like # http://www.paraleap.com/
HTH
As a dev team, we're looking to switch to asp.net MVC and I've heard rumors about IIS 6 not being able to support all of the MVC functionality. Is this true? Is there any official set of functionality supported in IIS 7 vs IIS 6? Should we completely avoid running it on IIS6?
You do not loose any functionality of ASP.Net MVC; however, you have one of two options. You can either define an extension on your URL's which will allow you to set up mapping. So for example:
www.example.com/books/computer/list
might become:
www.example.com/books.mvc/computer/list
You can use any extension you want so long as you map to ASP.Net. I am currently using .aspx which meant I could avoid changing IIS configuration at the sacrifice of having extensionless URLs.
The other option as mentioned is using a wild card mapping. What this does is route all requests to ASP.Net. Even requests for static content such as images. This does have a negative effect on performance that you will want to measure. There are ways around this, I believe such as placing all your content in a specific virtual directory that you turn off the wild card mapping for, but I haven't fully explored that option.
I think the issue with IIS6 is extensionless URLs that you can easily achieve by adding a wildcard ISAPI map in IIS configuration.
So, no. While I love IIS7 integrated mode and strongly recommend using it, you won't lose functionality using it. I've deployed several ASP.NET MVC 1.0 projects on Windows Server 2003/IIS6.
Url rewriting can help you to solve the problem. I've implemented solution allowing to deploy MVC application at any IIS version even when virtual hosting is used.
http://www.codeproject.com/KB/aspnet/iis-aspnet-url-rewriting.aspx