Can anyone or anything teach me ASP.NET MVC in 15 days?
-
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
-
No seriously! I have been asked to upgrade my entire team to "MVC ready" in 15 days! :confused: So any and all help will be appreciated!
Kind Regards, - Will william@enziq.com www.enziq.com
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
-
No seriously! I have been asked to upgrade my entire team to "MVC ready" in 15 days! :confused: So any and all help will be appreciated!
Kind Regards, - Will william@enziq.com www.enziq.com
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.
-
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')
-
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 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')
-
No seriously! I have been asked to upgrade my entire team to "MVC ready" in 15 days! :confused: So any and all help will be appreciated!
Kind Regards, - Will william@enziq.com www.enziq.com
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.
-
No seriously! I have been asked to upgrade my entire team to "MVC ready" in 15 days! :confused: So any and all help will be appreciated!
Kind Regards, - Will william@enziq.com www.enziq.com
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.
-
I jumped in my first MVC 4 project without any special preparations. My colleague was already a bit familiar with the framework and he started to work on the project alone, but due to circumstances he couldn't make the deadline so I was called in to help out where I could and finish. He explained the basics and I also found some tutorials online. Both of us made some mistakes, most common mistake was not following naming conventions (which is btw really important if you want to take full advantage of the framework). At the end it turned out okay. It wasn't a frustrating first experience and it didn't take long before it felt right. Also, to jump in an application that was already partly finished helped a lot because you have some examples from which you can build on.
.
Hello, If your team is familiar with rich javascript application, then they will have not that much trouble. The link http://www.asp.net/mvc[^] which was already posted in this discussion is a very good resource. Again, if they are quite familiar with Javascript/JQuery they will be fine. IF they are not familiar with that, well... then you´re in trouble...
-
Do a quick meeting with your team, see if everyone is willing to learn the new concept. Once everyone agrees, I am sure your team could learn the concept of MVC in few days, and after that they should work on a very small project using MVC (it is very important, not just jump in after only reading and watching stuff, you need to try it out). And after 15 Days, check where everyone stands and then, you all can just jump in with the new Project that your Client/Boss wants with extra days of buffer in the timeline. It is lot of work, but it's possible. And if you think that after 15 days of trying, the whole thing is not working, just say 'no' with facts and reasons. People respect when you say 'no' with proper justification. IMHO: for learning, read a book. It's OK if you don't read the whole book and only first few chapters. But before you start watching videos, you should read a book. You should learn the basic concepts thoroughly and only a book can teach you in a detail. Good luck. :)
Remind Me This - Manage, Collaborate and Execute your Project in the Cloud
Thanks a bunch, have been putting my peeps through the rigor. Reading online as and when we encounter problems. Asp.net makes it as difficult as possible to learn simple things, but yea we have been getting along.
Learning all the way...
-
I jumped in my first MVC 4 project without any special preparations. My colleague was already a bit familiar with the framework and he started to work on the project alone, but due to circumstances he couldn't make the deadline so I was called in to help out where I could and finish. He explained the basics and I also found some tutorials online. Both of us made some mistakes, most common mistake was not following naming conventions (which is btw really important if you want to take full advantage of the framework). At the end it turned out okay. It wasn't a frustrating first experience and it didn't take long before it felt right. Also, to jump in an application that was already partly finished helped a lot because you have some examples from which you can build on.
.
Thats comforting. I am counting on my good luck.
Kind Regards, - Will william@enziq.com www.enziq.com
-
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...
-
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...
-
No seriously! I have been asked to upgrade my entire team to "MVC ready" in 15 days! :confused: So any and all help will be appreciated!
Kind Regards, - Will william@enziq.com www.enziq.com
-
No seriously! I have been asked to upgrade my entire team to "MVC ready" in 15 days! :confused: So any and all help will be appreciated!
Kind Regards, - Will william@enziq.com www.enziq.com
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!
-
Thanks a bunch, have been putting my peeps through the rigor. Reading online as and when we encounter problems. Asp.net makes it as difficult as possible to learn simple things, but yea we have been getting along.
Learning all the way...
You could give each team member an area to specialise in once they've covered a certain amount of basics. Then have them give a presentation each - on learning resources as well as how-to's...
-
Do a quick meeting with your team, see if everyone is willing to learn the new concept. Once everyone agrees, I am sure your team could learn the concept of MVC in few days, and after that they should work on a very small project using MVC (it is very important, not just jump in after only reading and watching stuff, you need to try it out). And after 15 Days, check where everyone stands and then, you all can just jump in with the new Project that your Client/Boss wants with extra days of buffer in the timeline. It is lot of work, but it's possible. And if you think that after 15 days of trying, the whole thing is not working, just say 'no' with facts and reasons. People respect when you say 'no' with proper justification. IMHO: for learning, read a book. It's OK if you don't read the whole book and only first few chapters. But before you start watching videos, you should read a book. You should learn the basic concepts thoroughly and only a book can teach you in a detail. Good luck. :)
Remind Me This - Manage, Collaborate and Execute your Project in the Cloud
Rutvik Dave wrote: And if you think that after 15 days of trying, the whole thing is not working, just say 'no' with facts and reasons. People respect when you say 'no' with proper justification. In my opinion the best way to go is to warn your boss that it is not possible, explaining the reasons, the possible outcomes and some alternative solutions. Good bosses know that after getting a 'no' for an answer, comes a "so what do we do?" question.
-
William Emmanual wrote:
I have been asked to upgrade my entire team to "MVC ready" in 15 days!
Go back to the person who made this request and explain why that is not realistic.
Veni, vidi, abiit domum
Actually, I would go back to the requestor and challenge their assumption. Why 15? Why not 16 or 30 or 1? Once it's been established that 15 is a completely arbitrary, totally pulled-out-of-someone's-ass number, then start talking about what's realistic. I don't think OP said in what environment he's currently working. If it's something like Java, then maybe it's not too bad; you know OO concepts, are used to working with an IDE. Moving from Eclipse or whatever to VS won't be totally foreign. Of course, moving the existing software itself is a big job. However, if OP is doing something like COBOL or C, then it's a much, much, larger challenge. You have to start with a lower-level, learning the OO concepts and such.
-
Rutvik Dave wrote: And if you think that after 15 days of trying, the whole thing is not working, just say 'no' with facts and reasons. People respect when you say 'no' with proper justification. In my opinion the best way to go is to warn your boss that it is not possible, explaining the reasons, the possible outcomes and some alternative solutions. Good bosses know that after getting a 'no' for an answer, comes a "so what do we do?" question.
You are right, but I always want to try first before saying 'no'. That way I will have strong reasons on why I failed. He has 15 days, why not give it a try. :)
Remind Me This - Manage, Collaborate and Execute your Project in the Cloud