I'm sorry for cross posting this, not sure where it belongs. My Upgrade Wizard only states "Upgrade failed" and produces a log file I can't interpret. Could this be because of the sourcesafe? I've got VS2005 Team Edition for Developers and rights to our tfs, but I don't have VB6, VB6 runtime or SourceSafe. Grateful for any tip! /k
"kkarre" schrieb > I'm sorry for cross posting this, not sure where it belongs. This one only posted to m.p.languages.vb.upgrade (multipost?) > My Upgrade Wizard only states "Upgrade failed" and produces a log > file I can't interpret. > Could this be because of the sourcesafe? > > I've got VS2005 Team Edition for Developers and rights to our tfs, > but I don't have VB6, VB6 runtime or SourceSafe. Don't know if it helps, but the project _must_ be compilable in VB6 on the machine where you use the wizard. If it's not compilable, for example due to missing references, it is impossible for the wizard to do the upgrade. Maybe that's the reason. Or maybe due to Sourcesafe; don't know without knowing the message. Armin
The message was only "Upgrade failed". But it sounds like I need VB6 on the machine - so I can check that it compiles. Thanks! /kk "Armin Zingler" wrote: > "kkarre" schrieb > > I'm sorry for cross posting this, not sure where it belongs. > > This one only posted to m.p.languages.vb.upgrade > (multipost?) > > > My Upgrade Wizard only states "Upgrade failed" and produces a log > > file I can't interpret. > > Could this be because of the sourcesafe? > > > > I've got VS2005 Team Edition for Developers and rights to our tfs, > > but I don't have VB6, VB6 runtime or SourceSafe. > > Don't know if it helps, but the project _must_ be compilable in VB6 on > the machine where you use the wizard. If it's not compilable, for > example due to missing references, it is impossible for the wizard to do > the upgrade. Maybe that's the reason. Or maybe due to Sourcesafe; don't > know without knowing the message. > > > Armin > >
