Re: VS 6 to VS.Net justification

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Comments inline:

"Sandy" <Sandy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7A2AE7E3-7890-4978-A31A-3653FC2ABD7A@xxxxxxxxxxxxxxxx
So far, VB6 has been pretty good as far as the needs of the organization.

I am concerned, however, that we are using Sql Server 2005. Seems to me
there is a whole lot of functionality that is more compatible with VS.Net,
although I don't know how to present that argument.

Look for information comparing ADO.NET to ADO. Improved automation and
scalability.


Just about all of our apps involve saving in a database and retrieving
information for reports, etc.

Again, the advantages of ADO.NET are well documented. (Google, MSDN)

Also, by way of example, one solution I am in the middle of right now is
writing an application that incorporates MS Word. It basically grabs
records
from an outside Oracle database, pulls it into Sql Server, and it is used
to
provide information to form letters in MS Word (amongst other things it
does).

Look for info on VSTO (Visual Studio Tools for Office) VS 2005 version.


We are in the middle of migrating to Windows Server 2003 and Windows XP
for
client machines. We will probably be upgrading Office applications in the
future as well. I wonder if my application incorporating MS Word may
"break."

Future applications will need RAD, but I have to admit, I am not convinced
on that issue from what I've seen yet; let alone convince someone else.

I believe that if you installed VS 2005 and ran through some of the many
available tutorials and demos, that you'd become more enthusiastic.


Because the new techology relies on real O-O technology, what is going to
happen to all of the old dlls? Will VB6 apps "break"?

COM objects can be used in .NET, but having .NET will not cause your legacy
applications to break.

As far as my professional career is concerned, it is certainly in my best
interests to receive .Net training and advance to the next level; I
certainly
don't want to become obsolete . . . yet another one of my concerns, but
definitely something I cannot use as an argument.

Another question I have to ask is, due to Microsoft's inclination to
release
tools before they are completed is (i.e. service packs and fixes), what
recommendation would you give me for the Visual Studio version to go to?

I think timing will be a factor here. If the decision is imminent, I'd
suggest VS 2005. However, the next version (Codename Orcas) is in Beta 1 and
looks very promising. It's a public beta that you can download at no cost.

http://msdn2.microsoft.com/en-us/vstudio/aa700831.aspx

You can also get a trial version of VS 2005.

http://msdn.microsoft.com/trial/



I am sure you can see from my response how difficult it is for me to
implement a sales pitch . . . I am not even convinced myself. Perhaps the
best way to approach this is for someone to try to convince me to upgrade
and
then use their arguments!

The arguments you develop through research and by using the tools will be
much more convincing than anything passed on, IMHO.


(I do have to admit, though, that I have worked with .Net on Web
development
for about a year outside of work and I think it's fun. That certainly
will
not work as an argument!!)

Any help in this regard will be appreciated -- and please forgive my
rambling!!
--
Sandy


"pvdg42" wrote:


"Sandy" <Sandy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E7758730-1293-47D8-AFF6-3BB42C58F8B4@xxxxxxxxxxxxxxxx
Hello -

I need a justification for the powers that be on the purchase of Visual
Studio .Net. We are currently using Visual Studio 6.

Any reasons and/or points to make will be appreciated!
--
Sandy

A lot of what you write will depend on the type(s) of work you intend on
doing with VS. You want to avoid generalizations in the justification
with
no supporting specifics.

The biggest general differences, IMHO, are the introduction of the .NET
Framework and much better support for web app development. Add to that,
that
..NET is the present and future (you'll want to look up when VS 6 will no
longer be supported as part of your justification), and then add
pertinent
details.

If you tell us what type(s) of applications you are currently, or plan
on,
developing, more detailed feedback can be provided.






.

Relevant Pages

  • Re: Utter madness!
    ... Alternativelly go into Visual Studio help, then Contents, Visual Studio ... .net, Visual basic and C#, Creating applications, Creating web applications ... and services, Security considerations...., Accessing SQL server from a web ... > use Windows integrated security for database access. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: My C:Windows folder takes 9.21GB, is it too large?
    ... Visual Studio 2005 ... SQL Server 2005 Developer Edition ... like CCleaner, you could reclaim more free space, temporarily. ... your applications are probably taking up much of the space on C: ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: what is up with so called experts?
    ... Maybe throw in some SQL server. ... If you are going to identify MS specific applications, then yea, they ... Running Visual Studio is an appropriate answer. ...
    (microsoft.public.windows.vista.general)
  • SQL Server 2005 and Visual Studio 2005 Express Version Installation nightmare
    ... made the installation of SQL Server 2005 Expess and Visual Studio ... Why is the visual Studio shell bundled with SQL Server Advanced ... Visual Studio program applications. ...
    (microsoft.public.vstudio.general)
  • Re: Slow booting xp home.
    ... Changing the boot order to boot first from your hard disk might save you a half second, but you won't be able to boot from a CD until you change it back - and the time spent to do that will erase any previous time saved. ... 2- Consider what software you really want to start with Windows and also how you've configured your applications at startup ... Installing and Registering Visual Studio Express Editions Smart Device ...
    (microsoft.public.windowsxp.perform_maintain)