Srinivasa Rao Gottipalli

Visual WebGui is an open source rapid application development framework for graphic user interfaces of IT web applications. Visual WebGui lets you cut down development time and risk factors to the minimum, throughout the life cycle of the application, without compromising on performance, security or complexity. Visual WebGui is the only framework that provides seamless integration to Visual Studio and the .NET framework which extends the paradigms of ASP.NET in both design-time and run-time to support WinForms development for web. Visual WebGui offering is unique and not more of the same (150 AJAX frameworks)! Visual WebGui replaces all of the ASP.NET methodologies which were designed for developing sites, with WinForms methodologies, which were designed for developing applications. To demonstrate one of the differences, Visual WebGui is the only framework that is provided with a designer that was designed for application interfaces (WinForms designer) instead of a word documents (ASP.

ISAPI_Rewrite is a powerful URL manipulation engine based on regular expressions. It acts mostly like Apache's mod_Rewrite, but is designed specifically for Microsoft's Internet Information Server (IIS). ISAPI_Rewrite is an ISAPI filter written in pure C/C++ so it is extremely fast. ISAPI_Rewrite gives you the freedom to go beyond the standard URL schemes and develop your own scheme. What you can do with ISAPI_Rewrite: Optimize your dynamic content like forums or e-stores to be indexed by a popular search engines. *Block hot linking of your data files by other sites. *Develop a custom authorization scheme and manage access to the static files using custom scripts and database. *Proxy content of one site into directory on another site. *Make your Intranet servers to be accessible from the Internet by using only one Internet server with a very flexible permissions and security options. *Create dynamic host-header based sites using a single physical site. *Create virtual directory

if you find that the Query Optimizer has not chosen the ideal index for best performance. Normally, if the following conditions are met, the Query Optimizer will automatically consider the use of an indexed view if one exists when running a query: SQL Server 2000/2005 Enterprise Edition is used. These options are set to on: ANSI_NULLS ANSI_PADDING ANSI_WARNINGS ARITHABORT CONCAT_NULL_YIELDS_NULL QUOTED_IDENTIFIERS This option must be set to off: NUMERIC_ROUNDABORT But if you find that the index on the indexed view is not optimal, you can specify which index to use in an indexed view if you do the follow two steps: Use the NOEXPAND hint, which tells the Query Optimizer to treat the view like a table with a clustered index, and . . . Use the INDEX hint to specify which index to use. The syntax is: INDEX ( index_val [ ,...n ] ) where index_val is the name or index ID of the index in the indexed view. If you want to force a clustered index scan of the indexed view, use: "INDEX(0)"

While views are often convenient to use, especially for restricting users from seeing data they should not see, they aren't always good for performance. So if database performance is your goal, avoid using views (SQL Server 2000/2005 Indexed Views are another story). Views can slow down queries for several different reasons. For example, let's look at these two SELECT statements: SELECT * FROM table_name SELECT * FROM view_name Which is faster? If you test it, you will find that the first SELECT statement is faster, although the execution plan for both of them will be the same. How can that be? This is because it takes SQL Server extra work (such as looking up data in the system tables) before it can execute the view. This extra work is not part of the execution plan, so it appears that the two SELECT statements should run at the same speed, which they don't, because some of the work SQL Server is doing is hidden. Another way views can hurt performance is when JOINs or UNIO

Deadlocking occurs when two user processes have locks on separate objects and each process is trying to acquire a lock on the object that the other process has. When this happens, SQL Server identifies the problem and ends the deadlock by automatically choosing one process and aborting the other process, allowing the other process to continue. The aborted transaction is rolled back and an error message is sent to the user of the aborted process. Generally, the transaction that requires the least amount of overhead to rollback is the transaction that is aborted. As you might imagine, deadlocks can use up SQL Server's resources, especially CPU power, wasting it unnecessarily. Most well-designed applications, after receiving a deadlock message, will resubmit the aborted transaction, which most likely can now run successfully. This process, if it happens often on your server, can drag down performance. If the application has not been written to trap deadlock errors and to automatically

These points will difinitely increase the performance. I mean it. 1. Defrag Disk to Speed Up Access to Data One of the factors that slow the performance of the computer is disk fragmentation. When files are fragmented, the computer must search the hard disk when the file is opened to piece it back together. To speed up the response time, you should monthly run Disk Defragmenter, a Windows utility that defrags and consolidates fragmented files for quicker computer response. * Follow Start > All Programs > Accessories > System Tools > Disk Defragmenter * Click the drives you want to defrag and click Analyze * Click Defragment 2. Detect and Repair Disk Errors Over time, your hard disk develops bad sectors. Bad sectors slow down hard disk performance and sometimes make data writing difficult or even impossible. To detect and repair disk errors, Windows has a built-in tool called the Error Checking utility. It’ll search the hard disk for bad sectors and system errors and repair

Following are the language conversion links: Convert C# to VB.net http://www.kamalpatel.net/ConvertCSharp2VB.aspx http://www.eggheadcafe.com/articles/cstovbweb/converter.aspx Convert VB.net to c# http://www.developerfusion.co.uk/utilities/convertvbtocsharp.aspx

When the user enters information in a form and clicks Submit , there are two ways the information can be sent from the browser to the server: in the URL, or within the body of the HTTP request. The GET method, which was used in the example earlier, appends name/value pairs to the URL. Unfortunately, the length of a URL is limited, so this method only works if there are only a few parameters. The URL could be truncated if the form uses a large number of parameters, or if the parameters contain large amounts of data. Also, parameters passed on the URL are visible in the address field of the browsernot the best place for a password to be displayed. The alternative to the GET method is the POST method. This method packages the name/value pairs inside the body of the HTTP request, which makes for a cleaner URL and imposes no size limitations on the forms output. It is also more secure. ASP makes it simple to retrieve name/value pairs. If the forms output is passed after the question mark (?

SQL Server 2008 delivers on the following four key areas of the Microsoft data platform vision: Mission-critical platform – SQL Server 2008 enables organizations to run their most complex applications on a secure, reliable, and scalable platform while enabling IT to reduce the complexity of managing their data management infrastructure. SQL Server 2008 provides a secure and trusted platform by securing valuable information in existing applications and enhancing the availability of the data. SQL Server 2008 introduces an innovative policy-based management framework that enables policies to be defined for explicit and automated administration of server entities across one or multiple servers. In addition, SQL Server 2008 delivers predictable query performance with an optimized platform. Dynamic development – SQL Server 2008 along with the .NET Framework reduces the complexity of developing new applications. The ADO.NET Entity Framework enables developers to be more productive by working

Namespace assignment for Web Service proxies is not the most intuitive thing in the world since it's usually auto-generated. By default, the namespace is the name of the project dot name of the WebService. Here's a little tip that I use when I can't get it right the first time: Go into the client project's Web References directory, the directory for your Web Service and open the generated proxy file (WebService.cs). At the very top you'll find the fully qualified namespace for the Web Service proxy which is what you need in order to access the Web Service methods from your code. You can either type the fully qualified namespace path plus the class name each time you create a reference to the object or you can add it to your namespace references at the top of the class. Another hint – try to name your namespaces consistently. Avoid using the same name for a namespace and a class. When you create a project, create all client code in the scope of that namespace so othe

.Net supports data access through ADO.Net which provides a generic mechanism to access data. Unlike previous versions of data connector technology Microsoft decided to break with tradition and provide a customized library for SQL Server meant to improve performance by bypassing the high level OleDb API to access the database engine. The SqlClient namespace provides access to the SQL Server specific versions of objects for connecting and accessing the database while the OleDb namespace houses the same functionality for the generic OleDb driver access. You can use either for accessing SQL Server, but the SqlClient objects will be somewhat faster and specifically tuned for SQL Server. In practice this means if you want to use the Sql Server specific classes you will need to bracket your code if you also want to support other data sources because the object names vary for each of the class libraries. All Sql Server objects start with Sql like SqlConnection, SqlCommand and SqlDataAdapter, w

DataSets internally represent data in XML format and there's practically no overhead involved in generating XML from data contained within it. Depending on which parts of a DataSet object you access the representation of that data can always presented as XML. DataSets are also very flexible in dealing with incoming XML data. Pass it some data in XML format and .Net will create a DataSet from it. This means that a DataSet can work without any underlying datasource – instead using XML as the data store. You can load an XML document into a DataSet, modify the data and then write it back to disk for persistence. This is perfect for configuration information or other local data that does not rely on complex rules or has to deal with multi-user concurrency issues. It also means that you can use a DataSet as a mechanism to navigate XML instead of an XML reader or DOM parser. Take note DataSets are about more than just mere data!

After years of covert development, Microsoft says it will release a computer that uses the tabletop as its high-resolution display, recognizes objects placed on the surface and skips the traditional keyboard and mouse in favor of fingers on the screen. What it is : A computer in the form of a table, using the hard acrylic tabletop as a high-resolution screen. First product from Microsoft's previously secret Surface Computing team, which has 120 employees. How it works : The surface itself isn't touch-sensitive, but a series of cameras inside the table can see when someone places or drags a finger, hand or any other object on or across the tabletop screen. Internal projector lights screen from beneath. Interface : People can use their hands to touch and move virtual objects on the screen, just as they would with a mouse on a traditional PC. The system also can recognize objects placed on the surface, based on their shape or on special codes affixed to them.Size: 22 inches high,

ASP.NET 2.0 provides built-in membership management capabilities that allow applications to log users into and out of a Web site with minimal coding. Simply run the aspnet_regsql.exe tool to add Microsoft's membership database into your chosen database server (otherwise, a SQL Server 2005 Express database will be used), add a few lines of configuration code in web.config to point to your database, drag on a few controls such as the Login and CreateUserWizard controls, and you're ready to go! However, each time a user logs in to your application, a postback operation occurs which, in some situations, may not be desirable. In cases where you'd like to log users into a Web site without performing a complete postback of a page, you can use the ASP.NET AJAX authentication service instead. The authentication service consists of a service that lives on the Web server that accesses membership information from the database, as well as a client-side class named AuthenticationService

Membership and Role Manager Providers - ASP.NET 2.0 now includes built-in support for membership (user name/password credential storage) and role management services out of the box. Because all of these services are provider-driven, they can be easily swapped out and replaced with your own custom implementation. Login Controls - The new login controls provide the building blocks to add authentication and authorization-based UI to your site, such as login forms, create user forms, password retrieval, and custom UI for logged in users or roles. These controls use the built-in membership and role services in ASP.NET 2.0 to interact with the user and role information defined for your site.

Check this site to know .NET 3.0 Architecture

Click this link to see the features

Tip : Do not use the AutoPostBack attribute on the DropDownList control to simply redirect to another page. There are probably cases when this might make sense, but for the most part it is overkill. Using the autopostback for a redirect requires extra roundtrip to the server. First the autopostback returns to the server and processes everything up to the event handling the postback. Next a Response.Redirect is issued which goes back to the client requesting the client use another page. So you end up with two separate requests + processing just to get a user to another page. Using the onchange event of the select element, we can do this all on the client. In the sample below, I am simply redirecting to the current page with an updated querystring element. Your logic will vary, but in the case below, I am avoiding the zero index. 0) { window.location = window.location.pathname + '?t=' + this[this.selectedIndex].value;}" /> Tip : Never use the ASP.Net Label control. Ever i