?
Solved

Upgrade of VS2005 web service

Posted on 2014-01-09
8
Medium Priority
?
307 Views
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!
0
Comment
Question by:ToolTimeGang
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 4
8 Comments
 
LVL 96

Accepted Solution

by:
Bob Learned earned 2000 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.
0
 

Author Comment

by:ToolTimeGang
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.
0
 
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.
0
New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

 

Author Comment

by:ToolTimeGang
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?
0
 
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
http://www.asp.net/whitepapers/aspnet4/breaking-changes

Unintended Api Changes - .NET 4.0 Breaking Changes
http://geekswithblogs.net/akraus1/archive/2011/09/23/147019.aspx

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
...
0
 

Author Comment

by:ToolTimeGang
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!!!
0
 
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.
0
 

Author Comment

by:ToolTimeGang
ID: 39776897
Point well taken.  Thank you.
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

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…
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…
Have you created a query with information for a calendar? ... and then, abra-cadabra, the calendar is done?! I am going to show you how to make that happen. Visualize your data!  ... really see it To use the code to create a calendar from a q…

718 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