|
I've been making a killing doing Windows programming for 30 years - WAY before there was an internet. Mobile is still a cute fad.
Think about that for a second.
If it's not broken, fix it until it is
|
|
|
|
|
Agreed. I still find plenty to do writing Winforms applications. That technology (and ASP.NET) ain't going away. Winforms and ASP.Net are very reliable and mature (and well entrenched) technologies. The new stuff augments them for sure but totally replace them? No way.
|
|
|
|
|
I'm always hearing younger, up & coming developers tell people that "Windows programmign is dead" and I always say Nonsense!
There are and always will be untold millions of desktop apps that have no reason to be web or mobile - and that keeps me gainfully employed.
If it's not broken, fix it until it is
|
|
|
|
|
Microsoft AX - an ERP application that brings in Millions for Microsoft is a winforms/wpf(I am not sure which technology it is but it is definitely client based) application.
The reason Microsoft appear to have chosen this is that browser based apps are entirely at the mercy of the browsers - release an update to a browser and your whole Business goes down.
While the desktop .NET framework breaks much less frequently.
[edit] seems like I am "behind the curve"[^]
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
modified 23-Feb-16 5:56am.
|
|
|
|
|
ASP.NET what?
WebForms, MVC?
To me ASP.NET is just another backend technology. Also dive into the client side: HTML 5, CSS3, SASS/LESS, jQuery, bootstrap, angular ... The list goes on and on. 
Cheers!
"I had the right to remain silent, but I didn't have the ability!"
Ron White, Comedian
|
|
|
|
|
With a little focus, you should be able to spend so much time learning the multitude of new technologies that you never become employable
My long term goal is to live forever. So far, so good...
|
|
|
|
|
Frank Alviani wrote: you should be able to spend so much time learning the multitude of new technologies that you never become employable
Aye, ain't that the truth.
Marc
|
|
|
|
|
The very reason I hate web development.
So I recently quit my web development job and took a job programming Microsoft Dynamics AX - seemed perfect for a Windows guy like me.
And what happens then: Microsoft announces that starting from the next version of AX, they will quit the Windows GUI and only use the web GUI
Thanks so elephanting much! 
Hope that Kevin is right and mobile is just a fad... 
Anything that is unrelated to elephants is irrelephant
Anonymous
-
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-
I'd just like a chance to prove that money can't make me happy.
Me, all the time
|
|
|
|
|
Exactly. Jack of all trades but master of none.
|
|
|
|
|
Kelly Marchewa wrote: Do you think ASP.NET has a bright future? Why or why not?
I think it's mostly an irrelevant question. The back-end does what the back-end does, handle requests, interface to the DB, serve pages, etc. I probably spend less than 10% of my time working on the back-end, regardless of what technology I use. The remaining 90% is spent f***ing around with HTML and CSS, the oddities of bootstrap, the incomprehensibility of backbone (or whatever your favorite Javascript MVC poison is), and the bullshit of trying to get a web page to render on a dozen different browsers and their versions, tablets, phones, and so forth.
Marc
|
|
|
|
|
I don't believe that makes it an irrelevant question at all. I think ASP.NET has a great future as a 'backend', i.e. handling requests: session, cookies, authorization, caching etc. Web Forms and MVC are (well, Web Forms maybe[1]) are quite a small part of ASP.NET.
[1] That elephanting ugly viewstate model makes everything so easy, we just reconstitute our controls and render them.
Do what thou wilt shall be the whole of the Law. - Liber AL vel Legis 1:40, Aleister Crowley
|
|
|
|
|
Brady Kelly wrote: I think ASP.NET has a great future as a 'backend'
Certainly, but there's many options out there, many not .NET solutions, and even I prefer my own server implementation rather than using ASP.NET or Razor/MVC.
Pure ASP.NET though, I find horribly klunky actually. Well, at least the projects I've worked on that used it. Maybe the folks who originally wrote the back-end didn't know what they were doing. Strike that, they definitely didn't know what they were doing (I've seen some SQL statements in the friggin' HTML!)
Marc
|
|
|
|
|
|
Marc Clifton wrote: I think it's mostly an irrelevant question.
I beg to differ. I do almost no front-end work besides javascript (JQuery, Angular, et al). We have a team that develops HTML and CSS work and UI designs. I just make the interface work. And choosing a good backend to work with matters, a lot.
Complex business logic do not happen on the front-end, it happens on the business layer. Having a good framework that integrates well with a business layer you're comfortable with (like .net) can make all the difference in productivity.
Web API, ASP.Net MVC works ton towards productivity.
It's a great choice to me.
To alcohol! The cause of, and solution to, all of life's problems - Homer Simpson
Our heads are round so our thoughts can change direction - Francis Picabia
|
|
|
|
|
Fabio Franco wrote: We have a team that develops HTML and CSS work and UI designs.
You are SO lucky. The vast majority of projects I've worked on, us devs have had to that work.
Riddikulos![^]
Marc
|
|
|
|
|
Marc Clifton wrote: You are SO lucky.
I guess I am, if not me web apps would all look like winforms apps. 
To alcohol! The cause of, and solution to, all of life's problems - Homer Simpson
Our heads are round so our thoughts can change direction - Francis Picabia
|
|
|
|
|
I had to chuckle when I read Marc's comments. He hit it on the nose. As a web developer you spend most of your time "f**cking around" with the web UI piece. Hours just roll by when working with UI. The back-end is pretty straight-forward.
I do love ASP.NET MVC. It's the way to go and I believe it'll be around for many years. I've tried the "other" framework architectures and languages out there, but ASP.NET MVC is the best.
|
|
|
|
|
This is going to sound positively Jurassic, but I still prefer ASPNET WebForms over MVC. Sure MVC works great with all these flashy frontend Javascript frameworks but losing all those canned WebControls that come built into WebForms makes everything so much more tedious and cumbersome. I understand everyone wants Ajax and asynchronous partial POSTs and all that but there's something empowering about being able to roll up a web solution just as quickly as a desktop solution when using WebForms that is very hard for some of us ASPNET old timers to let go of.
|
|
|
|
|
Exactly. First make it work, then make it pretty...
I may not last forever but the mess I leave behind certainly will.
|
|
|
|
|
Do you think the internet has a future? Do you think Microsoft has a future?
|
|
|
|
|
It has a future, but it's moving towards using more of the Web API and then writing a Web frontend on top of it. Which, when you look at it that way, isn't really very different from most other common platforms.
The latest version of MVC that is coming out is really pushing this API backend with a general HTML/CSS/JavaScript frontend. So, yes, it has a future and is relevant. This is exactly how I've been using it for a while now, haven't even written any Razor code in a couple of years.
Things like Webforms don't really translate too well, but I have been working with .NET for 8 years and never once worked on a Webforms project. It's really not necessary to spend too much time learning it, unless the company you want to work for specifically asks for it.
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.
|
|
|
|
|
Count yourself as lucky. I've had to patch a few of our web forms projects, and the horrible coding practice seems to be the webforms bread and butter.
|
|
|
|
|
Oh, I've had plenty of horrible code thrown at me that I've had to fix/maintain even without Webforms!  
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 have been in the Microsoft development game for a few years now.
I personally think it does have a future, with Microsoft investing in the next version of ASP.net (VNext) and making strides in allowing for the deployment of ASP.Net applications to different types of containers via Katana and OWIN, the fact I can run an MVC application within a threaded process without the use off IIS is a big win and as a result of this I think we will see ASP.Net for a long time.
But as Frank said it is important that you spend time in learning a multitude of technologies as it will serve you well in the future.
|
|
|
|
|
Kelly Marchewa wrote: Do you think ASP.NET has a bright future? Why or why not?
This is the question every developer should ask themselves, every time they look at a new technology. "Is this worth learning?"
Like many others, I've been doing this for nigh on 30 years. I look at old resumes and see technologies that no longer exist, things I've mostly forgotten about. I've learned dead-end technologies (Object/1, anyone?) and things that still live on FAR past their expected lifespan (Visual Basic 6 still lives in VBA). I learned to pay attention to things like market share, and focus on technologies that I think will keep me employed.
To answer the actual question: Yes, ASP.NET has a future. It's been around in various forms for 20 years, and the current market share is currently great. Google "market share asp.net" -- ya gotta take what you find with a 5# bag of salt, but everything I've found indicates ASP.NET market share is solid - 15% to 30% of the backend market. Lot of large companies have significant investments in this technology, so it will be around for years to come.
How long? Sorry, my crystal ball is foggy. Nothing lasts forever, so plan on learning new technologies on a regular basis. You've got PHP? That's great! It supposedly powers 70% of the internet. I'm playing with it now.
IMO learn: C#, ASP.NET, CSS, HTML5. These technologies all currently have good market share and will give you a diverse background that will help you in future years when no one remembers how to spell "ASP". 
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
