Upgrade of VS2005 web service

Posted on 2014-01-09
Last Modified: 2014-01-13
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!
Question by:ToolTimeGang
  • 4
  • 4
LVL 96

Accepted Solution

Bob Learned earned 500 total points
ID: 39770452
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.

Author Comment

ID: 39772077
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.
LVL 96

Expert Comment

by:Bob Learned
ID: 39772121
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.

Author Comment

ID: 39772135
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?
How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

LVL 96

Expert Comment

by:Bob Learned
ID: 39772167
"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

Author Comment

ID: 39772232
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!!!
LVL 96

Expert Comment

by:Bob Learned
ID: 39772240
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.

Author Comment

ID: 39776897
Point well taken.  Thank you.

Featured Post

IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

Suggested Solutions

Title # Comments Views Activity
WCF Client digital signature 1 143
Web Service example 9 135
entity framework No LOCK 2 814
WCF Service call SOAP request 15 64
In previous Articles, we have discussed how we can upload a file using .asmx web service and isolated storage space. Here, in continuation to the topic, I am going to discuss how we can use WCF for the same purpose. Steps: 1.Create the silverli…
While working on Silverlight and WCF application, I faced one issue where fault exception occurred at WCF operation contract is not getting propagated to Silverlight client. So after searching net I came to know that it was behavior by default for s…
It is a freely distributed piece of software for such tasks as photo retouching, image composition and image authoring. It works on many operating systems, in many languages.
Here's a very brief overview of the methods PRTG Network Monitor ( offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…

760 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

23 Experts available now in Live!

Get 1:1 Help Now