|
for some comments like that might be hard to handle, bar set too low!
Message Signature
(Click to edit ->)
|
|
|
|
|
Why don't you toss your British style spelling dictionary into a fyre?
Ravings en masse^ |
---|
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
Because I'm neither Danish, nor Norwegian, nor Scottish:
fyre - Wiktionary[^]
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Tyre[^]
City in Lebanon
Tyre, sometimes romanized as Sour, is a district capital in the South Governorate of Lebanon. There were approximately 117,000 inhabitants in 2003. However, the government of Lebanon has released only rough estimates of population numbers since 1932, so an accurate statistical accounting is not possible.
Ravings en masse^ |
---|
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
Me either, although I got my DNA results back and I'm a little bit of all of those, plus eastern and Werstern European.
CQ de W5ALT
Walt Fair, Jr., P. E.
Comport Computing
Specializing in Technical Engineering Software
|
|
|
|
|
Me neither, although I got my DNA results back and I'm a little bit of all of those, plus eastern and Western European.
CQ de W5ALT
Walt Fair, Jr., P. E.
Comport Computing
Specializing in Technical Engineering Software
|
|
|
|
|
If I'd left the "y" the pun wouldn't work.
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Puns our too bee spoken allowed - not red!
Socialism is the Axe Body Spray of political ideologies: It never does what it claims to do, but people too young to know better keep buying it anyway. (Glenn Reynolds)
|
|
|
|
|
Likewise, unicycles are exhausted....they are always one tired bike.
|
|
|
|
|
I have a feeling you recycled this one.
/ravi
|
|
|
|
|
I used to use these Math software a long time ago. Recently, I noticed that the website was gone. Now I know why.
I always wondered what happened to the authors and developers that we never knew or met.
|
|
|
|
|
|
I have an opportunity to redesign a web app that is currently a KendoUI/JQuery app. I want to move to something like MVC or Razor Pages. We're using VS2015 (we are at the mercy of the USAF approved software list, and VS2017 isn't on it yet.
I'm interested in hearing an honest comparison between MVC and Razor Pages. I don't want evangelism, nor advocacy. I'm looking for honest pro/con comparisons.
You may begin.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
I would give my vote to .NET Core's Razor Pages at this point...
1. The code much better organized (very similar to the ASP.NET WebForm's organization, of single node for single page)
2. Easier to maintain the idea of single-responsibility
Beside this there is nothing you can not do wit Razor and can do with MVC...
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
|
|
|
|
|
|
Razor is a rendering engine, MVC is a a web architecture, you can't compare the two. The "V" in Microsoft's MVC is usually Razor.
|
|
|
|
|
Yeah, but Razor Pages is the new .NET Core approach that is based on the framework but is structured differently. I thought the same, somehow I was not tracking on this either:
Introduction to Razor Pages in ASP.NET Core | Microsoft Docs
"Never attribute to malice that which can be explained by stupidity."
- Hanlon's Razor
|
|
|
|
|
Ya, I was confused and thinking I didn't know what I was doing.
I agree with your statement.
Everyone is born right handed. Only the strongest overcome it.
Fight for left-handed rights and hand equality.
|
|
|
|
|
Thanks to good naming strategies of Microsoft there is a huge confusion about this...
There is MVC's - de facto standard - HTML rendering engine named Razor... and there is .NET Core's MVVM framework named Razor Pages (probably named because the basic syntax is the same as in Razor rendering engine and the HTML rendering part IS the Razor rendering engine)...
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge". Stephen Hawking, 1942- 2018
|
|
|
|
|
Thanks for the clarification, I knew he was probably referring to Core, I was being slightly facetious I didn't know they've called it Razor Pages though.
|
|
|
|
|
I have found MVC to be a powerful addition to my toolset but I must admit that the way MS implemented various facets can be confusing at times (I'm looking at you routing).
Pros:
I like to be able to write code loops right there in the HTML markup (list/table building is easier)
You can apply filters which execute on each request to an entire controller or a single action (no repeated session management boilerplate code)
Loose coupling between models and controllers
Cons:
Routing can become painful as web sites grow larger and deeper
Documentation for the under-the-hood parts is spartan
Far to many string literals required controller code
if (Object.DividedByZero == true) { Universe.Implode(); }
|
|
|
|
|
|
The big difference between the two come down to project organization.
Project Organization is related to two things:
1. Where the files (Views, Models, etc) -- not a big deal
2. Nuget packages -- how you deploy your MVC site - which can be a major pain when you move from one version of MVC to another (or to .NET Core Razor Pages).
However, you will find that you can relatively easily:
1. start out with VSTudio 2015 ASP.NET MVC (whatever version it is)
2. Move to .NET Core Razor Pages (or .NET Core MVC a very similar option) whenever you are ready.
The main thing to keep in mind is to :
1. Create real models for your domain objects
2. Use the Service and repository pattern for data access
3. Keep your Controllers and Views organized.
This will allow you move to .NET Core Razor Pages with little or no trouble at all.
In the future you'll just:
1. create a .NET Razor Pages Project
2. Move your Views, Controllers, Models in.
3. build and run.
It'll be pretty much that easy. The Razor code is the same and the Controller and View code will be okay too.
So, the point is, go ahead and use VSTudio 2015 ASP.NET MVC now and convert later.
You'll be fine. Good luck.
|
|
|
|
|
Might I suggest QlikView. ...ducking for cover. Well, we know it's on the approved list.
"Go forth into the source" - Neal Morse
|
|
|
|
|
I honestly don't know if Qlikview is on the USAF's approved list.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|