ASP.NET MVC 3 in production? - production

Now that ASP.NET MVC 3 is in beta, and ready for "go-live". Would it be safe to use in project, although not prevented I am curious on security, performance and ease of upgrade to release version.

I started using it in a project, but I couldn't get Dependency Injection working (using Unity). I was liking Razor, but the lack of intellisense did hurt my productivity.
I am sticking with MVC 2 for now. When this is more documentation on Razor available, I will probably upgrade to 3.
EDIT:
Check out this article. If you don't care about DI, then you might be all set. The only other change was the validation model.

Related

grails 2 / groovy 2 / JDK7: how to reap the benefits?

I really love Grails but I was wondering how to get the performance benefits of Groovy 2.
The question is how to configure the development and production environments in order to get that "close to Java" performance boost.
So, if I setup:
* JDK 7
* Groovy 2 (indie JAR to use invokedynamic)
* Grails 2.2
are there any guidelines in order to really speed my webapp out-of-the-box?
And do I need to do any re-factoring in my Grails webapp codebase? I mean that dependency injection stuff like referencing services in controllers should be statically compiled or should I keep writing code as the docs say?
ps: I guess Groovy #CompileStatic and Grails might be a relevant question...
It depends on what might be slowing your web application down :) I know "it depends" is so often the answer, but it's still true.
Anyway, I've asked around and it seems that Grails and invokedynamic won't go together just yet. The reloading agent needs updating and there may be problems with the cglib/asm libraries used by Hibernate.
Regardless, internally Grails is making more and more use of #CompileStatic (for the stuff that wasn't already written in Java), so unless your app is doing a lot of work itself, you're unlikely to see a big boost with invokedynamic.
It would be useful to have some official information on this, but it's not out there right now.

is DWR (direct web remoting) a dead project?

Is DWR a dead project? It does not appear to be under active development. The latest 3.0 release appears to be stalled. I'm specifically wondering if there are going to be maintenance releases of DWR 1.x or 2.x or is 3.0 is ever going to be released.
BTW. I asked this question on one of the DWR mailing lists and did not get a response.
Well, the 3.0 version is taking a while to get released, but it is nonetheless very stable.
We are using it in our production environment and we do did encounter any issue so far (2+ years in use).
Important issues on 2.0.X are fixed BTW. (seems that currently there are no major issues on 2.0.X).
BTW. I asked this question on one of the DWR mailing lists and did not get a response.
We had issues before (other version) and those were handler very quick.
Update Dec/2015: V3.0.1 released
Seems like it, I have used DWR like a year back and there is no release since then.
Their version 3 is still on RC (release candidate) and from my understanding of versioning, it is not stable or a general acceptance.
I would say move on... pass DWR. Pass Java too if you can ;)

How many changes have been made in Rails 3.2.1?

I started learning Rails recently. When I read Agile Web Development with Rails (4th Edition), some code is different in Rails 3.2.1. For instance, the JavaScript source is no longer in the public folder. Are there any important changes and what is their impact?
Thats the asset pipeline. A lot has changed. Most of them were introduced in 3.1
Checkout for a lot of the general ones in
http://guides.rubyonrails.org/getting_started.html

Spring Web Flow 3 Development Abandoned?

Does anyone have any information on Spring Web Flow 3 status?
Here are a few relevant links that support my sense that springsource has essentially abandoned the project:
1)Official roadmap indicates they are missing milestones by over a year now with no update to the roadmap.
2)Forum thread filled with these questions ignored by Keith Donald and Spring team.
3)Official Download page says the latest release is 2.2.1 but is actually 2.3 so that is not even being kept up-to-date anymore.
While Web Flow version 2 I'm sure is a great product, the issues above are all obvious red flags when it comes to evaluating an open source product -- as well as evaluating the company behind that project. Am I simply missing some communication channel where all this has been discussed in detail before? I find it hard to believe that springsource, a company that seemingly had their act together, would be this negligent with one of their flagship products.
They just added a graphical web flow editor into STS. See this InfoQ post. Also, I just checked JIRA and Fisheye and it looks like there's bug fixes going into a 2.3.1 coming that corresponds with Spring 3.1. So I don't think it's abandoned, it's just not getting new features.
Just wanted to mention that the latest version (2.3.1) of Spring Web Flow was released on Mar 27, 2012. See the changelog file: http://static.springsource.org/spring-webflow/docs/2.3.x/changelog.txt

Which projects do you include in your solutions

How do you commonly lay out your solutions in Visual Studio? Recently, I've kept the BLL, DAL and presentation in different classes and planned to add a test solution as I learn TDD. However, after recently watching a video from Rob Conery and viewing a project from an external contractor, I noticed a theme of multiple projects in the solution.
The projects included in the solution were:
Infrastructure
Model
Web
Tests
SQL Repository
Is this something new or a design technique suggested for MVC? Can anybody tell me more about this design?
First, you need to understand Rob's coding habits. He uses an MVC-esque approach to development (if not pure MVC) and uses his ORM SubSonic.
The use of MVC is the reason for the "Model" class, since SubSonic 2.1 contains Migrations, he is using the SQL Repository for those migrations, so that he can version his DB.
Tests and Web are self-explanatory, which only leaves the Infrastructure, and your guess is as good as mine, though it could be the "Controller" of the MVC pattern.
It all depends on the pattern that you're using, your own preferences for separation of concerns, and your comfort level developing multiple projects at once.

Resources