separate VB6 from .Net
-
How much would it cost you guys, to create a different department for each of those two dev env's? I mean, they are not quite the same, neither are they alike... so what's the point on keeping them together? A simple lightning-fast solution would be that on the 'new thread' page, there could be a couple of 'options' for each of 'previous to .Net' and '.Net itself', maybe defaulted to '.Net itself', and users could specify it on the 'thread's title'... it'd make the life of those of us who are here just to help much much easier... Thanks for listening to me. Pablo.ar
-
How much would it cost you guys, to create a different department for each of those two dev env's? I mean, they are not quite the same, neither are they alike... so what's the point on keeping them together? A simple lightning-fast solution would be that on the 'new thread' page, there could be a couple of 'options' for each of 'previous to .Net' and '.Net itself', maybe defaulted to '.Net itself', and users could specify it on the 'thread's title'... it'd make the life of those of us who are here just to help much much easier... Thanks for listening to me. Pablo.ar
We're actually trying to avoid VB6 content, and have the VB/VB.NET combination in the forums mainly to cater to those having issues moving from VB6 to VB.NET. If it turns out there's a pressing need for VB6 support forums and even VB6 article sections then we'll do it, but we'd prefer to leave VB6 to the many sites who have covered this topic sufficiently and move forward with VB.NET cheers, Chris Maunder