Registration page....why not go with static html and grab the data in the controller? (Use knockout if you need to). Be careful with MongoDB. If you need indexes on sub-forms (usually array fields) it will bog down when collection grows. For the right project MongoDB is awesome. Cheers (but I feel the pain).
charliebear24
Posts
-
MVC and RazorEngine rant -
What technology stack would you recommend as I start my first ever ASP.NET real project?Microsoft stack is: ASP.NET (with or without MVC), Razor, IIS and Entity Framework/MSSQL. But what about vNext? Seems to me that vNext is Microsoft's answer to Nodejs and looks to be a future 'upgrade' for ASP.NET (BTW Nodejs isn't written in Javascript, it's written in C and just translates JS). IIS is a slippery pig as far as I'm concerned but I still use it. The Javascript stack is: Angularjs (which is amazing), Nodejs (usually with Expressjs on top) and either SQL or Mongodb for the db. Knockout and especially Breezejs seems to be the ORM of choice. As far as open source goes, the creme de la creme rises to the top and isn't as 'open' from a development perspective as you might think (being controlled by the original authors which is now often Google, Amazon, Sencha, MS and a small group of super guru's). Open source it not a free for all. Typescript is a nice enhancement to JS but I don't like working with anything that's 1.0 (for production). I've been developing in C#/.Net since 2001 and now currently learning the Javascript stack and it's been PAINFUL! But, Javascript isn't a toy language anymore and is the language of web development going forward, just ask Microsoft! Cheers to all.
-
Why I like Microsoft todayVT100 was advanced technology! How about an IBM 360 with punch cards via COBOL! First program ever was 250 lines(cards). Got the program back from the University data center and it had 700 errors! lol. (circa 1970). C# and .Net have been great but I think the industry is now embracing JavaScript (TypeScript would be nice) and Angular along with a barrage of JS libraries. Microsoft has some serious catching up to do. They should have made .NET native to the IE browser. Never developed anything in Silverlight but it was a good idea. Cheers to all.
-
New to writing code...brain is melting......I feel the pain! I was in the same position in 2001 when switching to VS C#. I use google to find examples and help (forget about MS help system). For example: a search on google for ListCollectionView will show a good list with examples from all corners of the world. If MS shows up first, I check it out but scroll down through the members list to the examples. Mentally, in 2001, I said to myself "this stuff looks like Greek to me but a year from now I'll understand it." It worked. Now it's all about design, coding is more about the never ending challenge to keep things "clean" and "tidy". I also purchased at least $1,000 in books over the first two years. If you want a really good beginners book on WPF and MVC try "Teach Yourself WPF in 24 Hours" by Eisenberg and Bennage. It will point you in the right direction and get those "little grey cells" electrified! Buy older books from Amazon "used" for a fraction of retail. Good luck and Cheers!
-
I Hate Obsolete Computer Books!Recycle. I did it with no less than 100 tech books. But there was one I wish I had kept, so be careful!!! Cheers.
-
Why did Microsoft make the Entity Framework open source?You're right and it raised some eyebrowes here too. We feel EF is the best DAL that Microsoft has ever created. Just hope they don't drop it for some new intests in JavaScript and friends. We are a little worried that MS might not realize they have finally created a great set of tools for developing applications and go off in some weird direction chasing down some new language fad. XAML, EF, VS, C# should rule for business apps (and more) for a long time. I saw a suggestion that MS should put the CLI in the BROWSER! Why not? Cheers to all.
-
TDD : DO I reallly needs to learn it ?The primary reason TDD has popped up into the mainstream focus is because JavaScript is a crapper of a language. If you don't create a test script after ever new line of JS code it will break. TDD is just bottom up testing versus top down (the way you do it as do most other developers). Well tested top down applications work just as well as TDD apps and if you code properly it will be just as maintainable as TDD. The big difference is TDD takes 3 times longer and 5 times as expensive. Cheers.