Skip to main content

A first look at Microsoft ASP.NET MVC 3 Beta

First beta version of Microsoft ASP.NET MVC framework 3 is ready to be downloaded from here and announcement from Scott Guthrie's blog. Significant changes have already been made to this version. You can go through the release documentation to have detail information on the new changes that are available with this release.

One of the newest edition is the "NuPack Package Manager". If you are a ruby developer, then it will not be a real ground-breaking idea as you are already using RubyGem from the first day of your ruby development career. For .NET platform it's comparatively newer concept. There are few other open source project already available for the same purpose. But there is always a better expectation associated with something from Microsoft itself from developers point of view. To read more on NuPack refere to the this article from Scott Hanselman. With this release Microsoft is going to make integration of third party libraries with .NET easier.

The new view engine "Razor" is really cool!! Syntax is much cleaner now for view. Though the C# syntax was available from first preview version, now VB support is also in built. However, previously it was possible to use VB code but had to activate it manually. I am pretty excited with this view engine. But unfortunately the intellisense support is not yet ready for "Razor". Waiting for it...:) If you want to read more on this I will recommend Scott Guthrie's blog post on Razor.

There is an interesting new support for running code before views run for any particular view folder. If you want to set something default to all views, its extremely useful. The file that will be used for this purpose is named _viewstart.cshtml (C# code) or _viewstart.vbhtml (VB code). For example if you want to set the default layout for all views for a particular directory and its sub-directories you can set the layout code here. And it will run before running any view file within that directory.

There are bunch of other improvements including new helper methods, better dependency injection support, unobtrusive javascript support and many more.

Comments

  1. Microsoft is going towards right direction with ASP.NET MVC. Nice post...thanks

    ReplyDelete

Post a Comment

Popular posts from this blog

The contents of the feature's solution requires the Solution Sandbox service to be running

If you are developing any Sandbox solution for Sharepoint 2010, then you may have faced an error while deploying any solution to your development server. The error in Visual Studio 2010 output window looks like this generally:
Error occurred in deployment step 'Activate Features': This feature cannot be activated at this time. The contents of the feature's solution requires the Solution Sandbox service to be running.

The fix is simple. You must make sure that your "Sharepoint 2010 User Code Host" service is running. It is disabled by default installation. So, you have enable and run it. If you want to deploy the solution, then again you see the same error output. Actually, you have to make sure that this service's status is active in Central Administration Site. To see the status go to your Sharepoint 2010 Central Administration Application. Under System Settings > Manage services on server make sure that "Microsoft SharePoint Foundation Sandboxed Code…

Can not install Devise gem with Ruby 1.9.2 on windows

I was having a try out of devise gem with one of my Rails 3 pet project just yesterday. I installed Ruby 1.9.2 with the one-click installer from rubyinstaller.org and the latest Rails 3.0. But I faced installation problem as usual on windows. The problem was that it was not being able to build its native extensions.
After some research I found out the solution at http://github.com/oneclick/rubyinstaller/wiki/development-kit. What I was missing is development kit. I just followed the instruction and it was solved and installed devise with my Ruby 1.9.2 correctly.
But I am not sure whether it will work with Rails 3's bundle install command or not. I installed the gem from command line using the command gem install devise --platform=ruby before installing all the required gems with bundle install command . The last parameter platform is a must as it will temporarily use the DevKit to build native extensions. That's it.

Running ferret server with mongrel and shared index folder

If you are using acts_as_ferret plugin for searching in your rails application then you must have faced some issues with indexing or running ferret server on your production server. In this post, I will share with you some tips about running and maintaining ferret server: Running ferret server on productionSharing your ferret index folderWrite a simple script to re-index all your data

Running your ferret server
If you have multiple instances of mongrel running in your production, then you must need to run the ferret server to handle situations when multiple processes are updating ferret index at the same time. If you want to run ferret server in your production server, then at first you have to open the port you set in ferret_server.yml of your config directory on the server you want to run it. acts_as_ferret comes with a built-in drb server which uses dRuby protocol. So, you should remember to open the port with other protocol (not http or something else). One very important thing is t…