What to choose from WPF, WCF, WWF
-
As a .Net 2.0 developer, you always are attached with UI layer, business layer and Data access layer. This seems to be so much integrated till 2.0. Now with respect to 3.5 these terms have new meanings - WPF, WCF and WWF. (Note that I only know the longer names of these, nothing more than that) Naturally, to stay in competition you need to learn upcoming technologies such as framework 3.5 components listed above. So how you will prioritize these ? What would you learn first ? Please answer these questions assuming you are a developer who always wanted to be at the business layer instead of UI layer. I am a bit confused with these new features. It seems that learning all of the above is mandatory now. Am i correct ?
"A good programmer is someone who looks both ways before crossing a one-way street." -- Doug Linder
coolestCoder
-
As a .Net 2.0 developer, you always are attached with UI layer, business layer and Data access layer. This seems to be so much integrated till 2.0. Now with respect to 3.5 these terms have new meanings - WPF, WCF and WWF. (Note that I only know the longer names of these, nothing more than that) Naturally, to stay in competition you need to learn upcoming technologies such as framework 3.5 components listed above. So how you will prioritize these ? What would you learn first ? Please answer these questions assuming you are a developer who always wanted to be at the business layer instead of UI layer. I am a bit confused with these new features. It seems that learning all of the above is mandatory now. Am i correct ?
"A good programmer is someone who looks both ways before crossing a one-way street." -- Doug Linder
coolestCoder
-
As a .Net 2.0 developer, you always are attached with UI layer, business layer and Data access layer. This seems to be so much integrated till 2.0. Now with respect to 3.5 these terms have new meanings - WPF, WCF and WWF. (Note that I only know the longer names of these, nothing more than that) Naturally, to stay in competition you need to learn upcoming technologies such as framework 3.5 components listed above. So how you will prioritize these ? What would you learn first ? Please answer these questions assuming you are a developer who always wanted to be at the business layer instead of UI layer. I am a bit confused with these new features. It seems that learning all of the above is mandatory now. Am i correct ?
"A good programmer is someone who looks both ways before crossing a one-way street." -- Doug Linder
coolestCoder
coolestCoder wrote:
It seems that learning all of the above is mandatory now. Am i correct ?
No. It was mandatory last year. If you don't already know them, you'd best turn in your .NET card and get a slug-farming job. 'Cause yer ain't gonna get nothin' done without the dubyas.
Citizen 20.1.01
'The question is,' said Humpty Dumpty, 'which is to be master - that's all.'
-
As a .Net 2.0 developer, you always are attached with UI layer, business layer and Data access layer. This seems to be so much integrated till 2.0. Now with respect to 3.5 these terms have new meanings - WPF, WCF and WWF. (Note that I only know the longer names of these, nothing more than that) Naturally, to stay in competition you need to learn upcoming technologies such as framework 3.5 components listed above. So how you will prioritize these ? What would you learn first ? Please answer these questions assuming you are a developer who always wanted to be at the business layer instead of UI layer. I am a bit confused with these new features. It seems that learning all of the above is mandatory now. Am i correct ?
"A good programmer is someone who looks both ways before crossing a one-way street." -- Doug Linder
coolestCoder
coolestCoder wrote:
Please answer these questions assuming you are a developer who always wanted to be at the business layer instead of UI layer.
Hmmm...I hope you are not suggesting that you would like to make a career out of only writing business layer objects. Even if that were true you'd be well advised to stay on top of the UI stuff as much as possible. I don't know what WWF is in a programming context but the other two I took a cursory look at, bought a book, read some articles then left it alone as I don't require it currently and certainly it will all change in the not too distant future. That's how I suggest you approach any new technology: get to know it on a surface level, what it does, where it's useful then dismiss it from your mind until and unless it becomes relevant. The most important thing about any programming technology is to know what it is and where it might be useful, the rest you can pick up if and as required.
"It's so simple to be wise. Just think of something stupid to say and then don't say it." -Sam Levenson
-
As a .Net 2.0 developer, you always are attached with UI layer, business layer and Data access layer. This seems to be so much integrated till 2.0. Now with respect to 3.5 these terms have new meanings - WPF, WCF and WWF. (Note that I only know the longer names of these, nothing more than that) Naturally, to stay in competition you need to learn upcoming technologies such as framework 3.5 components listed above. So how you will prioritize these ? What would you learn first ? Please answer these questions assuming you are a developer who always wanted to be at the business layer instead of UI layer. I am a bit confused with these new features. It seems that learning all of the above is mandatory now. Am i correct ?
"A good programmer is someone who looks both ways before crossing a one-way street." -- Doug Linder
coolestCoder
coolestCoder wrote:
It seems that learning all of the above is mandatory now. Am i correct ?
Oh, I don't think so. I'm quite successful and I haven't used WCF or WF and only dabbled very lightly in WPF. They're just tools, like a hammer, and Microsoft expects everything to look like a nail. Marc
-
As a .Net 2.0 developer, you always are attached with UI layer, business layer and Data access layer. This seems to be so much integrated till 2.0. Now with respect to 3.5 these terms have new meanings - WPF, WCF and WWF. (Note that I only know the longer names of these, nothing more than that) Naturally, to stay in competition you need to learn upcoming technologies such as framework 3.5 components listed above. So how you will prioritize these ? What would you learn first ? Please answer these questions assuming you are a developer who always wanted to be at the business layer instead of UI layer. I am a bit confused with these new features. It seems that learning all of the above is mandatory now. Am i correct ?
"A good programmer is someone who looks both ways before crossing a one-way street." -- Doug Linder
coolestCoder
Well, young man, in my stint at a major bank, the only thing I regretted was not getting closer to Enterprise Services, i.e. COM+ in cammo. Today I realised I can seek out my old love in WCF. The term SOA is cheap as mud these days, but it still means something. If you have anything more than one UI, or one web interface, one BL layer, and one DB, you should look at the advantages that a serviced environment can put on your table.
-
As a .Net 2.0 developer, you always are attached with UI layer, business layer and Data access layer. This seems to be so much integrated till 2.0. Now with respect to 3.5 these terms have new meanings - WPF, WCF and WWF. (Note that I only know the longer names of these, nothing more than that) Naturally, to stay in competition you need to learn upcoming technologies such as framework 3.5 components listed above. So how you will prioritize these ? What would you learn first ? Please answer these questions assuming you are a developer who always wanted to be at the business layer instead of UI layer. I am a bit confused with these new features. It seems that learning all of the above is mandatory now. Am i correct ?
"A good programmer is someone who looks both ways before crossing a one-way street." -- Doug Linder
coolestCoder
I wouldn't say that you need to know any of them. We had a consultant build a small website here and they used WCF. The first thing I did when I became responsible for the website was to remove WCF. The funny thing is, after it was built they had to downgrade it to .net 2.0 because the WCF wouldn't work with 3.5! The data in the website is only being used in the website, so the WCF didn't add any value to the application. It was just another piece that needed to be upgraded and maintained. So I removed it all together. Anyway, if you check the message boards, you'll see that http://www.codeproject.com/script/Forums/View.aspx?fid=1004114[^] have only 1500 posts. So not may people are using this stuff yet. Unless you have need to use it, why would you? Most of us asp.net programmers have been learning css and ajax over the last couple years. That's enough for now, it is getting to be ridiculous. Also the LINQ stuff is ridiculous IMO. LINQ seems great for working with xml but why should I use LINQ instead of ADO.Net with store procedures. What is to gain by using these tools? Sometimes you have to actually spend some time creating software and not just upgrading code / installing service packs / testing / learning new tools. Seriously, not everyone can know everything. In my job they want want me to be an expert in IIS, SQL, ASP, VB, C#, HTML, CSS, JAVASCRIPT, CAML, SHAREPOINT, VB6, DotNetNuke, MS OFFICE, Web Services, Windows Services. Edit*** I forgot AJAX, Crystal Reports, SQL Reporting Services, SSIS, DTS and SQL Server Administration. Now I need to learn LINQ, WPF, WCF, WF because MS says so. Give me a break!
I didn't get any requirements for the signature
-
As a .Net 2.0 developer, you always are attached with UI layer, business layer and Data access layer. This seems to be so much integrated till 2.0. Now with respect to 3.5 these terms have new meanings - WPF, WCF and WWF. (Note that I only know the longer names of these, nothing more than that) Naturally, to stay in competition you need to learn upcoming technologies such as framework 3.5 components listed above. So how you will prioritize these ? What would you learn first ? Please answer these questions assuming you are a developer who always wanted to be at the business layer instead of UI layer. I am a bit confused with these new features. It seems that learning all of the above is mandatory now. Am i correct ?
"A good programmer is someone who looks both ways before crossing a one-way street." -- Doug Linder
coolestCoder
coolestCoder wrote:
It seems that learning all of the above is mandatory now
No it's not. Like everything else, they are just tools - so they aren't essential. I know that they seem exciting, but that's just because their spanky shininess hasn't worn off yet. They are useful, but they aren't the be all and end all. Learn them because you want to, not because you think somebody else wants you to.
Deja View - the feeling that you've seen this post before.
-
As a .Net 2.0 developer, you always are attached with UI layer, business layer and Data access layer. This seems to be so much integrated till 2.0. Now with respect to 3.5 these terms have new meanings - WPF, WCF and WWF. (Note that I only know the longer names of these, nothing more than that) Naturally, to stay in competition you need to learn upcoming technologies such as framework 3.5 components listed above. So how you will prioritize these ? What would you learn first ? Please answer these questions assuming you are a developer who always wanted to be at the business layer instead of UI layer. I am a bit confused with these new features. It seems that learning all of the above is mandatory now. Am i correct ?
"A good programmer is someone who looks both ways before crossing a one-way street." -- Doug Linder
coolestCoder
WF always struck me as a toy for Don Box to use in his presentations.
--Mike-- Visual C++ MVP :cool: LINKS~! CP SearchBar v3.0 | C++ Forum FAQ "That's what's great about doing user interface work. No matter what you do, people will say that what you did was idiotic." -- Raymond Chen
-
As a .Net 2.0 developer, you always are attached with UI layer, business layer and Data access layer. This seems to be so much integrated till 2.0. Now with respect to 3.5 these terms have new meanings - WPF, WCF and WWF. (Note that I only know the longer names of these, nothing more than that) Naturally, to stay in competition you need to learn upcoming technologies such as framework 3.5 components listed above. So how you will prioritize these ? What would you learn first ? Please answer these questions assuming you are a developer who always wanted to be at the business layer instead of UI layer. I am a bit confused with these new features. It seems that learning all of the above is mandatory now. Am i correct ?
"A good programmer is someone who looks both ways before crossing a one-way street." -- Doug Linder
coolestCoder
-
Chris Losinger wrote:
WWF has been superseded by the WWE
That doesn't seem right. Shouldn't the successor technology be WWG? And what will they do when they run out of permutations on the alphabet?
"A Journey of a Thousand Rest Stops Begins with a Single Movement"