Upgrade of VS2005 web service

I have a web service that was created using Visual Studio 2005 (VB).
It is pretty simple, it only has one function and is only called by one application (written in .NET 1.1).
I thought maybe I should recompile it into the .net 4.0 framework because I have read that using the asmx technology is considered legacy.

But now I am leaning towards leaving it "as is".  

And here is why...I have heard that a 1.1 app that calls a WCF service doesn't work that well.  There are issues with it getting a return result back from WCF.

Which then brings me to another question....
Does Windows 2008 R2 support .net framework 2.0 apps?  If it doesn't, then I don't have a choice and I must convert it to WCF.

Any thoughts, advice, sites to refererence on using WCF vs web services would be most appreciated!  Thank you!
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Bob LearnedCommented:
Here are my thoughts:

Leave a stable product alone, until such time as action is required
Work on upgrading the entire system, and not just one piece
We run 2.0 applications on Windows 2008 R2 all the time, but you mentioned 1.1, and that is an unknown.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ToolTimeGangAuthor Commented:
1. That is good advice.  "If it ain't broke...don't fix it".  and that is just what I am going to do.
2. I'm not sure what your point is on the 2nd bullet?
3. Good to know.  I'll just need to make sure I test it out real good.
Bob LearnedCommented:
Work on upgrading the entire system, and not just one piece
If there comes a time when you need to upgrade, I would move all the system components up to more current versions.  1.1 is extremely old, and finding people around that are still using it, and can answer questions, is getting more difficult.

Upgrading would mean choosing a better platform for the web service, such as WCF, Web API, or ServiceStack, and migrating the Windows Forms to Windows Presentation Foundation (WPF), or changing the target framework version for the existing project.  There will be a high probability of breaking changes between 1.1 framework and higher versions, like 4.0 and 4.5.
You will find significant improvements in the .NET framework in 4.0, 4.5, and 4.5.1, over 1.1.
HTML5 and CSS3 Fundamentals

Build a website from the ground up by first learning the fundamentals of HTML5 and CSS3, the two popular programming languages used to present content online. HTML deals with fonts, colors, graphics, and hyperlinks, while CSS describes how HTML elements are to be displayed.

ToolTimeGangAuthor Commented:
We are actually in the process of recompiling our 1.1 apps to 4.0 as you mention.  The web service mentioned earlier will probably one of the few exceptions that will be made.
The conversion process provided by VS2010 has been working pretty good so far.

When you say "breaking changes between 1.1 & 4.0" do you mean the actual process of recompiling the app?  Or the process that uses the app?
Bob LearnedCommented:
"Breaking changes" refers to something like this (a better term might be unexpected API changes):

ASP.NET 4 Breaking Changes

Unintended Api Changes - .NET 4.0 Breaking Changes

Going from 1.1 to 4.0 is a very large step, and there would be a set of breaking changes along the upgrade path (including service packs):

1.1 to 2.0
2.0 to 3.0
3.0 to 3.5
3.5 to 4.0
4.0 to 4.5
4.5 to 4.5.1
ToolTimeGangAuthor Commented:
All of our apps are console apps, so I am hoping most of those will not affect us.  but I will for sure study these in great detail.
Thank you so much for sharing.  I am glad I asked for clarification.
You are always so helpful.  thank you!!!
Bob LearnedCommented:
If you have a good automated unit testing framework, then you should have more confidence in upgrading, since you can run the unit tests after changing the framework version.  

Safety from unexpected API changes depends on what part of the framework that you are using.  Assume that you will be vulnerable to breaking changes, and test as thoroughly as possible.
ToolTimeGangAuthor Commented:
Point well taken.  Thank you.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.