Thanks for the help. Got it!

Thanks for responding. I don't need the value of the checkbox (in the sender object). Instead, I need the value of the key field for the row clicked (which is in a hidden field in the GridView control). Thanks

This seems like a ridicously easy thing to do but I'm stumped... I have a databound checkbox that I am displaying in a Gridview (template) column. I want to be able to fire a server event whenever a user clicks on a checkbox. Since the gridview control doesn't fire an event when the user clicks on the checkbox, my app can't figure out which row was clicked. The OnCheckedChanged event does work but I can't find a way to pass the key field to the event to identify which checkbox was changed. Any clues on how how to get a checkbox in a GridView control to fire a gridview event when a checkbox is updated by the user? Thanks in advance!

AAArgh 3rd time lucky. I forgot to click Ignore HTML tags. I’m trying to obfuscate the source code for a Clickonce Windows forms project using dotObuscator 4.1 (CE+) edition. The goal is to use MSBuild to script the process. However, I’m still having problems getting the signing process to work. I get the following MSBuild script to run okay but the install fails with a hashvalidation error. Basically my script copies the uses the event to backup the original compiled files and then run dotObuscator. The script then copies the obuscated files to the release\bin directory, signs them and regenerates the manifest. I’ve only included the signing part of the script for clarity. Do I need to sign the EXE file in both the bin\release and obj\release directories? Do I need to sign additional DLLs? It looks like the new manifest is not being generated correctly. Any advice is appreciated. Note: This approach came from an forum thread: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=166236&SiteID=1 (Copy obfuscated files to release\bin and release\obj directory) < SignFile CertificateThumbprint ="0d5ef111f89cf3ccc2eb36fa01a42d411f680704" SigningTarget ="C:\..\bin\Release\sharpSh3ll.dll"/>

Reposting as some of the previous message was missing. I’m trying to obfuscate the source code for a Clickonce Windows forms project using dotObuscator 4.1 (CE+) edition. The goal is to use MSBuild to script the process. However, I’m still having problems getting the signing process to work. I get the following MSBuild script to run okay but the install fails with a hashvalidation error. Basically my script copies the uses the event to backup the original compiled files and then run dotObuscator. The script then copies the obuscated files to the release\bin directory, signs them and regenerates the manifest. I’ve only included the signing part of the script for clarity. Do I need to sign the EXE file in both the bin\release and obj\release directories? Do I need to sign additional DLLs? It looks like the new manifest is not being generated correctly. Any advice is appreciated. Note: This approach came from an forum thread: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=166236&SiteID=1 (Copy obfuscated files to release\bin and release\obj directory) < SignFile CertificateThumbprint ="0d5ef111f89cf3ccc2eb36fa01a42d411f680704" SigningTarget ="C:\..\bin\Release\sharpSh3ll.dll"/>

I’m trying to obfuscate the source code for a Clickonce Windows forms project using dotObuscator 4.1 (CE+) edition. The goal is to use MSBuild to script the process. However, I’m still having problems getting the signing process to work. I get the following MSBuild script to run okay but the install fails with a hashvalidation error. Basically my script copies the uses the event to backup the original compiled files and then run dotObuscator. The script then copies the obuscated files to the release\bin directory, signs them and regenerates the manifest. I’ve only included the signing part of the script for clarity. General questions: Do I need to sign the EXE file in both the bin\release and obj\release directories? Do I need to sign additional DLLs? It looks like the new manifest is not being generated correctly. Any advice is appreciated. Note: This approach came from an forum thread: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=166236&SiteID=1 (Copy obfuscated files to release\bin and release\obj directory) < SignFile CertificateThumbprint ="0d5ef111f89cf3ccc2eb36fa01a42d411f680704" SigningTarget ="C:\..\bin\Release\sharpSh3ll.dll"/>

Okay, The mystery is solved. It turns out that I'm running McAFee antivirus software. It has two browser components that are meant to catch phishing activities. I disabled these two comnponents and everything works fine. BTW, McAfee SUCKS. They have been sending out daily builds recently requiring reboots. These guys are clueless. Note to self, GET RID OF MCAFEE :mad: Thanks to all for helping me work through this.

Fred, Thanks for confirming that I am not going crazy! I cut and pasted your code into an empty ASPX form and still get the same behavior. When I click Cancel on the confirm() dialog, it does a postback! :confused: I've tried running the code from a local IIS and from an ISP and get the same behavior. Unless, you have any suggestions, I guess I need to open an incident with Microsoft to get to the bottom of this. Thanks!

Thanks for responding. I removed the IsPostBack on the load event and it made no difference. The confirm function is executing. The generated code is below. If you hit cancel I was under the impression that no postback would occur. However, it does and the button code click event fires on the server when you click cancel. Is it your understanding that a postback should not occur if you click Cancel on a confirm dialog box? [Delete](javascript:__doPostBack('btnDelete','')) function __doPostBack(eventTarget, eventArgument) { if (!theForm.onsubmit || (theForm.onsubmit() != false)) { theForm.__EVENTTARGET.value = eventTarget; theForm.__EVENTARGUMENT.value = eventArgument; theForm.submit(); } } Thanks for your time.

Michael, Thanks for pointing me to the blog you did on using the prompt funtion. It's helpful but is not solving the problem I'm having. I'm a novice Javascript programmer so it may be something elemental that I'm missing. According to articles I've read on using confirm() is that if the user clicks Cancel to the OK/Cancel prompt, nothing happens (which is what I want). If they click OK, a postback occurs and executes the code in my button click event. What I'm finding is that regardless of whether OK or Cancel is clicked, the client does a postback. This means I have no way of knowing whether they clickede OK or Cancel. Original article: http://aspnet.4guysfromrolla.com/articles/021104-1.aspx (see response http://www.thescripts.com/forum/thread115874.html) I hope this makes sense and thanks in advance for any help.

Thanks, I'll take a look at the samples you pointed to!

I am trying to use a client side confirm dialog box. I have a generic sub (borrowed from an article by Jim Stall) that successfully generates the client side Yes/No dialog box. According to the forums and docs I've read, a postback should only occur if the user clicks OK. This means my server code should only needs to check if OK was pressed. The behavior I'm finding is that a postback occurs regardless of whether the user clicks OK or Cancel. This means I can't detect what was selected. Can someone suggest what I'm doing wrong? Here's the server side code: Public Shared Sub CreateConfirmBox(ByRef btn As WebControls.LinkButton, ByVal strMessage As String) btn.Attributes.Add("onclick", "return confirm('" & strMessage & "');") End Sub The button declaration code: The page load code that calls the button generation code: Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load If Not Page.IsPostBack Then eVSUtils.CreateConfirmBox(btnDelete, "Are you sure you want to delete this user?") End If End Sub Any suggestions on why it does a postback regardless of the button pressed? Thanks!