Re: Good Reasons to port asp.NET VB.NET app to C#
- From: "Ken Cox [Microsoft MVP]" <BANSPAMken_cox@xxxxxxxxxxxx>
- Date: Thu, 31 Mar 2005 11:50:43 -0500
If you're more comfortable in C# than VB.NET, that's a good justification in itself.
As for the time to port it, you can't get a headstart by using a tool like Reflector to decompile the existing assemblies and show the source in C#.
http://www.aisto.com/roeder/dotnet/
"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:
- Good Reasons to port asp.NET VB.NET app to C#
- From: WebMatrix
- Good Reasons to port asp.NET VB.NET app to C#
- Prev by Date: Re: directly typing url in address bar
- Next by Date: Re: What to use instead of the CommandArgument in DataGrids?
- Previous by thread: Re: Good Reasons to port asp.NET VB.NET app to C#
- Next by thread: Tracing and Web.Config
- Index(es):
Relevant Pages
|
