|
William Emmanual wrote: I have been asked to upgrade my entire team to "MVC ready" in 15 days!
What is the rationale for doing so?
I started looking at MVC5 about a week or 2 ago and have been 'experimenting' with it on and off and it doesn't appear too difficult: it's just making the transition to a new way of doing things that takes a little time.
I'm sure that as I get deeper into a 'proper' application I will be googling and cping quite a bit!
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
Those who seek perfection will only find imperfection
nils illegitimus carborundum
me, me, me
me, in pictures
|
|
|
|
|
There is a difference between being "MVC ready" and "MVC proficient." MVC is one of those things where it can be quite a nightmare if the software designed wrong (in other words MVC done badly is much worse than no MVC at all.) Besides, isn't MVVM the big thing now?
|
|
|
|
|
Joe Woodbury wrote: Besides, isn't MVVM the big thing now
Where would you apply MVVM to a web technology now that Silverlight has been deprecated?
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Use KnockoutJs for your ViewModel
HTML for your view
POCO for your Models
and web services accessed via Ajax to stich them together
NO need for any of that Web Forms or MVC rubbish
MVVM # - I did it My Way
___________________________________________
Man, you're a god. - walterhevedeich 26/05/2011
.\\axxx
(That's an 'M')
|
|
|
|
|
I presume the magic is in the KnockoutJs, we are going to use Kendo for the View
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I don't know much about Kendo (but may well be investigating soon so keen to hear any thoughts)
Knowckout really just allows you to create a viewModel in JS and bind it to, well, whatever you want in your HTML.
So, simplistically, your HTML tags have bindings specified, you grab some JSON using AJAX, create a Knockout object from it and then yes, the magic happens - two-way binding to your viewmodel.
ANd you can use it with Kendo[^]
If you haven't looked at it before, I would recommend looking at knockout, as it makes client-side logic much easier (IMHO) than some of the messiness you can get into trying to do it yourself in JS
ONe day, when I have a few days, I will write an article on all this stuff to show how poerful and easy it is - meanwhile SuperLloyd has written an article [^]covering some of this stuff, which I only discovered 10 minutes ago myself!
MVVM # - I did it My Way
___________________________________________
Man, you're a god. - walterhevedeich 26/05/2011
.\\axxx
(That's an 'M')
|
|
|
|
|
William Emmanual wrote: I have been asked to upgrade my entire team to "MVC ready" in 15 days
If you have previous experience with web programming and .NET, 15 days should be more than enough.
|
|
|
|
|
Yes I do.
Learning all the way...
|
|
|
|
|
And continue to do the jobs you are currently involved in full time I suppose. Is this person going to give you 3 weeks full time commitment to learning and is he going to fund the resource to help.
I think it will depend where you are coming from, if you are currently in ASP.net/javascript/CSS then it should be achievable. We are coming from Silverlight and xaml so the learning curve is dramatically greater.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Try the nerd dinner tutorial. It's the "Hello World" for ASP.NET MVC. It was written with MVC 1.0, but should still work nicely. It's how I learned, and the concepts are really nice and clear. Also, Nerd Dinner is maintained at codeplex.com, where you can, after taking the tutorial, take a look at how the enhancements since MVC 1 have come into play. The Nerd Dinner tutorial can be found here: http://aspnetmvcbook.s3.amazonaws.com/aspnetmvc-nerdinner_v1.pdf[^] You should be able to complete it within a day or two and have a great foundation for being MVC ready.
|
|
|
|
|
Thanks for sharing. I have shared with my team
Learning all the way...
|
|
|
|
|
I've spent a lot of time on MVC3/4. A few people have suggested the pluralsight tutorials, which are a good intro, particularly Scott Allen's series. However I have to sound a rather negative warning in that I do not believe that it is possible to get proficient in MVC in 15 days and that this is asking for problems. The reason I say this is MVC is only the architecture. The real expertise is required when you start doing slightly more complex things with data and this is where a deep knowledge of EF including LINQ (either SQL or Entities) is essential. Also a good understanding of which pathway you are going to follow e.g Code First, Model First or database First. If you don't understand the full implications of EF and which Code pathway you choose you will wander around in circles. Also your model structure is heavily tied into all these choices. This knowledge only comes with actual experience.
I would seriously recommend getting an MVC Guru to work with your team as the team leader and allocate specific parts of the work with the Guru providing full time assistance.
|
|
|
|
|
I know that makes rational sense, I haven't really known any MVC expert. I can get my HR to scout for someone.
Learning all the way...
|
|
|
|
|
Try this structured curated guide: http://webdev.simple-talk.com/[^]
It's been put together by a few members of the .NET community including a colleague of mine from Red Gate.
|
|
|
|
|
Here[^] is a free tutorial from Scot Allen from Plural sight for MVC 4 - hope this helps a little. Good Luck !! 
|
|
|
|
|
15 days? I'd start polishing my resume now and then have a serious talk with whoever issued this ludicrous directive. I worked for a guy like that once, he wanted 2 completely tested new versions of our product (a large enterprise-level system) in 30 days. I called in the "white coats". The guy wasn't there too long after that one!
|
|
|
|
|
Join Pluralsight[^]
Their training is awesome, and they have an extensive list of videos on MVC.
No, I don't work for them, or have any ties to them, other than being a very happy customer of theirs for about 3 years now. It's helped me tremendously.
Of course, you'll pretty much have to devote full time to studying if you want to learn it that fast.
I have always wished for my computer to be as easy to use as my telephone; my wish has come true because I can no longer figure out how to use my telephone - Bjarne Stroustrup
The world is going to laugh at you anyway, might as well crack the 1st joke!
My code has no bugs, it runs exactly as it was written.
|
|
|
|
|
I love your quote from Bjarne, petty much sums up my expertise with my telephone. I want my telephone to send and receive calls. It took me a while to figure out how to send and figuring out how to receive was easy, but still took time to figure out how to touch it the "right" way or put it on speaker or how to send a call. I almost miss calls because I don't touch it right.
The phone messaging tab still tells me I have to set up messaging, while figuring out one arcane symbol leads me straight to it, already set up from my last phone.
I also see you've adopted MS' stand: "It's NOT a bug, it's a FEATURE!". Funny how often, when they go to a new release, the FEATURE is dropped. (Without mentioning they removed it.) You'd think that when they go to a new release they would want to expand and increase the effects of their past FEATUREs.
|
|
|
|
|
KP Lee wrote: I love your quote from Bjarne, petty much sums up my expertise with my telephone.
Yeah, I agree. Haven't really even used half the 'features' of my phone. 
Honestly, I mainly got a fancy phone because, as a Web Developer, it's becoming a necessity to learn how to code for these darn things! I certainly don't need all that functionality. I'm one of those few people who actually use it mainly as a (*gasp*) phone. I know, amazing, isn't it? 
As for the 'my code has no bugs' quote, yeah, well. It kind of ties into the one before it about not taking yourself too seriously. Which I thoroughly believe. As a programmer, you pretty much need a good sense of humor to keep your sanity. That, and lots of ![Java | [Coffee]](https://www.codeproject.com/script/Forums/Images/coffee.gif) and ![Beer | [beer]](https://www.codeproject.com/script/Forums/Images/beer.gif) !
I have always wished for my computer to be as easy to use as my telephone; my wish has come true because I can no longer figure out how to use my telephone - Bjarne Stroustrup
The world is going to laugh at you anyway, might as well crack the 1st joke!
My code has no bugs, it runs exactly as it was written.
|
|
|
|
|
MVC ready to do what?
that's like asking someone to be drive Porsche ready.
if you collected a bunch of scrpit kiddies from the street it may take years to crack the basics. For a good programmer it takes days to be good at it.
modified 20-Oct-19 21:02pm.
|
|
|
|
|
It may be doable, given that they have experience on .NET or some technologies close to that, also of course assuming they will be given this 15 days to fully grasp the concept, otherwise, it's a pipe dream from management.
|
|
|
|
|
William Emmanual wrote: I have been asked to upgrade my entire team to "MVC ready" in 15 days!
Do nothing, but tell your manager you've succeeded.
If he/she is like most Management by Magazine Articletm types I had to deal with, and this sounds like one from that tribe, they won't be able to tell whether you have or not.
Just make sure your team drops MVC terms randomly into their conversations.
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
|
|
|
|
|
It depends where you're starting from on the learning curve. If you're just adding ASP.NET to an already impressive CV of talent, the answer is probably yes. If coming from a graduate Com.Sci. level, forget it and hire a new team with the required talent!
Being taught ASP.NET MVC in 15 days is not the problem. Being able to apply the new talent in a productive manner is a problem. I would suggest 6-12 months to be totally up to speed...
|
|
|
|
|
Have you looked at http://www.asp.net/mvc[^]?
It has tutorials on MVC (A programming pattern I hadn't heard or listened to if mentioned before.) and the differences between that and regular ASP.NET programming.
With a solid web design background behind me, I had no problem picking up ASP.NET, while most students were thrashing around, trying to figure out what the HTTP protocol was doing.
I've never touched MVC, but it is a pattern for C's sake.
I haven't reviewed the entire thread, so if I'm repeating what's been said, sorry. I did have a laugh on the Agile thread. (I think that was a dig at management that jumps on the newest bandwagon trend with no idea where it is heading or what it does. It's just the best thing to do, so learn it.)
On the flip side, management probably has no idea what MVC or ASP.NET are, so in 15 days you may be able to claim mastery and continue to figure out what MVC is, so when they get a clue, you may actually have mastered it.
|
|
|
|
|
Not sure if you are still reading the answers...
1) Assign 1 or 2 top dogs to drill in and learn MVC, your strongest bench players willing to master it
2) Become familiar with the core concepts yourself
3) Start the project in the most UNUSUAL way. By doing a lot more analysis of the customers needs.
Whatever process you are going to follow, start it, and start putting together what it is that you need to build.
4) Identify the proper metaphor for the software your are going to build, that will help frame it for everyone on the team.
Now, with a decent understanding of what your are going to build. The fact that you need a Model, a View and a Controller. Assign your team to write a DISPOSABLE version of the prototype. Group people into the teams, and the top 2 people from the beginning will work across the entire design.
Write it, make it work. Code Reviews. and a Solid Postmortem to review everything they have learned.
Now, do it again, from scratch. Throw it away.
Now, do it for the last time, and add everything in via iterations or whatever process you follow. I find that the cohesion derived from having a team work together, make something work, and then throwing it away and doing it a second and third time tends to produce BOTH a great product and a GREAT team.
Finally, DO NOT share these steps with management... They will NEVER UNDERSTAND!
Besides the goal is not to learn ASP.NET MVC in 15 days. The goal is to be able to start producing MVC using ASP.NET in 15 days, and even more importantly, to become very good at it in the long run. I think this should accomplish that.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
