eval() is not necessary. This will work fine:
var date = new Date(parseInt(jsonDate.substr(6)));
The substr() function takes out the /Date( part, and the parseInt() function gets the integer and ignores the )/ at the end. The resulting number is passed into the Date constructor.
I have intentionally left out the radix (the 2nd argument to parseInt); see my comment below.
Also, I completely agree with Rory's comment: ISO-8601 dates are preferred over this old format - so this format generally shouldn't be used for new development.
For ISO-8601 formatted JSON dates, just pass the string into the Date constructor:
var date = new Date(jsonDate); //no ugly parsing needed; full timezone support
Server.MapPath specifies the relative or virtual path to map to a physical directory.
Server.MapPath(".")1 returns the current physical directory of the file (e.g. aspx) being executedServer.MapPath("..") returns the parent directoryServer.MapPath("~") returns the physical path to the root of the applicationServer.MapPath("/") returns the physical path to the root of the domain name (is not necessarily the same as the root of the application)
An example:
Let's say you pointed a web site application (http://www.example.com/) to
C:\Inetpub\wwwroot
and installed your shop application (sub web as virtual directory in IIS, marked as application) in
D:\WebApps\shop
For example, if you call Server.MapPath() in following request:
http://www.example.com/shop/products/GetProduct.aspx?id=2342
then:
Server.MapPath(".")1 returns D:\WebApps\shop\productsServer.MapPath("..") returns D:\WebApps\shopServer.MapPath("~") returns D:\WebApps\shopServer.MapPath("/") returns C:\Inetpub\wwwrootServer.MapPath("/shop") returns D:\WebApps\shop
If Path starts with either a forward slash (/) or backward slash (\), the MapPath() returns a path as if Path was a full, virtual path.
If Path doesn't start with a slash, the MapPath() returns a path relative to the directory of the request being processed.
Note: in C#, @ is the verbatim literal string operator meaning that the string should be used "as is" and not be processed for escape sequences.
Footnotes
Server.MapPath(null) and Server.MapPath("") will produce this effect too.
Best Answer
You can only have one script manager per page but you can have multiple proxies.
Used if you have the script manager in your master for instance which will go across all pages but you want a script manager reference in an underlying page or user control. In that instance you would add the proxy. If you added another script manager the page would error.
The offical MSDN documentation gives the details.