By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,667 Members | 1,740 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,667 IT Pros & Developers. It's quick & easy.

Mind-boggling issue - text box not updating on Vista

P: n/a
Hello:

We are working in VS 2005, C# with Team System. We have a text box
that is bound to a business object property. We have some code behind
that will populate the text box when they choose a value from a
validation form. It works on everyone's machine, except for the one
that deploys using Click Once. We have debugged the code, watched the
value get returned by the validation form, see the business object
property be set to the new value, see the DataTable reflect the
change . . . and yet, the text box doesn't change on the interface.

Well, I thought maybe the validation form returned the wrong
DialogResult, or maybe we missed assigning the value, or maybe the
business object property setter wasn't written correctly, or that the
DataTable was invalid. Debugging showed these all work well. So, I
figured that machine wasn't getting the latest version from source
control. We diff'd our source and confirmed they were identical.

Why isn't that text box being changed? The only thing different is
that the deployment machine is Vista.

Is there something about Vista that would prevent code behind from
updating a text box? Are there problems with binding in Vista?

We are at a loss. It doesn't seem to make any sense. Has anyone seen
anything like this? For now, if we deploy from another machine, we
don't have any issues. Please ask if you need more details.

Thanks,
Travis
Jul 14 '08 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Are you talking about a web page here? Is it possible that machine has
something like Roboform or some other form-filling software that overwrites
the value after the page is rendered in the browser?

<je**********@gmail.comwrote in message
news:95**********************************@p25g2000 hsf.googlegroups.com...
Hello:

We are working in VS 2005, C# with Team System. We have a text box
that is bound to a business object property. We have some code behind
that will populate the text box when they choose a value from a
validation form. It works on everyone's machine, except for the one
that deploys using Click Once. We have debugged the code, watched the
value get returned by the validation form, see the business object
property be set to the new value, see the DataTable reflect the
change . . . and yet, the text box doesn't change on the interface.

Jul 14 '08 #2

P: n/a
On Jul 14, 3:30*pm, "Josh Valino" <no spam pleasewrote:
Are you talking about a web page here? *Is it possible that machine has
something like Roboform or some other form-filling software that overwrites
the value after the page is rendered in the browser?
Nope, a Windows Form.
Jul 14 '08 #3

P: n/a
McAfee AV running? If so, disable all traces of your AV (disconnect from the
Internet, if worried) and try again. iirc, McAfee 8.0i caused that specific
problem... it effects all languages (including VB6) and was some kind of
"buffer overflow prevention" mess that caused it.

<je**********@gmail.comwrote in message
news:a2**********************************@y38g2000 hsy.googlegroups.com...
On Jul 14, 3:30 pm, "Josh Valino" <no spam pleasewrote:
Are you talking about a web page here? Is it possible that machine has
something like Roboform or some other form-filling software that
overwrites
the value after the page is rendered in the browser?
Nope, a Windows Form.
Jul 14 '08 #4

P: n/a
On Jul 14, 4:09*pm, "Ken Halter"
<Ken_Halter@Use_Sparingly_Hotmail.comwrote:
McAfee AV running? If so, disable all traces of your AV (disconnect from the
Internet, if worried) and try again. iirc, McAfee 8.0i caused that specific
problem... it effects all languages (including VB6) and was some kind of
"buffer overflow prevention" mess that caused it.
Gte this: if we deploye from the Vista machine, all the XP machines
deployed to will show the same issue. If we deploy from an XP machine,
they work.

We were thinking security also . . . bu then why would it persist to
the other machines?

Still searching . . .
Jul 15 '08 #5

This discussion thread is closed

Replies have been disabled for this discussion.