I am a junior vue developer currently looking into server side rendering with Node.js. I have just started to use Nuxt but would like to set up SSR from scratch by myself to know how it actually works. I am really struggling to find any good resources or guides on the subject. The official vue docs are a bit too advanced for me and dont really explain how to fully set things up and the few examples I have found on the subject seem to be incomplete. I would really appreciate any pointers to good resources on this subject or any advice on where to look for a beginners guide to SSR
I am creating an ASP.Net MVC 5 website with EF Code First. Although I have written a lot of code and have worked in this business for a long time, I have no experience in deploying a managed website. It seems to me that the goal of EF Code First approach is to create a DB that just works and it's no good for real world deployment.
If that's the case, I was wondering if there is a conference talk, tutorial or other type of resource that I can use to learn about best practices for this purpose. Especially learning how to create a secure and sophisticated database from the scheme of my existing one.
I've searched around and read a lot of opinions about this and got a little confused. Since I'm using MVC 5, I think there are some old and some new ways to do this so I'm asking your advice to pick the best method that works for me.
Recently I ran into this open source project ASP.NET WebformsMVP.
It seems like an alternative to asp.net mvc and also a quick way to introduce testability into an existing webforms applications. (without having to go through the pain of rewriting a bunch of code to make it work for asp.net mvc)
Of couse community support and open-source projects abandonment is always a concern when trying new things, but moving on from those fears, has anyone giving it a serious try at this framework? If so, can you share some insight into its pros/cons and if it's really worth trying it?
Thanks a lot!
WebformsMVP is included in DotNetNuke now, so we have started using it indirectly as part of custom module development within DNN.
I don't think we're fully utilizing everything the framework is capable of, but have had no problems to date. The implementation is very clean and simple to implement, and retrofitting existing webforms code is fairly straightforward. For us the learning curve has been minimal.
We have run into a number of cases where we aren't certain of the "right" way to do things, and have found pretty limited guidance online. (Try as I might to avoid it, sometimes I just have to poke some stuff into the ViewState.) But, with it being used by the DNN team, we feel pretty confident that it will not fade away soon, and a growing number of examples should appear online.
Of course I encourage its use, even if only for the selfish reason of wanting to see the community grow.
I'm mostly a asp.net developer (and currently work as one), but I'm thinking about expanding my skillset or to learn something else. I'm thinking about learning Ruby on rails. What's the pros and cons with these (preferably from a asp.net (mostly version 2.0) perspective). Anyone
who has any insights?
I think it is easy to learn - and worth a try.
From ASP.NET MVC perspective it's easy to learn. ASP.NET MVC is close to rails - but rails has some more features.
For plain ASP.NET it's a bit harder.
Pro:
easy to learn
good to keep on learning new things
excellent linux/apache integration
Cons:
learning something new instead of extending existing asp.net knowledge
Integration in Windows (not good enough from my point of view)
why not? Variety is the spice of life and learning how to perceive code and data in multiple ways should flex your mind to create creative solutions no matter what the problem. There are things that .NET that are fantastic, while other things that RoR and other frameworks do better. No way to understand that until you do it.
Pro:
Exposure to another stack of tools which could be useful if you want to get into mixed environments. Seeing a different paradigm in going to a weak typed language.
Con:
There may be many areas closer to ASP.Net that you could choose to take instead including Azure, database development like MS-SQL or Oracle or Javascript frameworks like jQuery or mobile ASP.Net stuff for sites on smartphones or other things that may be closer to what you are doing now. WCF or WPF may also be options to consider that would be staying within the Microsoft stack in a sense.
While the Pro is certainly a valid one, I would think carefully about what other options are out there that may also be worth doing as well as considering what kind of stuff would you want to do later in your career.
Yes, if you're learning because you're curious. There's no reason why not. Ruby's a great language and learning any new language is interesting, since it can change the way you think about code.
Yes. if you're learning for job skills. RoR and Ruby skills are in good demand, as it's the highest profile web framework.
Personally, I like Python and Django. You might check out Django as the above logic applies to it as well.
I have been working with C# for past four years at the enterprise level. Now, I have taken a decision of moving to Web side of the things. Since I am well versed with C# and WCF I naturally zeroed in on ASP.NET as I need not learn a new Programming language. Learning just the Web Framework will suffice.
I have read a lot regarding MVC, so starting out with MVC 2.
My Question is Will I face any roadblocks if I learn MVC without learning Web Forms? Keeping in mind that this is my first foray into Web Development?
Looking forward to some good suggestions.
I was in your exact same position. The only problems you may have is wrapping your head around postbacks and what tha means. Having said that, MVC2 will teach you how to write better code instead of the typical spaghetti that comes asociated with webforms.
If you're new to MVC2 I'd recommend buying Wrox Professional ASP.NET MVC2 from writer Scott Hanselman.
Learning web development these days is hard as you need to be an expert on so many different things!
You need to learn HTML/CSS/JavaScript(ie, JQuery)/Json regardless of the server side framework you are using if you are creating “rich” web applications.
I would say starting with ASP.NET MVC is not a bad option before moving onto ASP.NET Web Forms. You are likely to hit both going forward, but as ASP.NET MVC does not hide what’s going on so much, I think it may be a better start.
However if you just wish to create simple forms on the web, it is hard to beat ASP.NET Web Forms, but as soon as you wish to do something more advanced, the Web Forms complex page cycle will give you pain.
If you're looking to apply your web skills to enterprise environments, you'd probably find a lot of environments still leveraging Web Forms. Outside of that, I can't imagine it would really hurt you that much.
The bigger thing about web development is getting familiar with HTML/CSS/JavaScript(ie, JQuery). The skills learned there are applicable to either environment. You'd probably be able so switch back end frameworks rather painlessly as long as you're used to c# and all the web stuff previously mentioned.
I think it depends on what type of applications you are going to be developing. I believe web forms would be easier for you to learn with the background you already have in WCF. But it might not be worth it if the applications you are developing are better suited for MVC rather than web forms.
My recommendation would be to determine what type of applications you are going to be developing and then look at the strengths and weakness's of each and then determine which one you are going to focus on.
You most probably won't. There are some concepts that belong to the web-application environment (session, caching, etc) that are common but you'd have to learn about them anyway. They are two separate frameworks so nothing very specific about one of them could help you with the other.
You will undoubtedly run into issues when knowing a "new" way of doing things without having been brought up in the "old" way of doing things. It's unavoidable, really. I'd suggest learning the basics of WebForms code if possible, if for no other reason than to be able to trudge through it when necessary. Of course, if you find yourself in the position of having to support a WebForms application, you'll learn by doing just like anything else.
This question reminds me of my early days in .NET (which were the very early days of .NET in general) and trying to find assistance with various issues. I was an entry level developer, hitting up forums and such with questions. Everywhere I went, people weren't really adopting .NET just yet. They were all old Windows platform developers, whereas .NET was my first Windows development (I was all UNIX/Linux in school). Invariably, nearly every question I asked was answered with something suggesting that I "just use COM." Of course, I wasn't familiar with this. It was "the old way" and I was using "the new way."
It was difficult to work past that, and you'll likely face the same issue here. Basically, when people have made a career out of doing something the one single way they know how, they tend to expect everyone else to know it as well and will cling tightly to it as their bread and butter. You can be better than that, but it'll require patience :)
I assume that your development experience included Windows Forms. In terms of the transition from Windows Forms to ASP.NET WebForms, there's no doubt that would be an easier transition. Whether that would be the best transition is another question. And I believe the answer is without a doubt, no.
MVC allows you to gain an understanding of the way the Web works. Understanding GET and POST, Requests and Responses, not to mention HTML, CSS, JavaScript, et al.
I would not hesitate to recommend MVC.
I don't understand why you don't want to learn Web Forms. Learning Web Forms is just like learning abc's. You'll learn it as you go along with MVC. My suggestion is, Just go with the flow in your learning of MVC and you'll be surprise that you're already learning Web Forms.