Framework overload
-
Then why do they call it the .NET Framework?[^] ;P
Beacause "they" are marketing people. "They" also named Windows 6.1 Windows 7 and real Windows 7 will be called Windows 8. Just type "ver" in a command line window if you don't believe me :)
-
WTL/ATL small framework, high learning curve, vast rewards.
Software Kinetics Wear a hard hat it's under construction
Metro RSSATL defintely, I agree! ATL was good with VS6 then it also got bulky.
-
Rama Krishna Vavilala wrote:
Surely I am not the only one who feels that there is an overload of frameworks and libraries by Microsoft
No you are not the only one, but why focusing on Microsoft? There are too many overengineered frameworks out there, period. Microsoft ones are at least somewhat documented.
Quote:
Which frameworks released by Microsoft, do you think has been easy to get started and has really simplified your life?
Well, if you consider WTL to be a framework (an edge case between a library and a framework, IMHO), that would be an obvious one.
Nemanja Trifunovic wrote:
here are too many overengineered frameworks out there, period.
Yes I don't deny that. But I wanted to focus on the ones by MS.
Nemanja Trifunovic wrote:
Well, if you consider WTL to be a framework (an edge case between a library and a framework, IMHO), that would be an obvious one.
I agree!
-
Surely I am not the only one who feels that there is an overload of frameworks and libraries by Microsoft all trying to make the life of a developer easy. :) But has it really become easy? My personal opinion is that most frameworks have a high learning curve and they are too much to do little. In my opinion ideal framework should have small learning curve (easier to get started) and should add great value. Which frameworks released by Microsoft, do you think has been easy to get started and has really simplified your life? Ok I am not talking about .NET framework or generic ones like that. I am talking about stuff like Prism, AddIn framework, Entity Framework etc
Silly boy. You don't need all these silly Microsoft frameworks, just use Java. :-D [Vilmos runs and hides in the gin cupboard. Again.]
Panic, Chaos, Destruction. My work here is done. Drink. Get drunk. Fall over - P O'H OK, I will win to day or my name isn't Ethel Crudacre! - DD Ethel Crudacre I cannot live by bread alone. Bacon and ketchup are needed as well. - Trollslayer Have a bit more patience with newbies. Of course some of them act dumb - they're often *students*, for heaven's sake - Terry Pratchett
-
Surely I am not the only one who feels that there is an overload of frameworks and libraries by Microsoft all trying to make the life of a developer easy. :) But has it really become easy? My personal opinion is that most frameworks have a high learning curve and they are too much to do little. In my opinion ideal framework should have small learning curve (easier to get started) and should add great value. Which frameworks released by Microsoft, do you think has been easy to get started and has really simplified your life? Ok I am not talking about .NET framework or generic ones like that. I am talking about stuff like Prism, AddIn framework, Entity Framework etc
I used to be intimidated by the plethora of frameworks out there. I came to the conclusion that it's just like a smorgasbord, you don't HAVE to know everything or use everything, you just have to know what you want to do and know how to look it up. It's just a bunch of toolboxes, that's all. -Max
-
Why MFC of course. :)
Chris Meech I am Canadian. [heard in a local bar] In theory there is no difference between theory and practice. In practice there is. [Yogi Berra] posting about Crystal Reports here is like discussing gay marriage on a catholic church’s website.[Nishant Sivakumar]
Agreed. MFC is compact enough to be learned quickly, and encapsulized well enough to be employed, step by step, even by a mere beginner. I find that not to be the case with .NET / CLR.
-
Beacause "they" are marketing people. "They" also named Windows 6.1 Windows 7 and real Windows 7 will be called Windows 8. Just type "ver" in a command line window if you don't believe me :)
Lol I never realised that the reported version in W7 is 6.1. You'd think they could get their marketing and technical people lined up to that degree. It's also interesting that after the 95, 98, ME, 2000, XP, Vista experiment they seem to be going back to simple version numbers.
-
.NET is not really a framework.
-
Surely I am not the only one who feels that there is an overload of frameworks and libraries by Microsoft all trying to make the life of a developer easy. :) But has it really become easy? My personal opinion is that most frameworks have a high learning curve and they are too much to do little. In my opinion ideal framework should have small learning curve (easier to get started) and should add great value. Which frameworks released by Microsoft, do you think has been easy to get started and has really simplified your life? Ok I am not talking about .NET framework or generic ones like that. I am talking about stuff like Prism, AddIn framework, Entity Framework etc
-
Lol I never realised that the reported version in W7 is 6.1. You'd think they could get their marketing and technical people lined up to that degree. It's also interesting that after the 95, 98, ME, 2000, XP, Vista experiment they seem to be going back to simple version numbers.
Marketing/technical alignment still hasn't happened. The Windows Phone Mango update is officially called Windows Phone 7.5, but my phone reports the OS version as 7.10.7720.
-
I used to be intimidated by the plethora of frameworks out there. I came to the conclusion that it's just like a smorgasbord, you don't HAVE to know everything or use everything, you just have to know what you want to do and know how to look it up. It's just a bunch of toolboxes, that's all. -Max
-
Beacause "they" are marketing people. "They" also named Windows 6.1 Windows 7 and real Windows 7 will be called Windows 8. Just type "ver" in a command line window if you don't believe me :)
Windows 7 is version 6.1 because they are unable to move away from the 6.0 'major' because people used "Version == 6" instead of "Version >= 6"; and thus the application would think it was running in a pre-7 pre-Vista environment. No, I don't have the source, I read this during the Win7 beta days.
He who asks a question is a fool for five minutes. He who does not ask a question remains a fool forever. [Chineese Proverb] Jonathan C Dickinson (C# Software Engineer)
-
The .NET framework has saved me tremendous amounts of work. Things are in places that make sense, there are a lot of complex functions that I don't have to write, etc. This is similar to the "Office bloat" threads you see. There are a TON of features, and people usually only use a small percentage of it. But, everyone uses a different slice of it, so if anything was removed, those people would no longer be able to do their work. It's a rich set of things. There's just no way to pare it down. If you want to learn to use the framework effectively, then I suggest learning small areas of the framework very well. Have a specific goal. I studied the Collections namespaces with the goal of learning which kinds of collections were applicable to different situations. I also had to study the Network namespaces, and System.Data. All of these at different times, for different reasons. Then, because of these studies and the auxiliary learning that just happened because I was working with those things, I had a pretty good overview of what was in all of the standard .NET Framework namespaces. It's better to be ruthlessly effective at a few things and able to search for the information you need on the other things, than to be mediocre at everything and not know where to turn for help. We've all got our own personal libraries of code snippets, so can anyone really claim to be doing anything different anyway?
I think that's a good tip. Learning stuff one piece at a time. Unfortunately I usually get distracted and still end up knowing just a bit of more than I should ;p I think it's also important to learn the general idea of things. For example, if you know that to connect to a SQL database you need a SqlConnection, pass it to a SqlCommand, use that with a SqlDataAdapter etc. you should also know that things work exactly the same for any other database (without the Sql prefix of course) because they are really all just IDbConnection, IDbCommand etc. And when you learn such patterns it becomes easier to learn a new framework where you might recognize certain patterns. In other words, you don't have to re-invent the wheel with every new library or framework :)
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
} -
Surely I am not the only one who feels that there is an overload of frameworks and libraries by Microsoft all trying to make the life of a developer easy. :) But has it really become easy? My personal opinion is that most frameworks have a high learning curve and they are too much to do little. In my opinion ideal framework should have small learning curve (easier to get started) and should add great value. Which frameworks released by Microsoft, do you think has been easy to get started and has really simplified your life? Ok I am not talking about .NET framework or generic ones like that. I am talking about stuff like Prism, AddIn framework, Entity Framework etc
It's very hard to keep yourself updated with all stuff that gets released by the day. My suggestion: Focus on what you think you're going to use and will help on your daily basis. No "immediate" sense on focusing on WPF when your doing web development. Instead, focus on WebForms, MVC and related frameworks like Entity Framework. But then that takes some psychic work on your part when you don't really know what you're gonna need. Try to get acquainted with the most related ones and decide for yourself which ones you should dig deeper.
"To alcohol! The cause of, and solution to, all of life's problems" - Homer Simpson
-
Beacause "they" are marketing people. "They" also named Windows 6.1 Windows 7 and real Windows 7 will be called Windows 8. Just type "ver" in a command line window if you don't believe me :)
off topic, but informative. :)
