Printable View
hi all,
i am a new member to this forum
i have project which i have done 3 years back in vb6 which i want to migrate to .net
please provide me some input
while doing the vb6 project i was using a 3rd party grid called as SCGrid
we have a licensed version of that grid which we brought for 190$
can we use the same grid in .net
please give ur valuable feedback
You haven;t given us much to go on. The consensus is don't use the upgrade wizard fro the whole project. Learn VB.NET and recode it by hand, perhaps upgrading chunks using the wizard here and there. There's a link to free eBook from MS in my signature on upgrading. As for your grid, you can still use it but it may not offer you anything over what the DataGrid and/or DataGridView can provide, plus it can often be a bit more painful working with COM controls in a .NET app than working with native .NET controls.
Hi jmcilhinney,
thanks for ur kind reply
my problem was that the scgrid used to give me lot of benefits i could really make each col.
look as i wanted like textbox,combo,list,check even it had option to integrate a custom control to it.
i have seen DataGrid and/or DataGridView but they are not giving me enough options
for ex: i want one column to be edited by user where he will select from list of values from a master table like supplier name
will it be possible
The DataGridView is extremely functional. It can host pretty much any control you like, although I haven't really used it my self so I don't know all the details. The thing to do would be to jump on MSDN and read some of the articles about it. I know there was one in MSDN magazine a while back, although I don't remember exactly when. you could follow the link in my signature and just look through back issues until you find it. It would have to be in the last 8 months or so I'd think.
sure ,
i will check and post back if any issues
thanks for ur support
as for the upgrade part... i agree.. but have a slightly different view.
I found it best to do a full upgrade on the project, then start a new one in the same folder and import a form, and then create a new form with the same name but with 2 on the end, and begin replicating that form, this way i could easily check back on layout and code but completely recode the form.. this also helped me make the change from vb6 to vb.net, i recoded all the forms but could still snip at least some code out of the old ones (where the upgrade was a success) and refer back to them easily.
I can dig that. :thumb:Quote:
Originally Posted by Phill64
hi jmcilhinney,
one more doubt i have installed version 1.0 framework of .net
i have found that your WFC controls will be useful for me which i have downloaded and i was unable to install them as it requires 1.1 framework
now my doubt is can i download the framework1.1 and start using it
or should i have to de install the .net and install again with 1.1 framework
waiting for ur reply
If possible, I would strongly suggest you forget about the .NET Framework v1.0 and v1.1 and go straight to v2.0 (2005), it's more suited to VB6->.NET upgraders, and it offers a huge collection of vastly better Windows Forms controls than the old version did, plus if you don't mind using the express edition, you can get it for free for the time being from Microsoft here.
hi,
will the software work only by upgrading the framework
If they were made in v1.1 of the framework, then yes you need this, v1.1 replaces v1.0 (well, it should), however, v2.0 and v1.1 run side-by-side because there are some major changes that prohibit full replacement.
If you try to run software written for version 2.0 of the Framework on a computer that only has version 1.1 installed the software will not run at all. If you try to run software written for version 1.1 of the Framework on a computer that only has version 2.0 installed the software will still run OK. In this second scenario, the majority of software will run without issue, although there is no guarantee that it will. There are some changes to the Framework in version 2.0 that will break some apps. You can use those WFC controls in a VB 2005 (.NET 2.0) application. I've tested it myself, although not every control in every situation so I cannot guarantee 100% compatibility. I'm told by the company that there is a .NET 2.0 version in the works, so you can do as I am and use the current version for now and when the new version is released you can simply have your app reference the new DLL instead and you should hopefully not have to change any code at all.