I'm in a vile mood this morning because someone decided that it would be a
neat idea if too many clicks in the name of a field in the dataset editor
view would cause code bo be generated. As a side effective of this my xsd is
getting messed up and won't compile.
How do I turn that off?
How do I get rid of the excess baggage of <dataSet>.vb when I have no need
for that partial class to contain the code that I don't want generated when I
double click too much?
I know they put office users in rooms at redmond and watch them use the new
stuff. Do they ever do this with the development tools?
Regards,
Al Christoph
Senior Consultant and Proprietor
Three Bears Software, LLC
just right software @ just right prices @3bears.biz
"Gary Chang[MSFT]" - 05 Nov 2005 07:38 GMT
Hi Al,
>How do I turn that off?
I am afraid this behavior is by design in VS2005, there isn't any options
setting to disable it. This is a new code complete feature in VS2005, it
will add some custom common used code function(empty) when user double
clicks the name of a field in the dataset editor.
I am regret this new feature has bring you the inconvenience to your daily
development work, I will forward your concern to our corresponding product
team member, actually this feedback is a good lesson that we should
consider all kind of customer's needs and their usages, and keep our
product's interactive UI consistent with its previous version.
Thanks for your understanding!
Best regards,
Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn
This posting is provided "AS IS" with no warranties, and confers no rights.
Al Christoph - 05 Nov 2005 08:59 GMT
Thanks for the response.
I'm in the process of designing datasets. I'm still figuring out the names
of the columns. The ones in the previous generation were horrible. So I'm
constantly clicking on the name in the edit window (not the properties pane)
to start the edit. If only VB would adopt F2 as edit name ala explorer. That
is an ingrained habit that is soooo bad that I'm about to turn F2 off. I'm
not even sure that I can set F2 to act to open up the edit name window.
If you watched what I had to do to get the names and the captions correct MS
would try to figure out a better way to do it. Hmmm ... may be if I went to
extra large type font on the desk top and undocked the properties window. and
...
The moral of this story is code completion is fine BUT what makes this game
worthwhile is that "Bill Gates Won!" Ergo all MS products should work the
same way. If clicking or double clicking or whatever on a name in Explorer
allows you to edit it, the same should work universally. Ditto F2.
"Bill Gates Won!" implies that all programs work like Excel, Word and
Explorer when it comes to the GUI.
I make a good living making my GUI's do just that and don't have to spend a
lot of time writing help or hand holding.
Regards,
Al Christoph
Senior Consultant and Proprietor
Three Bears Software, LLC
just right software @ just right prices @3bears.biz
> I'm in a vile mood this morning because someone decided that it would be a
> neat idea if too many clicks in the name of a field in the dataset editor
[quoted text clipped - 15 lines]
> Three Bears Software, LLC
> just right software @ just right prices @3bears.biz
[MSFT] - 08 Nov 2005 06:38 GMT
Hello,
I used to also work in this way and I found a double-clcik actually will
open the code editor window. Sometimes this is convenient; Sometimes is not
necessary. Anyway, I didn't found any messed code will be added into XSD
file and make it won't compile. Can you tell more details on this? we may
find a proper solution for this issue.
Luke
Al Christoph - 08 Nov 2005 11:28 GMT
Unfortunately, I've gotten better at the IDE and at dataset and xsd
manipulation so I can't really be helpful at this point. I'm also doing real
debugging i.e. figuring out my own stupid mistakes that make the code not
produce the right numbers. Soooo I can't really provide anymore information
at this time.
I'm also still working with the last release candiate on one box. Need to
bite the bullet and get it up to date.
But the one thing that I did consistently observe with some now unknown
earlier VS 2005 and after some unknown activity was a complete doubling of
all the code in the <dataset>.designer.vb module.
Thanks for your interest. Sorry that I can't be more helpful at this time.
Oh yes, in regard to some of my other mechanical complains. I found that by
going to the default keyboard and fixing up the few VB6 shortcuts that I want
I have a lot less trouble:-) Believe Me, F2 no longer brings up the object
browser.
Regards,
Al Christoph
Senior Consultant and Proprietor
Three Bears Software, LLC
just right software @ just right prices @3bears.biz
> Hello,
>
[quoted text clipped - 5 lines]
>
> Luke
[MSFT] - 09 Nov 2005 09:24 GMT
Thank you for the feedback. If there is any related question, please feel
free to post in the newsgroup. We are welcome to listen your any opinions
and feedback on MS products.
Luke