Recently, Microsoft released the new MVC 4 in beta version, this release works with VS2010 and .NET 4.0 which is also compatible with the previous MVC versions.
The new version supports build and deploy to production apps, through its “go-live” license. Here are the features that the new MVC 4 taunts.
The ASP.NET MVC 4 Beta includes a bunch of great new features and capabilities. Some of the highlights include:
- Bundling and Minification – ASP.NET MVC 4 includes the new bundling and minification support we are also adding to ASP.NET 4.5. These features enable you to build web applications that load faster and feel more responsive to users, by minimizing the number and size of HTTP requests that your pages make. Included with the MVC 4 beta are new “cache busting” helper methods that enable easy proxy caching of bundled files (with automatic invalidation if you change the cached CSS or JavaScript). You can learn more about bundling and minification from my previous blog post about it.
- Database Migrations – ASP.NET MVC 4 includes the new Entity Framework 4.3 release, which includes a bunch of great new features. One of the most eagerly anticipated features it provides is database migration support. This enables you to easily evolve your database schema using a code focused migration approach – and do so while preserving the data within your database. I’ll blog more about this in the future – you can also see a walkthrough of database migrations in this tutorial.
- Web API – ASP.NET MVC 4 includes some fantastic new support for creating “Web APIs”. This enables you to easily create HTTP services and APIs that can be programmatically called from a broad range of clients (ranging from browsers using JavaScript, to native apps on any mobile/client platform). The new Web API support also provides an ideal platform for building RESTful services. I’ll be blogging much more about this support soon – it is really cool, and opens up a bunch of new opportunities. There are several tutorials, samples and screencasts covering ASP.NET Web API on the ASP.NET site to help you get started.
- Mobile Web – ASP.NET MVC 4 includes new support for building mobile web applications and mobile web sites, and makes it much easier to build experiences that are optimized for phone and tablet experiences. It includes jQuery Mobile, and includes new support for customizing which view templates are used depending upon what type of device is accessing the app. See the ASP.NET MVC 4 tutorial series.
- Razor Enhancements – ASP.NET MVC 4 includes V2 of our Razor View engine. Razor V2 includes a bunch of juicy enhancements that enable you to make your view templates even cleaner and more concise – including better support for resolving URL references and selectively rendering HTML attributes.
- Async Support and WebSockets – You’ll be able to take advantage of some additional language and runtime capabilities when using ASP.NET MVC 4 with .NET 4.5 and VS 11. Async support is one of the big ones, and the ASP.NET MVC runtime support for this combined with the new C#/VB async language enhancements (which are super elegant and clean) is going to enable you to write incredibly scalable applications. You will also be able to take advantage of the new WebSocket support built-into .NET 4.5 to build applications with even richer browser/server communication.
To install MVC 4.0 today click here
So you have a new project that you are working on, and you wanted this to be part of the open-source community, where do you host it?
We all know that projects can be a living and breathing, and since it’s open-source we wanted to share the code so that other skilled people such as yours are able to contribute to your masterpiece. Google Projects allow you to do this using their repository, here’s a quick “get started” link from Google.
http://code.google.com/p/support/wiki/GettingStarted#Working_with_your_Project
You can also contribute to other project that you find worthwhile.
Know your Limits.
“In SharePoint Server 2010, there are certain limits that are by design and cannot be exceeded, and other limits that are set to default values that may be changed by the farm administrator. There are also certain limits that are not represented by a configurable value, such as the number of site collections per Web application.”
Since I’m only interested in Web apps, here’s the limit that MS assigned to Web apps:
| Limit |
Maximum value |
Limit type |
Notes |
| Content database |
300 per Web application |
Supported |
With 300 content databases per Web application, end user operations such as opening the site or site collections are not affected. But administrative operations such as creating a new site collection will experience decrease in performance. We recommend that you use Windows PowerShell to manage the Web application when a large number of content databases are present, because the management interface becomes slow and difficult to navigate. |
| Zone |
5 per Web application |
Boundary |
The number of zones defined for a farm is hard-coded to 5. Zones include Default, Intranet, Extranet, Internet, and custom. |
| Managed path |
20 per Web application |
Supported |
Managed paths are cached on the Web server, and CPU resources are used to process incoming requests against the managed path list.Exceeding 20 managed paths per Web application adds more load to the Web server for each request.If you plan to exceed twenty managed paths in a given Web application, we recommend that you test for acceptable system performance. |
| Solution cache size |
300 MB per Web application |
Threshold |
The solution cache allows the InfoPath Forms service to hold solutions in cache in order to speed up retrieval of the solutions. If the cache size is exceeded, solutions are retrieved from disk, which may slow down response times. You can configure the size of the solution cache by using the Windows PowerShell cmdlet Set-SPInfoPathFormsService. For more information, see Set-SPInfoPathFormsService. |
| Site collection |
250,000 per Web application |
Supported |
The maximum recommended number of site collections per Web application is 250,000.Note that this limit is affected by other factors that might reduce the effective number of site collections that can be supported by a given Web application. Care must be exercised to avoid exceeding supported limits when a container object, such as a content database, contains a large number of other objects.For example, in a farm that contains a large number of Web applications, the total number of site collections might reach a number that cannot effectively be supported by farm resources. This can be true even when both the number of Web applications per farm and the number of site collections per Web application fall within their supported limits.
Similarly, if a farm contains a smaller total number of content databases, each of which contains a large number of site collections, farm performance might be adversely affected long before the supported limit for the number of site collections is reached.
The following case illustrates this point.
Farm A contains a Web application that has 200 content databases, a supported configuration. If each of these content databases contains 200 site collections, the total number of site collections in the Web application will be 40,000, which falls within supported limits. However, if each content database contains 2,000 site collections, even though this number is supported for a content database, the total number of site collections in the Web application will be 400,000, which exceeds the limit for the number of site collections per Web application. |
