Re: Using VS.NET 2005 to support VS.NET 2003 app

Tech-Archive recommends: Speed Up your PC by fixing your registry


"Carl Rapson" <cr@xxxxxxxxxxx> wrote in message news:ufUMQEwWFHA.3584@xxxxxxxxxxxxxxxxxxxxxxx
> I've been informed that I will need to support an application that was developed (by an outside consultant) with VS.NET 2003,
> so I'm looking into my options. This is an opportunity for me to convince my company to provide me with an MSDN subcription,
> so what I am wondering is, do I need to obtain an MSDN subcription while it still include VS.NET 2003, or will VS.NET 2005
> suffice? In other words, will I be able to use VS.NET 2005 to maintain/enhance the application that was written with VS.NET
> 2003?
>
> Thanks for any information,
>
> Carl Rapson
>
Visual Studio 2005 is still in Beta ( Beta 2) right now. If your company can afford to get you a MSDN Subscription with
Development Tools now, that is the way to go. When VS2005 is finally released, you
will get the newer version with your next distribution. Besides, depending on the complexity of the app you will be supporting,
you will have to make some changes in it from 2003 to 2005. I have tested a conversion of a VB.NET 2003 app to VB 2005 ( the
..NET is being (has been) dropped) and have run into a couple of issues (nothing bad, just annoying). For one thing, some
settings in the Forms Designer that is set at Design Time raise an error in the Import and say that those settings are
Depreciated in this version (Beta 2).
I managed to fix that, but, if loading a VB.NET 2003 app into 2005 causes problems and the Import function cannot fix them, then
I wonder what a more complex 2003 application might cause problems with.
And don't get me started on what happens when you try to import a VB6 application! Needless to say, it don't work!!!
A VB6 to VB 2005 (or even VB.NET 2003) conversion application would be great. Someone could make a ton of money if they were
able to write a good one.
But, back to your quesiton, since the app you are going to be supporting is written with VS.NET 2003 and version 1.1 of the
Framework, then unless you intend to move it to 2005 & the 2.0 Framework, you will need VS.NET 2003. Both are tied to their
individual frameworks. (and much easier to work with that way too in my opinion) .
Good luck.
james


.

Relevant Pages

  • Re: Good Reasons to port asp.NET VB.NET app to C#
    ... I think you'll find that migrating the pages from VB.NET to C# is trivial and shouldn't take you much time at all. ... 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. ... 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. ... If I am going to be supporting this app I want to support in C#. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Good Reasons to port asp.NET VB.NET app to C#
    ... Now they want to add new features change some of the ... > time to rewrite this application to C#. ... If I am going to be supporting this app I want to support in C#. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Using VS.NET 2005 to support VS.NET 2003 app
    ... >> provide me with an MSDN subcription, so what I am wondering is, do I need ... > I managed to fix that, but, if loading a VB.NET 2003 app into 2005 causes ... > But, back to your quesiton, since the app you are going to be supporting ... Both are tied to their individual frameworks. ...
    (microsoft.public.vsnet.general)
  • Re: Is file is being used
    ... A system on which I was programming in 1976 that only had 16K of RAM and supported up to 16 attached workstations supported the concept of "Open Private". ... File and record locks were forced, ... It saw a lot of use in the retail market as it also was capable of supporting electronic cash registers. ... If the file is not open, then my app can open the file. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Outlook 2000 SP3 with XP SP2 Mail Delay
    ... > We can't fix it so we're, going to stop supporting it mentality. ... When Outlook 2000 was written, WinXP hadn't even been invented yet. ... try some network trace tools to look for UDP issues? ...
    (microsoft.public.outlook)