How to customize logon background/screen in windows 7

How to customize logon background/screen in windows 7

If you don’t like the default logon background of windows 7,or you want to change the background to a picture you like,you can do it easily in windows 7 without any third-party softwares.Below will give you a simple guide about how to do it.

source: http://www.windows7home.net/how-to-customize-logon-backgroundscreen-in-windows-7/

Advertisements

Stocate modificate in utlima vreme

alternativa la view dependencies

select * from sys.objects so JOIN sys.syscomments sc ON so.object_id=sc.id WHERE type=’P’ and text like ‘%ReservationCityFees%’
====================================================

ce stocate au fost modificate in utlimele 7 zile

SELECT name
FROM sys.objects
WHERE type = ‘P’
AND DATEDIFF(D,modify_date, GETDATE()) < 7

Loose Typing in Javascript

What is Loose Typing?

Well, this seems like a good place to start. It is important to understand both what loose typing is, and what loose typing is not. Loose typing means that variables are declared without a type. This is in contrast to strongly typed languages that require typed declarations.

Consider the following examples:

  1. /* JavaScript Example (loose typing) */  
  2. var a = 13; // Number declaration  
  3. var b = “thirteen”; // String declaration  
  4.   
  5. /* Java Example (strong typing) */  
  6. int a = 13; // int declaration  
  7. String b = “thirteen”; // String declaration  

Notice that in the JavaScript example, both a and b are declared as type var. Please note, however, that this does not mean that they do not have a type, or even that they are of type “var”. Variables in JavaScript are typed, but that type is determined internally. In the above example, var a will be type Number and var b will be type String. These are two out of the three primitives in JavaScript, the third being Boolean.

Source: http://blog.jeremymartin.name/2008/03/understanding-loose-typing-in.html

‘Operation is not valid due to the current state of the object’ error during postback

Error:

System.InvalidOperationException: Operation is not valid due to the current state of the object.

[InvalidOperationException: Operation is not valid due to the current state of the object.]    System.Web.HttpValueCollection.FillFromEncodedBytes(Byte[] bytes, Encoding encoding) +11372207    System.Web.HttpRequest.FillInFormCollection() +329

[HttpException (0x80004005): The URL-encoded form data is not valid.]    System.Web.HttpRequest.FillInFormCollection() +11486290    System.Web.HttpRequest.get_Form() +157    System.Web.HttpRequest.get_HasForm() +11487092    System.Web.UI.Page.GetCollectionBasedOnMethod(Boolean dontReturnNull) +141    System.Web.UI.Page.DeterminePostBackMode() +100    System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Uncaught Sys.WebForms.PageRequestManagerServerErrorException: Sys.WebForms.PageRequestManagerServerErrorException: An unknown error occurred while processing the request on the server. The status code returned from the server was: 500

Solution:

<appSettings>
  <add key="aspnet:MaxHttpCollectionKeys" value="1001" />
</appSettings>

Microsoft recently (12-29-2011) released an update to address several serious security vulnerabilities in the .NET Framework. One of the fixes introduced by MS11-100 temporarily mitigates a potential DoS attack involving hash table collisions. It appears this fix breaks pages that contain a lot of POST data. In our case, on pages that have very large checkbox lists. Why would this be the case?

Some non-official sources seem to indicate that MS11-100 places a limit of 500 on postback items. I can’t find a Microsoft source that confirms this. I know that View State and other framework features eat up some of this limit.

source: http://stackoverflow.com/questions/8684049/asp-net-ms11-100-how-can-i-change-the-limit-on-the-maximum-number-of-posted-for

Alternative reading: http://www.webreference.com/programming/asp/ASPNet-Exception-Handling/index.html