[RESOLVED]Webmatrix here to stay ?

Hi,

i’m about to build a large project, that will be live for years, and I chose the asp.net environement, and specifically webmatrix web pages as my development stack, as it seems the best compromise between power and ease of use.

Do you know the plans from microsoft with webmatrix ? Will they support it for the years to come, develop new versions….. I would hate working on that project, to learn discontinuation of the product in favor of MVC only.

Please advise,

Thanks,

Brakkar

Brakkar

Hi,

i’m about to build a large project, that will be live for years, and I chose the asp.net environement, and specifically webmatrix web pages as my development stack, as it seems the best compromise between power and ease of use.

Do you know the plans from microsoft with webmatrix ? Will they support it for the years to come, develop new versions….. I would hate working on that project, to learn discontinuation of the product in favor of MVC only.

Please advise,

Thanks,

Brakkar

In short, the ASP.NET Web Pages (Razor) coding framework is getting continual updates however Webmatrix seems to be neglected.

You can look at getting started in Webmatrix then perhaps when you are comforable, move over to
VS Studio for Web (http://www.visualstudio.com/en-us/products/visual-studio-express-vs.aspx). 

This has been discussed over here, if you wish to learn more about the fate of Webmatrix: http://forums.asp.net/t/1999455.aspx?Is+it+worth+to+invest+time+in+WebMatrix+projects+ 

If you wish to get started, here is a link to some great starting resources –

http://www.asp.net/web-pages

The community forums are really helpful as well, I strongly suggest the tutorials first and check out the sample templates bundled with Webmatrix!

Cheers!

There are two distinct issues here: one is WebMatrix and the other is the Web Pages framework. WebMatrix is purely a tool – a development environment. There is no official word from Microsoft on its future, but it has a number of bugs and no new releases
have been made for some time. At best, WebMatrix is on a back burner somewhere, although it feels like it has been silently dropped. If you are drawn to Web Pages because of WebMatrix, stop and try using Visual Studio Express for Web instead. You can use that
to build Razor Web Pages sites. 

Web Pages on the other hand is now on version 3.2.2 (although WebMatrix only supports version 2.0), and is actively being developed – although its mainly performance improvements and bug fixes these days. It will also form part of ASP.NET vNext, although
no details on that have been made available. Since Web Pages also forms the basis of the preferred view engine for MVC, there is no danger of the framework being discontinued.

Ok, glad I asked, thanks for your answers.

i just downloaded VS 2013 and will use that from now on. So to create an MVC project, I must "create a new project", and to create an new Web Pages project, I must "create a new web site (with razor 3)" right ?

Also, can you please clarify what SQL should I use… i read that some sql of webmatrix will be discontinued. I ask this in the context of hosting it on Azure.

Brakkar

So to create an MVC project, I must "create a new project", and to create an new Web Pages project, I must "create a new web site (with razor 3)" right ?

Correct.

Brakkar

i read that some sql of Webmatrix will be discontinued

That’s SQL Compact  Edition (SQL CE) and yes, it is being deprecated. Use SQL Server.

For me the WebMatrix silent death confirms again that Microsoft appears not to consider the cost of ownership of their products.

Developers and users of their products invest a lot of time migrating to a new product and expect a certain amount longevity and active support.

The webPages team is leaving the developers hanging, cannot even bother to tell us what is going on.

This is not the first time that his happened to me, two previous examples are Office Accounting and Office Sharepoint Server 2007.

At least Google has the decency to inform their users when something is discontinued and why.

The new CEO is focusing his efforts on getting Microsoft to react quicker, but that is only part of the problem.

I feel that Microsoft’s objective was to make it easier for developers of PHP, classic ASP, Coldfusion, and similar programming languages to transition to ASP.NET.  It worked for me.  I now use Web Pages exclusively for all new development. I am happy to
see that Microsoft will have Web Pages in vNext.  Hence I personally feel safe with developing using Web Pages and would recommend it to others.

 

Leave a Reply