From: Michel Posseth [MCP] on 21 Apr 2010 12:31 Until sofar everything seems to work almost flawless over here i encountered until sofar 2 problems with the conversions of my projects 1. if you have a solution with multiple projects you have the chance that some files are converted twice , you can recognice this by the obvious errors ( just removing the .1 versions wil solve this ) 2. Some warning messages appear while the warning is total #$#% ( i submitted this to microsoft connect with a screendump ) if you are not so sure of yourself you might refactor the code while it is in fact perfectly valid code michel "Gale Green" <gale(a)databeat.fsnet.co.uk> schreef in bericht news:cjgts59f53e57sj59826oonih14chcg7dm(a)4ax.com... > > Hi all. > > I've been reading on the MS web site till my eyes crossed and I've not > found the info that I need. > > I have VS 2008, although I use only VB. If I upgrade to 2010 will my > existing apps build OK or will they require change? > > Thanks for any guidance. > > Gale.
From: J.B. Moreno on 22 Apr 2010 01:27 Cor Ligthert[MVP] <Notmyfirstname(a)planet.nl> wrote: > You cannot use framework 4.0 if you have used the > Microsoft.VisualBasic.Compatible.VB6 namespace) the latter is normally only > if you have automatically converted from VB6. http://msdn.microsoft.com/en-us/library/microsoft.visualbasic.compatibil ity.vb6.aspx shows a lot of obsolete calls, but obsolete calls work.... -- J.B. Moreno
From: Gale Green on 22 Apr 2010 12:41 On Wed, 21 Apr 2010 18:31:56 +0200, "Michel Posseth [MCP]" <msdn(a)posseth.com> wrote: >Until sofar everything seems to work almost flawless over here >i encountered until sofar 2 problems with the conversions of my projects > > >1. if you have a solution with multiple projects you have the chance that >some files are converted twice , you can recognice this by the obvious >errors ( just removing the .1 versions wil solve this ) > >2. Some warning messages appear while the warning is total #$#% ( i >submitted this to microsoft connect with a screendump ) if you are not so >sure of yourself you might refactor the code while it is in fact perfectly >valid code Thanks for the extra info Michel. Gale.
From: Cor Ligthert[MVP] on 23 Apr 2010 03:32 Hi, Thanks for this information, I really had the idea that it was described in the same time as the upgrade facility. I see now that this is only for 64bits where it is not available while available for 32bits. Cor "J.B. Moreno" <planB(a)newsreaders.com> wrote in message news:210420102127270841%planB(a)newsreaders.com... > Cor Ligthert[MVP] <Notmyfirstname(a)planet.nl> wrote: > >> You cannot use framework 4.0 if you have used the >> Microsoft.VisualBasic.Compatible.VB6 namespace) the latter is normally >> only >> if you have automatically converted from VB6. > > http://msdn.microsoft.com/en-us/library/microsoft.visualbasic.compatibil > ity.vb6.aspx shows a lot of obsolete calls, but obsolete calls work.... > > -- > J.B. Moreno >
From: J.B. Moreno on 22 May 2010 16:31 In article <uZihjcr4KHA.6104(a)TK2MSFTNGP05.phx.gbl>, Cor Ligthert[MVP] <Notmyfirstname(a)planet.nl> wrote: -snip cannot use both 4.0 and Microsoft.VisualBasic.Compatibility.VB6- -snip yes you can, just obsolete now- > Hi, > > Thanks for this information, I really had the idea that it was described in > the same time as the upgrade facility. > > I see now that this is only for 64bits where it is not available while > available for 32bits. Thanks, I almost missed the fact that the obsolete attribute on the methods include a notice that they are 32 bit only. -- J.B. Moreno
First
|
Prev
|
Next
|
Last
Pages: 1 2 3 Prev: MailMessage message size Next: How to build the form with details button? |