Link Buttons Fail in Published Website

qdd · September 7th, 2007, 09:35 AM

I am debugging on the production server using Visual Studio 2005 Express Edition.

I have compiled the website on the production server. I was not able to find a \bin directory and if I remove the aspx.vb files, I receive an error message that the aspx.vb file cannot be found. Perhaps the build failed somehow?

Production vs. development appear to be rendering correctly. How would I check if the right version of ASP.NET is selected on the server application? Are other postbacks firing correctly?

What about if you create a very simple page with a couple different controls and see if some simple operations work so you can rule out a fundamental problem? - The simple page shows the same problem behavior.

Imar · September 7th, 2007, 09:59 AM

As Peter said, and as I suggested in my message: are other postbacks firing?

What happens if you use IE on the server to look at the app on the development machine? Does that work?

Imar

---------------------------------------
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Everyone is unique, except for me.
Author of ASP.NET 2.0 Instant Results and Beginning Dreamweaver MX / MX 2004

qdd · September 7th, 2007, 12:46 PM

Hi Imar - yes, other postbacks are firing. The development version of the app is on the production server. I can't get the development version to open unless I open it through Visual Web Developer.

Bill

Imar · September 7th, 2007, 03:06 PM

I think I am out of ideas then. But I still think it's a browser thing, rather than a server thing because of what you said earlier:

Quote:

quote:As an experiment, I added a button control, "button1" with the exact same code - and it works, while the linkbutton does not:

These controls give you the following HTML:

Code:

<div>
  <a id="LinkButton1" href="javascript:__doPostBack('LinkButton1','')">LinkButton</a>
  <input type="submit" name="Button1" value="Button" id="Button1" />
</div>

The LinkButton requires JavaScript, while the Button ends up as a simple submit button that doesn't require JavaScript.

Might be worth investigating, although I cannot recommend anything on how to actually do that....

Imar

---------------------------------------
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Everyone is unique, except for me.
Author of ASP.NET 2.0 Instant Results and Beginning Dreamweaver MX / MX 2004

qdd · September 10th, 2007, 08:03 AM

Imar, you were correct. I found the problem on my customer's server. He had set custom settings for Internet Explorer Security: Scripting > Active scripting > Disable, so any controls using Javascript failed. I simply changed this to "Enable" and it now works fine. Thanks Peter, Imar and Doug for your help.

Bill

Imar · September 10th, 2007, 01:29 PM

It just had to be something like that.... Glad it's working now....

Imar

---------------------------------------
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Everyone is unique, except for me.
Author of ASP.NET 2.0 Instant Results and Beginning Dreamweaver MX / MX 2004