Re: VS 6 to VS.Net justification

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.

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

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

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.

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"?

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 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!

(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: Create Storedprocedure with VB6? Is this possible?
    ... VB6 and ADO no .NET ... can SQL Server Management Studio." ... Can VB6 create a stored procedure on the fly. ... something similar) exactly what you're sending to the db engine (via ADO), ...
    (microsoft.public.vb.database.ado)
  • Re: T-SQL and OLE Automation
    ... A library created as type ActiveX.exe will run out of the SQL Server ... To deploy a .dll, you make it, using the VB6 file/make command, then copy to ... Creating COM libraries with VB6 is probably better discussed in a VB ... > OLE automation and I'm not sure how to write the application on the VB6 ...
    (microsoft.public.sqlserver.programming)
  • Re: T-SQL and OLE Automation
    ... components from VB6 now that VB.Net is so well established as that code will ... Choose a path to save the .dll & remember where it is. ... If you are running your SQL Server on that machine, ... >> Greg Linwood ...
    (microsoft.public.sqlserver.programming)
  • Re: Compact SQL Database and ADO
    ... SQL Server 3.5 Compact 3.5 SP1 Database ... Set prmID = .CreateParameter("plngID", adInteger, ... Set prmText = .CreateParameter("pstrText", adVarWChar, ... VB6 to crash. ...
    (microsoft.public.data.ado)
  • Are multiple-instances on a single cluster supported with SQL Server 2005 Standard Edition?
    ... instances were not supported on a single cluster with SQL Server '05 ... Server 2005 Enterprise Edition instead of Standard Edition. ... instance of sql server. ... supporting multiple instances. ...
    (microsoft.public.sqlserver.clustering)