Les,
The subject of the post indicates that he is not moving from VB6 but from
VS.NET 2002 to VS.NET 2003, so no migration tool is needed ;-)
Shawn,
It should be quite direct, no problems. Both VS.NET IDEs and NET Frameworks
can coexist. The only caveat is that the project files are in different
format, so once you save a project file with version 2003 you can not open
it with 2002 (there are tools on the internet to move back if needed, or you
can wisely make backups). Pure code files remain unchanged but .resx files
also change.
--
Carlos J. Quintero (Visual Developer - .NET MVP)
FAQs, Knowledge Base, Files, Docs, Articles, Utilities, etc. for .NET
addins:
http://groups.yahoo.com/group/vsnetaddin/ (free join)
"Les Smith" <les@nospamplz.knowdotnet.com> escribió en el mensaje
news:eX$$3g9JEHA.1264@TK2MSFTNGP12.phx.gbl...
[quoted text, click to view] > Shawn,
> It depends on how much special code you have in VB6. Obviously, all code
> must compile in VB6 on the computer that you use to migrate to .NET.
>
> I have migrated several major apps, and the problems are by no means
really
> difficult. The migration tool does a good job and does not force you to
> move from standard ADO to ado.net but I certainly recommend it since
ADO.NET
> is much more powerful for future development.
>
> Have some good resource books available as well as several .NET sites.
> Learn to use Google search for help, there are thousands of answers on the
> web.
>
> HTH
> Les Smith
> Articles, free code, add-ins at
>
http://www.KnowDotNet.com >
> "Shawn Melton" <anonymous@discussions.microsoft.com> wrote in message
> news:32B7A7D5-403E-4B04-9DFD-BE817F6D0D4C@microsoft.com...
> > What are the issues and problems I am likely to encounter wheh migrating
> my developers to the newest development tools?
>
>