vb.net doesn't manage its form code
Is there an option in vb.net to force the form designer to delete the code behind a controls that are removed from a form?
Every time I modify a form significantly I'm left with a very large number of unreferenced control declarations. I find it such a pain to remove them all. I'm also quite upset that vb.net doesn't manage its form code for you. I have wasted a considerable amount of time modifying forms. In fact it is so much work sometimes that I just end up creating a new form and moving all the code over.
Thus far vb.net is very aggravating as a development tool. My team is strongly considering going back to VB6. We have wasted a considerable amount of time dealing with vb.net related issues. We have also found that it takes a considerable amount of time to develop a vb.net application properly.
Microsoft has created a complex development tool with a interface that is full of bugs. They haven't made things easy for the developer at all. In fact, they have increased the development time of all my projects.
Re: vb.net doesn't manage its form code
Quote:
Originally posted by 00Kevin
Thus far vb.net is very aggravating as a development tool. My team is strongly considering going back to VB6. We have wasted a considerable amount of time dealing with vb.net related issues. We have also found that it takes a considerable amount of time to develop a vb.net application properly.
Microsoft has created a complex development tool with a interface that is full of bugs. They haven't made things easy for the developer at all. In fact, they have increased the development time of all my projects.
I can tell your frustration has been building up for a while, and I'm guessing that the form designer feature, or lack thereof, might have been the last straw, but just relax. You can't really dive into VB.NET like you and your team have been trying to do, it's a slow migration process that requires you to figure out the VB.NET way to do all the things you used to do in VB6, and so much has changed. If you stop and look at the big picture though.. multithreading, true OO, ADO.NET, all that good stuff.. you will realize there's a bigger benefit to making the transition.
Either way, VB.NET 2003 has the form designer feature you want. I never have to edit the code for the controls I delete with the form designer, if I look at the code for the form, the code is gone. That IS what you're talking about isn't it?
Your post really hurts, man! You talk like that about my baby again and we're gonna have a problem.
:bigyello:
KT