Sunday, February 20, 2011

Google Chrome 10 beta Released

Google has just released Chrome 10 beta (10.0.648.82 for all you perfectionists) and it brings with it a whole slew of new things to play with.

First off, there’s a significant JavaScript performance boost thanks to the updated V8 engine. According to Google, this version of the V8 engine offers a 66% performance advantage over the current stable release. That alone is pretty impressive.

Download Google Chrome beta 10 here.

Friday, February 18, 2011

Microsoft Code Samples for Developers

This code sample library will help all developers to find useful code in various dot net areas. Microsoft goal is to centralized all codes in one place. This library having below things:

  • Microsoft All-in-One Code Framework: Free, centralized code sample library
    • Code Samples
    • Services
  • Microsoft SDKs: provide documentation, code samples, tools etc..
  • MSDN Code Gallery:  download and share sample applications, code snippets and other resources.

You can download it from here

Wednesday, February 16, 2011

Download: ASP.NET MVC 3

ASP.NET MVC 3 is a framework for developing highly testable and maintainable Web applications by leveraging the Model-View-Controller (MVC) pattern. The framework encourages developers to maintain a clear separation of concerns among the responsibilities of the application – the UI logic using the view, user-input handling using the controller, and the domain logic using the model. ASP.NET MVC applications are easily testable using techniques such as test-driven development (TDD). The installation package includes templates and tools for Visual Studio 2010 to increase productivity when writing ASP.NET MVC applications. For example, the Add View dialog box takes advantage of customizable code generation (T4) templates to generate a view based on a model object. The default project template allows the developer to automatically hook up a unit-test project that is associated with the ASP.NET MVC application. Because the ASP.NET MVC framework is built on ASP.NET 4, developers can take advantage of existing ASP.NET features like authentication and authorization, profile settings, localization, and so on. Go through this help to get started MVC 3.

MVC stands for model-view-controller. MVC is a pattern for developing applications that are well architected and easy to maintain. MVC-based applications contain:

  • Controllers: Classes that handle incoming requests to the application, retrieve model data, and then specify view templates that return a response to the client.
  • Models: Classes that represent the data of the application and that use validation logic to enforce business rules for that data.
  • Views: Template files that your application uses to dynamically generate HTML responses.

Download MVC 3

Thursday, February 10, 2011

How do I know which version of SQL Server I'm running?

When working with SQL Servers or other features that are version-specific, you often need to know what version of SQL Server is running on the target server.

For SQL 7.0 and earlier, You can query

SELECT @@VERSION

And the following query will work on SQL Server 2000 and up:

SELECT 'SQL Server ' 
+ CAST(SERVERPROPERTY('productversion') AS VARCHAR) + ' - ' 
+ CAST(SERVERPROPERTY('productlevel') AS VARCHAR) + ' (' 
+ CAST(SERVERPROPERTY('edition') AS VARCHAR) + ')'
 

Monday, February 07, 2011

Different types of status in Bug report

Here is the description of all the status with its brief description

1. Bug: When QA files new bug.

2. Deferred: If the bug is not related to current build or cannot be fixed in this release or bug is not important to fix immediately then the project manager can set the bug status as deferred.

3. Assigned: ‘Assigned to’ field is set by project lead or manager and assigns bug to developer.

4. In Process: This is the state of issue when Developer starts working on the assigned issue.

5. Resolved/Fixed: When developer makes necessary code changes and verifies the changes then he/she can make bug status as ‘Fixed’ and the bug is passed to testing team.

6. Could not reproduce: If developer is not able to reproduce the bug by the steps given in bug report by QA then developer can mark the bug as ‘CNR’. QA needs action to check if bug is reproduced and can assign to developer with detailed reproducing steps.

7. Need more information: If developer is not clear about the bug reproduce steps provided by QA to reproduce the bug, then he/she can mark it as “Need more information’. In this case QA needs to add detailed reproducing steps and assign bug back to dev for fix.

8. Reopen: If QA is not satisfy with the fix and if bug is still reproducible even after fix then QA can mark it as ‘Reopen’ so that developer can take appropriate action.

9. Closed: If bug is verified by the QA team and if the fix is ok and problem is solved then QA can mark bug as ‘Closed’.

10. Rejected/Invalid: Sometimes developer or team lead can mark the bug as Rejected or invalid if the system is working according to specifications and bug is just due to some misinterpretation.

11. Not a Bug: If the reported issue is not a bug or not for the current build then project lead or manager will set the status to 'NAB'