Re: Good Reasons to port asp.NET VB.NET app to C#
- From: Matt Berther <mberther@xxxxxxxxxxx>
- Date: Thu, 31 Mar 2005 11:53:07 -0800
Hello WebMatrix,
There is no technical reason that I can see that would require you to port from C# to VB.NET, unless you require some functionality that isnt available from VB.NET (unsafe code and pointers). In most cases, this is not needed.
-- Matt Berther http://www.mattberther.com
No, I am not asking anyone to help me to lie. Maybe I didn't phrase my question correctly. I didn't mean for it to turn into ethics discussion, I was simply asking is there any good TECHNICAL reasons to port to C# besides personal preference. I realize that "I prefer C# over VB.NET" is not a good reasons by itself for my client or myself, and I wouldn't even bring it up. And to do it on my own without telling them would be not only dishonest but plain stupid, I have other projects ( C# :) ) lined up, so I would be pushing back their deadlines and making myself look incompetent. That's why asked this NG for any other reasons besides "I like C# better". So I get that the answer is " it's more of a personal preference thing", I can live with that. "Steve C. Orr [MVP, MCSD]" wrote:
I agree with Kevin. It doesn't sound like you have a good reason for switching the app to C#. It's just a personal preference. So you're basically asking us how to help you lie to your client, which I won't do. Either keep the app in VB.NET (which is a perfectly fine language) or port the app on your own time (with the help of a code converter application to cut down on the effort needed.)
-- I hope this helps, Steve C. Orr, MCSD, MVP http://SteveOrr.net "Kevin Spencer" <kevin@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:e7XPG1gNFHA.3560@xxxxxxxxxxxxxxxxxxxxxxx
Okay, your requirement is to upgrade the app. Your DESIRE is to change it to C#. I'm assuming that you're paid for your time. IMHO, you have 2 ethical choices:
1. Migrate it to C# on your own time. 2. Leave it in VB.Net IOW, there are no logical reasons for changing the language. If you do so, your boss will want to know why, since he's paying for it. And there is no why, other than your personal preference.
-- HTH,
Kevin Spencer Microsoft MVP .Net Developer What You Seek Is What You Get. "WebMatrix" <WebMatrix@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:A95E22A7-A7EC-41F9-8D6B-DDA71DCD786C@xxxxxxxxxxxxxxxx
Hi,
I developed ASP.NET application in VB.NET about a year ago; it has been in production since. Now they want to add new features change some of the existing ones, it's not a major rework, but probably a week of work or so. My dilemma is that I have switched to C# since than and want to continue coding in C#. Now would be a good time to port this app to C# with new features which will add probably twice as much time to development of this new release. What reasons I can give to the management to convince them to give me extra time to rewrite this application to C#. From what I understand there's not that much difference between VB.NET and C# it compiles to the same code. But I find C# more concise and more "suitable" for .NET; just more elegant language. If I am going to be supporting this app I want to support in C#.
.
- References:
- Re: Good Reasons to port asp.NET VB.NET app to C#
- From: WebMatrix
- Re: Good Reasons to port asp.NET VB.NET app to C#
- Prev by Date: Re: moving from vb.net to c#
- Next by Date: Re: Persisting Trace.axd
- Previous by thread: Re: Good Reasons to port asp.NET VB.NET app to C#
- Next by thread: Re: Good Reasons to port asp.NET VB.NET app to C#
- Index(es):
Relevant Pages
|