Search results matching tag 'workaround'

Re: RC DropDownList helper - still seriously flawed?

simeyla — Thu, 29 Jan 2009 05:00:00 GMT

assuming that they put back some overloads with SelectList - and I think they most likely will then this is the current workaround I'm using in anticipation of SelectList overloads:

ViewData.Model.MilitaryData.Services is of type SelectList

<%= Html.DropDownList("Service", ViewData.Model.MilitaryData.Services.Items.OfType<SelectListItem>(), "Select Service")%>

I'm very confused about how we're supposed to use it and why a SelectList is so determined to remember its own state. I assumed it was something to do with how it round-trips its state which i think makes sense. My impression now is they got themselves all confused for RC1 and that most likely these overloads will be returning soon.

The wording in the release notes regarding SelectList definitely implies they intended to ADD overloads and not replace them.

I'm using my workaround and I'll come and revisit the issue for RC2

Re: ScriptManager.RegisterClientScriptBlock and Combobox Issue in Mozilla

cBueno — Fri, 14 Nov 2008 05:00:00 GMT

I found a workaround.

A similar bug occurred with Firefox 2.0.0.1. I´ve tried several alternative but just a javascript trick solve the problem.

Here is the workaround:

ScriptManager.RegisterStartupScript(Button1, typeof(Button), "scriptkey", "window.setTimeout(\"alert('test!')\",0);", true);

with window.setTimeout, the dropdowns will work properly after the alert.

Re: Compression does not work with UpdatePanel 2

d.marzo — Tue, 21 Oct 2008 04:00:00 GMT

This is a bug (nasty), compress update panel response its high performance improvement,
reported at Microsoft Connect: https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=357565

Expected to be fixed at 3.5.

But... Too much people work with 2.0 (include us), and dont want compress at IIS level.

We play for a while and try to find a workaround, we found, but we need feedback and advice.

You could see description at:

https://connect.microsoft.com/VisualStudio/feedback/Workaround.aspx?FeedbackID=357565

And download source code:

http://www.solnatec.com/archive/public/2008/CompressAjaxResponse.zip

Thanks in advance.

David Marzo
www.solnatec.com

Re: Session Timeout

MaheshIndia — Thu, 10 Jul 2008 04:00:00 GMT

How to set session timeout limit for a web-application.
The setting that you need to modify to use session management is the <sessionstate> node present in web.config file.following is demo syntax .
<sessionstate
mode = "inproc" | "sqlserver" | "stateserver"
cookieless = "true" | "false"
timeout = <session timeout in minutes>
sqlconnectionstring = <connection string>
server = <server name>
port = <port number>
/>

Timeout tab is used to configure the ASP.NET session timeout limit for the whole application.You need to change timeout tab as per your need.
The following is the example where we are assigning timeout limit to 20 minute in web.config file.
<sessionstate
mode="inproc"
cookieless="false"
timeout="20" <----- This is timeout number in minute.
sqlconnectionstring="data source=127.0.0.1;user id=sa;password="
server="127.0.0.1"
port="42424"
/>

There is another setting i.e. in IIS.

Internet Information Services Setting
you have to change settings from Control Panel >> Internet Information Services.
1) IIS >> Default WebSite >> Properties >> Home Directory >> Configuration >> Option >> Session timeout change to 20 minutes.

2) IIS >> Default WebSite >>your webapplication >> Properties >> ASP.Net. >> Click on “Edit Configuration”. >> On State Management set Session timeout to 20 minutes.

now your application will automatically logout if no activity occurs for last 20 min.if you want your application will logout after x min then change 20 by x number into setting.

Re: Validation of viewstate MAC failed / The state information is invalid for this page and might be corrupted

dbrook007 — Sat, 28 Jun 2008 04:00:00 GMT

I have had this problem in a shared hosting environment.

After testing, I discovered that I could experience this problem with even the most basic of web pages, consisting of only a couple of ASP.Net labels and an ASP.Net button.

Working within a Session, the pages and site function fine.

The problem occurs after a period of the site being idle, without activity.

The problem I have been having was not related to quick-clicking of the mouse.

This is when, upon a postback, the problem occurs.

My initial thought was that it was connected with the Session timing-out. However, further tests showed that this problem did NOT always occur after a period of inactivity longer than the Session timeout. This did not make sense, as it should replicate each time if this is the problem.

I then discovered that the IIS Application Pool was recycling also after a period of inactivity. This led me to wonder about the MachineKey in the machine.config file on the server.

I have been assured by the hosting company that they are not using a web farm or cluster.

So my first question is, if the IIS Application Pool is recycled, would a new MachineKey for validation/decryption be generated?

My second question is, how often should and IIS Application Pool recycle on inactivity?

I believe the default is 5 minutes?

However, a few people have told me that this is not a good idea, especially if the Session timeout is defaulted at 20 minutes.

Surely, the IIS recycle idle timeout should be >= the Session idle timeout?

Can anyone tell me if this is a problem only experienced with Ajax-enabled websites?

I noted this thread, and am probably going to test with a manual MachineKey in the web.config.

Can anyone tell me if this is an acceptable solution, and/or if there are any risks?

Lastly, please see this markup:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" >
<head><title>
	Untitled Page
</title></head>
<body>
    <form name="aspnetForm" method="post" action="GenKey.aspx" id="aspnetForm">
<div>
<input type="hidden" name="__VIEWSTATE" id="__VIEWSTATE" value="/wEPDwUKMTIyNzk5MzE0Mg9kFgJmD2QWAgIDD2QWAgIBD2QWBAIBDw8WAh4EVGV4dAWAAUE4MDg3NUQ0NUVCOTNEQUEzMUU5OEMzQUNBMDMyNEM0NzI2NzNEMEY5RDdGNTNCRkQxQkFEOTA1RUYxRjQyNTVFRDBERDVEN0VEQjQxODNDNEYwNjk1MkMxNTYwNzMwQ0YyM0FENzJFMkM2Q0I2OTE4QUM2NDY3RUZGMzMwQkY1ZGQCBQ8PFgIfAAVANjk2NTc5RDk5MjU1QkQzNTUxQzcxMUI5MjRGRUY2QzQ5OEY5RUUwNTZCNTQxN0Q1MUM1NjhCRUUwNzIwNEU2NmRkZK4c9eoRzrWCRMex0oFKRHSn8It0" />
</div>

    <div>
        
    Validation Key (SHA1, 64 bytes - 128 hexadecimal characters):<br />
    <textarea name="ctl00$ContentPlaceHolder1$validationKeyTextBox" rows="2" cols="20" id="ctl00_ContentPlaceHolder1_validationKeyTextBox" style="height:64px;width:592px;">A80875D45EB93DAA31E98C3ACA0324C472673D0F9D7F53BFD1BAD905EF1F4255ED0DD5D7EDB4183C4F06952C1560730CF23AD72E2C6CB6918AC6467EFF330BF5</textarea> 
    <br />
    <input type="submit" name="ctl00$ContentPlaceHolder1$genKeyButton" value="Generate" id="ctl00_ContentPlaceHolder1_genKeyButton" /><br />
    <br />
    Decryption Key :<br />
    <textarea name="ctl00$ContentPlaceHolder1$decryptionTextBox" rows="2" cols="20" id="ctl00_ContentPlaceHolder1_decryptionTextBox" style="height:64px;width:592px;">696579D99255BD3551C711B924FEF6C498F9EE056B5417D51C568BEE07204E66</textarea><br />
    <input type="submit" name="ctl00$ContentPlaceHolder1$decryptButton" value="Generate" id="ctl00_ContentPlaceHolder1_decryptButton" />

    </div>
    
<div>

	<input type="hidden" name="__EVENTVALIDATION" id="__EVENTVALIDATION" value="/wEWBQK76qXuDAL4v+vCAwK35aLpBQLEkYMtAv2nzrMPpL6kdbdU58mIZVgpcXkMCUg2Uqc=" />
</div></form>
</body>
</html>

I noted that the "__EVENTVALIDATION" appears at the bottom of the form. Is this not likely to cause problems? Would there be implications for partial page postbacks using Ajax-enabled sites?

Many thanks,
Darren

Re: Problem to set focus to auto complete extender

PJonDevelopment — Tue, 24 Jun 2008 04:00:00 GMT

Hi Francis,

Just in case you haven't yet found a solution, sometimes a simpler workaround might do the trick.

Did you try doing the following?

1    <label id='<%= Me.txtSample.ClientID & "_LABEL" %>' for="<%= Me.txtSample.ClientID %>">Caption:</label>
2    <asp:TextBox runat="server" ID="txtSample" />
3    <script type="text/javascript">
4    function SetFocus()
5    {
6      document.getElementById('<%= Me.txtSample.ClientID & "_LABEL" %>').click();
7    }
8    </script>
9

Re: Validation of viewstate MAC failed / The state information is invalid for this page and might be corrupted

loginitin — Mon, 28 Apr 2008 04:00:00 GMT

One of the causes of this error was session time out so i tried this

    Protected Sub Timer1_Tick(ByVal sender As Object, ByVal e As System.EventArgs) Handles Timer1.Tick
        T2.Text = ""
    End Sub

<asp:Timer ID="Timer1" OnTick="Timer1_Tick" runat="server" Interval="300000">
</asp:Timer>
<asp:UpdatePanel ID="T1" runat="server">
<Triggers>
<asp:AsyncPostBackTrigger ControlID="Timer1" EventName="Tick" />
</Triggers>
<ContentTemplate>
<asp:Label ID="T2" runat="server"></asp:Label>
</ContentTemplate>
</asp:UpdatePanel>

this makes an async post back to the server every 5 minutes and thus the session does not expire, it seems to have reduced the error by 90%

let's see

AutoComplete Extender

mattsaltz@live.com — Sat, 15 Mar 2008 04:00:00 GMT

In the sample for the Ajax Autocomplete Extender they have this code:

If i have this code after my extender my button on the usercontrol not longer works.
Do i need this code, do i need to change aspnetForm to something?

Re: AlwaysVisibleControl makes it possible to scroll forever in IE

mtv — Thu, 31 Jan 2008 05:00:00 GMT

I concocted a technique which (if the user has JavaScript enabled) prevents a particular element (div in my case) from being resized smaller than a certain height (should work for width as well); not sure if that would help for your case or not. I seem to recall that it isn't possible to set the browser window size using JavaScript because it is prevented for security reasons. You could also open your page in a pop up window using JavaScript and prevent it from being resized at all, but then users can't resize the window to make it larger either.

Acknowledgments to Andy Langton at http://andylangton.co.uk/articles/javascript/get-viewport-size-javascript/ for his cross-browser get viewport size function

On my page I have a div as follows:

<div style="width: 100%; height:415px; overflow:auto; margin-right:20px" id="divContent">

<!-- insert content here --> 

</div>

Disclaimer: This div is actually on a content page, and the ContentPlaceHolder is inside a table cell on the Masterpage. The table is 800px wide, so with no cellpadding/spacing, divContent will be 800px wide (100%). Don't see why that particular rather unusual setup would be required, however.

I used the following JavaScript to make the div automatically change height when the window is resized, and to enforce a minimum height (415px) for the div:

function getWindowHeight() 
{ 
 var viewportheight;
 
 // the more standards compliant browsers (mozilla/netscape/opera/IE7) use window.innerWidth and window.innerHeight
 
 if (typeof window.innerWidth != 'undefined')
 {
    viewportheight = window.innerHeight;
 }
 
// IE6 in standards compliant mode (i.e. with a valid doctype as the first line in the document)

 else if (typeof document.documentElement != 'undefined'
     && typeof document.documentElement.clientWidth !=
     'undefined' && document.documentElement.clientWidth != 0)
 {
    viewportheight = document.documentElement.clientHeight;
 }
 
 // older versions of IE
 
 else
	{		
    viewportheight = document.getElementsByTagName('body')[0].clientHeight;
	}	
	return viewportheight; 
} 
 
window.onresize = resize;
window.onload = resize;

function resize() {  
		var docheight = getWindowHeight();
		var dv = document.getElementById('divContent');		
      if (docheight > 650)
			{
				docheight = docheight - 235;
				dv.style.height = docheight + 'px';
			}
			else
			{
				dv.style.height = '415px';
			}      
}

The subtraction of 235 pixels is a result of the navigation bar on my Masterpage which is 235 pixels high. If you want your div to take up the full height of the window then you can just chuck that line.

Kind of a funky almost-solution to your question about enforcing minimum size. It worked out for what I needed to do, so hopefully it might for you or someone else!

Re: ModalPopupExtender + iFrame + Google Maps = Off Center Map

blkbam — Mon, 21 Jan 2008 05:00:00 GMT

I found the reason for the problem and a workaround. I don't totally understand the cause but it has to do with the iFrame being loaded while invisible. If you load the page bring up the ModalPopUp Extender before iFrame loads, it is centered correctly. If you wait and let it load while invisible, it will render off center. Now, it just dynamically create the iFrame instead of having it load when the page loads

Workaround:

<script type="text/javascript">
        function showDialog()
        {
            var modalPopupBehaviorCtrl = $find('<%= mpeMap.ClientID %>');
            modalPopupBehaviorCtrl.show();
            document.getElementById('divMap').innerHTML = '<iframe runat="server" id="mm" width="600" height="450" frameborder="0" scrolling="no" marginheight="0" marginwidth="0" src="minimap2.aspx?lat=39.86887222271858&long=-75.35767078399658&desc=just%26a%26sample"></iframe><br />';
        }
    </script>
    <form runat="server" action="">
        <ajaxToolkit:ToolkitScriptManager ID="ScriptManager1" runat="server" />

        <a id="showModalPopupClientButton" href="#" runat="server" onclick="showDialog();">Click Me</a><br /><br /><br />
        <asp:LinkButton ID="LinkButton1" runat="server">LinkButton</asp:LinkButton>

        <asp:Panel runat="server" ID="Panel1" Style="display:inherit;width:600px;height:475px;" CssClass="modalPopup">
            <div id="divMap"></div>
            <asp:Button runat="server" ID="cmdClose" Text="Close" />
        </asp:Panel>
        
        <iframe id="test" width="600" height="450" frameborder="0"  scrolling="no" marginheight="0" marginwidth="0" src="minimap2.aspx?lat=39.86887222271858&long=-75.35767078399658&desc=just%26a%26sample"></iframe><br />

        <ajaxToolkit:ModalPopupExtender ID="mpeMap" runat="server" 
            TargetControlID="LinkButton1" 
            PopupControlID="Panel1"
            BackgroundCssClass="modalBackground"
            DropShadow="true"
            CancelControlID="cmdClose"
            OkControlID="cmdClose"
        />
    </form>