Hi,

I am not sure I can use the MVC on .NET 3.0.

Thanks,

3.5 SP1 is best ... it's possible to do what you want, example:
http://www.hanselman.com/blog/DeployingASPNETMVCOnASPNET20.aspx.

is there a reason you do not want to do this?



Regards,
Gerry (Lowry)

3.5 is the minimum required for the runtime, but 3.5 SP1 is recommended.  If you want Visual Studio design-time support, Visual Studio 2008 SP1 is required.  See http://haacked.com/archive/2009/03/03/aspnetmvc-changes-for-rc2.aspx for more info.

It's possible to make MVC run on 2.0 SP1, but it's not supported or recommended and risks destabilizing your machine.  See the link in Gerry's post for more info.

Thank you for your replies. You have answered my question.

I guessed the same, but nice to check with experts.

My client has .Net 3.0 on the production servers and they do not want to install 3.5 SP1 or 3.5. I really want to code this app in MVC, and I have already created a prototype on my dev image. Works great and it is clean code. Thanks to examples of NerdDinner and experts blogs.

PANKAJ11, have you tried selling the benefits to your client?:

  see http://msdn.microsoft.com/en-us/library/cc713697.aspx
        "What's New in the .NET Framework Version 3.5 SP1".
SP1 has been out for over half a year already,

also:  http://msdn.microsoft.com/en-us/library/bb332048.aspx
         "What's New in the .NET Framework Version 3.5".

Microsoft is moving forward; the rest of the world is moving
forward with Microsoft.  For people who do not want to
be on the bleeding (sic) edge, a SP1 is usually a good
time to join in.

New Microsoft technologies and improvements to
existing ones will build on the latest stable versions.

Third party products and tools will also build on the
latest versions of the .Net Framework, example Moq.
While tools and products built with 3.5 may have been
designed to also work with prior versions of the .Net
Framework, that is no justification of living in the past.

Installing .Net 3.5 will not likely break your client's
production server, assuming your client is competent.

You may want to remind your client that any important aspect
of the .Net architecture is that it was designed to avoid .DLL hell.

Regards,
Gerry (Lowry)

@ PANKAJ11 :   P.S.:   levib is the expert; I've got a long way to go.   g.

Excellent points. I agree with you completely. I will try to sell, but still I am a coder, not a business person. So to articulate is hard part, the easy part is coding. :-)