ASP.NET

Pankaj Garg wrote:

but also opening the same page i pop up window

string a = "The code project website is blah blah blah...";
int index = a.IndexOf("is"); // gets the index of 'is'.
int startIndex = 0;
int length = index + 1; //the length of the string
a.Substring(startIndex, length);//returns the new string...

int index = a.IndexOf("is"); // gets the index of ' is '.
int startIndex = 0;
int length = index; //the length of the string

Vri SSK wrote:

if the domains are truly both in "website.com", just issue the cookie once and set the domain attribute of the cookie to "website.com". Then the cookie will automatically be useable in both domains since both sites share a common portion of their DNS name.

Vri SSK wrote:

The prop system is ATN's way of ensuring that user information is homogenous across the different systems in the DCI namespace. At the heart of this system is a database containing default information on users: their userid, uid, gid, gecos field, home directory, and default shell. Using the propclient tool in conjunction with a local configuration file, this system will update your local password files with the information housed in the database. To use the system, create a /etc/prop.cfg file on your local machine. An example file can be found at /afs/isis.unc.edu/@sys/etc/prop.cfg. Copy this file to your /etc directory and customize it to your system (instructions on how to do that are contained in the file itself). Then run the propclient as root and it will automatically update the password files on your local system.

Vri SSK wrote:

ASP.NET 2.0 was a major improvement upon web development everywhere. One very powerful aspect of ASP.NET 2.0 is the ability to make your web application personalizable using the Web Part framework. With the launch of MOSS (Microsoft Office SharePoint Server 2007) many companies and developers have rekindled focus on utilizing this amazing tool. This article will start with the basics of understanding web parts and personalization.