Vikram Lakhotia Blog on Asp.Net, Dot Net, SQL, VIsual Studio, C# etc

Hi

Yesterday I came across a very common but interesting requirement from a friend. Actually the requirement is very common for developer dealing with the database. Many a times a we have some SQL, TSQL code which we use during development but that should not run on the server.

Normally developers have a process of checking from the process prospective so that the code does not go on the server. But mistakes are inevitable. So we should also have a solution for the same from programmatic aspect. This is very important because some code (Like delete, or update statement) can cause big problem in the live site if they run by mistake also.

We should have a process to stop such error, but we can also take small care in the code itself to prevent any major problem. Some of the way are discussed below.

If we are sure of the production server name then we can have a small IF statement based on the

Hi

A few days back when I wrote the blog on design pattern a small but interesting question came to my mind. How and why did the design pattern started. So I started hunting in the google for my curiosity and found some interesting stuff. So I thought I would share them with you.

A repeatable solution for commonly occurring problem in the software programming is called design pattern. Design patterns are not finished designs for the problems, but are template and description on how the solve the problem, which might occur in different situations.  Design patterns commonly show relations and interaction of different class or objects or types. They do not specify the final class or types that will be used, but give an abstract view of the solution.

As design patterns provide tested and proven development paradigms, they can speed up the process of development. For a design pattern to be effective, it

Hi,

A few days back on of my senior talked about different pattern and how useful they can be in the process of development. We were talking about the observer pattern. So I thought I will write a bit about the observer design pattern.

Based on the principal of implicit invocation, Observer design pattern (also known as publish Subscribe) is used in programming to observer the state of and object in a program. In many programming language the issue of this pattern are handled in native event handling syntax.

The bottom line of the pattern is that one or more listeners or observer (objects) register themselves to observer an event, which is raised by the subject. The object that raises the event maintains a collection of all the observer or listeners. We can also say that the pattern defines a one to many dependencies between objects so that one the state of a object is changed all the dependent are notified and

Hi,

A few days back a friend of mine asked me a simple but tricky question in SQL. The question was how would you check that the number of rows deleted through a delete query and the logic of the delete query is correct.

I know the first answer that comes to the mind the @@rowcount variable. But that variable is good enough for the row count only. How do you verify the login of the delete statement?

The answer is first we create a select query with the same clause that we want to delete the records. Now when we are satisfied with the login in the select statement, we use the delete statement with the same clauses. So here we have checked the logic of the delete with a select clause. After the delete we find the number of the rows deleted with the help of the @@rowcount variable. But this is not the end of the process. We should again use the Select statement with the same clause (as the delete statement). And this

Hi

A few days ago Microsoft Released the Asp.Net Futures. This is a list of futures that might be delivered in the future. I have still looked at only one of the Category and the list already looks promising and exiting to me. The functionality in the Futures release includes early experimental versions of features currently being considered for future versions of ASP.NET and the .NET Framework.

1. DynamicAutoData: Displays the current table as a GridView control, along with user interface elements to select which rows of the table are displayed.
2. DynamicList: Displays the current table as a GridView control.
3. DynamicDetails control: Displays the columns of a row in the current table.
4. DynamicFilter: Enables users to select which rows of the

Hi

Today I was playing around with some window form and came up with a simple and interesting requirement. I wanted to take a print screen of the monitor from inside the application. What I wanted to do was allow the user to save the screen as and when they wanted it from inside the application.

So first thing I had to do for this was to find out the resolution of the screen that the user was working with. Because the screenshot need to be save of the same size as the screen resolution. This can be done by using the System.Windows.Forms.SystemInformation class. This class provides a static method PrimaryMonitorSize which gives us the monitor size. This property is of type Size. So we have width and height of the screen using the following code.

int width, height;

width = System.Windows.Forms.SystemInformation.PrimaryMonitorSize.Width;

height =

Hi

It seems to be the season of the beta download and beta testing again. Dot net developers have got tons of things to play with. Four most important products in their different level of Beta. Wow! Here is the list and the links to download

First we have IIS 7 in Beta 3 for download. Yes it also support the go live license. This means that you can use it in the production environment also. And is its stable? Well Microsoft.com is already deployed on this.

Some of the new features of IIS 7 are

• Web Farm Shared Configuration
• Delegated Remote Administration
• Automatic Application Pool Isolation
• Continued...