What would be the best approach to migrate VB6 ocx project to VS.net? Is VC++ and ATL the only option? Or is it better to forget OCX and create .NET object? What are the pros and cons? TIA
"yk" schrieb: > What would be the best approach to migrate VB6 ocx project to VS.net? > Is VC++ and ATL the only option? > Or is it better to forget OCX and create .NET object? > What are the pros and cons? In which host environments do you want to use the control (VB6, .NET, IE, ...)? -- M S Herfried K. Wagner M V P <URL:http://dotnet.mvps.org/> V B <URL:http://dotnet.mvps.org/dotnet/faqs/>
"Herfried K. Wagner [MVP]" wrote in message news:#0nJJoDiIHA.4468@TK2MSFTNGP03.phx.gbl... > "yk" schrieb: >> What would be the best approach to migrate VB6 ocx project to VS.net? >> Is VC++ and ATL the only option? >> Or is it better to forget OCX and create .NET object? >> What are the pros and cons? > > > In which host environments do you want to use the control (VB6, .NET, IE, > ...)? > > -- > M S Herfried K. Wagner > M V P <URL:http://dotnet.mvps.org/> > V B <URL:http://dotnet.mvps.org/dotnet/faqs/> It is a custom windows application for Windows XP or Vista. The application was mostly written in VC++ and VB6 using VisualStudio 6.0. VB6 code builds OCX. ATL and MFC were used in VC++ part. I would like to modernize the application and migrate to a single and moderm IDE like VisualStudio.NET 2008, but the VB6 part is the main concern. I am wondering whether I should convert all to .NET using language like C# or leave them unmanaged code in VC++ and MFC10. The latter seems to be less work, but may not be a good choice in a long run. Any suggestion would be appreciated.
