Dim
a As Boolean = Me.ActiveCheckBox.CheckState and get the warning, implicit conversion from syste.windows.forms.checkstate to boolean.I have lots of such warnings. You'd think vs would allow you to get more information on how to solve it. I have many such warnings and can't submit a million questions to this forum on solving each one.
In addition, I can't copy the warning
Another irritant is the well known need to click alt+enter
A bigger problem is my attempt to inherit and add features to a binding navigator.
Let me quote from my submission to microsoft
| Please refer to microsoft technical forums http://forums.microsoft.com/msdn/ShowPost.aspx PostID=4261 The drag and drop binding navigator lacks a canceledit button a canceledit button is important because if you've already clicked the addnew or started to edit, it's important for obvious reasons. I inherited a binding navigatgor, created the missing buttons, and added the code canceledit to the canceledit item. Yet when I drag and drop a table to a form, the normal bindingnavigator appears. Various forums suggested I submit abug report I've referenced the dll in my main project, and put the inherited bindingnavigator in the toolbox. | |
| Edited by Microsoft on 2005-08-27 at 11:34:31 | |
Thank you for submitting this issue. I'm passing it to the feature team to take a look. -Shamez | |
| Resolved as Won't Fix by Microsoft on 2005-08-30 at 08:46:25 | |
Hi Dennist This is an interesting feature, but not something that we have time to do. Thanks for taking the time to post. Steve Lasker Program Manager Visual Studio Blogs @ http://blogs.msdn.com/smartclientdata/ | |
Another,
T
| I filled an AuthorsListbox with a list of Authors. I set multiple selection to simple, as an article can have more than one author. The article has already been saved and has a unique ID. When I select more than one author I get a duplicate index error. If I change mutlipleselection to one, and save the authors one at a time, the database is updatged properly | |
| Edited by Microsoft on 2005-08-18 at 10:06:53 | |
Thanks for reporting the issue, we are unable to repro the issue with the steps provided. If you could provide us with a sample project/solution that demonstrates the problem and the corresponding repro steps, we would still like to address the issue. Thank you, Vishal, VS2005 Product Team | |
| Resolved as Not Reproduced by Microsoft on 2005-08-25 at 09:10:21 | |
Thanks for your feedback. Since we don’t have enough information to address this issue, we are resolving it Not Repro. Please reopen this issue by changing "Status" to reopened if you would like to provide further details and we will reinvestigate. Thank you, Vishal, VS2005 Product Team | |
That's enough for now.
dennist685
Major shortcomings -will vs2005 fix them?
c o e s u r f
For your first post I'd not sure how more detailed the warning can be. I'm not sure how long you've been programming but the generated warning is pretty standard for almost every compiler I've ever used. It is really pretty simple to understand if you break it apart. An implicit conversion (meaning a conversion that the compiler is automatically generating for you) is being performed on the line specified. The type System.Windows.Forms.CheckState is being coerced to a boolean. This tells me that on this line I am trying to convert a CheckState to a boolean. If the compiler generates a warning then the conversion can be done but you're likely to lose data in some cases. The compiler is doing you a favor by letting you know at compiler time that it might not work as you expected at run time. In this case you should change your code to not simply assign CheckBoxState to a boolean but instead determine when the boolean should be true and code against that (for example Dim b As Boolean = (Me.ActiveCheckBox.CheckState = CheckBoxState.Checked). More correctly however you should probably just use Me.ActiveCheckBox.Checked. For this and other messages that you don't understand your first reference should be MSDN which documents all error messages from the compiler and provides examples on what the problem is and how to solve it.
Don't know what you are talking about with Alt+Enter. I don't think I've every used that key combination in the IDE.
For the BindingNavigator the behavior is what I would expect it to be. The default binding navigator is always used. This makes sense. Just because I wrote a custom navigator doesn't mean I want all my code using it. Imagine referencing a third-party component that defines its own binding navigator. Wouldn't it get annoying if the designer automatically starting using this other navigator when I didn't want it to. In theory the designer could ask you but the goal is a non-instrusive environment. I get annoyed if I have to keep answering questions when I'm trying to do something simple. Besides changing the navigator isn't a common operation so it shouldn't prompt me either way. The best way perhaps would be to expose the navigator through the property grid and let me change it there.
It should be a simple matter to change the binding var to the correct type. It should stick. If it doesn't then that is a bug. I do this all the time with my own controls. I oftentimes start with a standard control and then end up customizing it so much that I create a new derived control. Instead of removing the old control, adding the new one and then resetting all the design-time properties I just change the type of the var in the IDE generated code. With the new refactoring tools this is getting a lot easier. Of course with a table and a binding navigator I'm not sure if it is even exposed enough to do that. It is an interesting feature and hopefully will be added in the future but as it is not something that many people do (the cancel button is more likely to be added) it isn't worth the development time right now.
As for your listbox issue it sounds like a logical error in your code. Without posting the code I'm not sure. I don't understand what you hope MS can do about it. It isn't their code. The ListBox works correctly. If you are using the auto-update feature of a DataSet then you should examine the command being used to update the data. You might have to customize the command (which is fully supported) to meet your needs.
Again I'm sorry that you are frustrated with VS 2005. I have had my frustating moments with the tool and I've submitted more than my fair share of suggestions and bugs but it is important to remember that the goal is provide a stable, feature rich and reliable tool for developers to use. People have been waiting for a long time for .NET 2.0 and VS 2005 and therefore it is critical that MS releases it soon. No software is bug free nor does any software contain every feature that you could hope for. That is why there are subsequent releases. I'm not sure how much experience you have in commercially-driven applications but it is important to both the product and the company to have timely releases that contain enough new features to make it worthwhile for customers to purchase and at the same time not introduce any new defects and not take a long time to be released. Most developers would probably be willing to cut a few features from VS 2005 if it would meaning getting it a few months earlier. It is all part of the software lifecycle management process.
Feel free to post as many questions as you want on the forums. That is why they are here. I would suggest you use the existing forum posts and MSDN to try and answer the questions you might have on your own but otherwise this is the best place to get your answers as it is trolled by some real experts including people from MS. People with MVP next to their names are identified by MS (but not MS employees) as really knowledgeable in their specified areas (for the span of a year) and are generally the most reliable. Hopefully your experiences with VS 2005 will get better. I've been using VS 2005 since the early betas and I have to say it is really solid and feature rich now. It can only get better.
Happy programming,
Michael Taylor - 10/21/05
Greg Fiore
I want to thank you for your thorough answer. You gave me some answers I could use. I've now fixed many of the warnings, mainly with cint, but not all.
There's a few I'll have to ask the forums about, but I'll try more before I do.
I've looked at my code with the listbox and I can't find anything wrong. I tried several variations, but all of them produced the same error. I'll ask about that in one of the vb forums.
I'm not sure what you mean by binding var. Variable How would I use that to add the cancel button
dennist685
JMartin
Hi,
Hmmm... I still haven't used the Release Candidate. But still many of its users are still reporting bugs. Unresolved bugs should not be just left out for the next version, better provide some service pack or something that would address the errors reported in the Feedback Center.
I really hope so...
cheers,
Paul June A. Domag