No template information found. See the application log in Event Viewer for more details.

No template information found.
See the application log in Event Viewer for more details.

I got this problem I found solution of this problem is very easy fix is
use visual studio command prompt type devenv/installvstemplates

hope this help you out!

How to Enable AdHoc Quaries

I want to save my records in excel file for this I have to use openrowset in my query . It throws my error of AdHoc Quaries is disable on you server contact your administrator.
If you are using sqlserver 2005 or 2008 then follow this pictorial represenstation this is one way

and easy way :)

click on surface area configuraiton for feature and then you see screen below.

enable this adhoc query option and enjoy.

there is another way which is manual way for this follow this link

http://www.kodyaz.com/articles/enable-Ad-Hoc-Distributed-Queries.aspx

Becoming a Great Developer

Becoming a Great Developer

You are very good programmer, problem solver and algorithms writer.

If your code is not good enough to deliver your knowledge,however,your team and your company will suffer in logn run.It is crucial that as a great developer you are not passionate about code.

We talk consistantly about design patterns,refacotring and code readablity, but when it gets right down to it, we often ignore infromation due to constraints of time.

The fact remains that we must consider some important points begin to always right code in this manner.

Here are some techniques that I have learned,which we can include in our daily programming practice.

1. Use common template in whole code ,it shows your code consisitancy in whole proj/prod.

2. Repitative code should be in single method.

3. Try to use factory method where ever object creation is concern.

4. Variable name should be self descriptive.

if (HasInstantiationAwareBeanPostProcessors)

{

foreach (IObjectPostProcessor processor in ObjectPostProcessors)

{

IInstantiationAwareObjectPostProcessor inProc = processor as IInstantiationAwareObjectPostProcessor;

if (inProc != null)

{

if (!inProc.PostProcessAfterInstantiationwrapper.WrappedInstance,name))

{

continueWithPropertyPopulation = false;

break;

}

} }

5. Use singleton on your Service and Dao layer, it creates a hell on each call of new object creation.

6. These objects are useless to create at every call.

7. Use at least one line summary of method in your comments area.

8. KIS principle.(Keep it Simple)Your method should contain single respoinsiblity don’t make your method monolithic.

///

Checks if a string has length.

/// if the string has length and is not

///

///

///


/// StringUtils.HasLength(null) = false

/// StringUtils.HasLength("") = false

/// StringUtils.HasLength(" ") = true

/// StringUtils.HasLength("Hello") = true

///

public static bool HasLength(string target)

{

return (target != null && target.Length > 0);

}

9. Your calss should be single responsible of your logic means userservice should have method of only related with user related.

10. Declare interface for your each layer’s object.Mean to say userservice should have IUserservice same with other service layer object either it is infrastructure,Dao,persistnance.

Writing software is not just one time activity as codes have to dealt with 90% of the time.It's a life time activity and I think that code maintanance should be a part of everyday.Code maintanance is understanding that the easier code is to write the easier it is to maintain.

packing my stuff

Just writing task in my vacation tour of hometown.My School, meeting with University's Juniors, shopping,meeting with friends.....etc

MicroSoft SharePoint Labs

http://sharepoint.microsoft.com/Pages/Default.aspx

very good site for those who don't have envoirnment for sharepoint practice
can do their practice with labs.

Application Architecture

Last days I was busy in discussion architecture of an Application.
Without going in any further detail we divided our application architecture (Arch) into traditional three layers. But throughout the whole design of application Arch that implementation should be separate from the communication between layers.
I explain what I did with it.

User Interface
First of all discuss UI actually it depends on the technology you are using like I was on .net then .net provides you controller class in shape of aspx.cs ,but it would be different in case of Java.
In Java usually most of architects use Front Controller Pattern but in case of .net we usually prefer Page Controller Pattern I will not delve into the detail of patterns because this is not our target.
I really love this pattern(FCP) to use in my application .In Asp.net we have facilitated by web Framework of .net it handles itself all the requests,but if needed more control on application or new request handler so go to FCP.

Page control pattern should be use in every application it reduce our calling from every instance, it take care of all prevention that we have to do on every page.

Like session, security, some cached object, most visited objects and all decision we have to take on most of the pages we promoted it into base controller. Base controller will handle it, now it’s time to move on Facade thin layer.

Facade
As our focus on we want to separate implementation from its abstraction. Actually this is very important for us to know this rule. Everyone can implement own its own way. I do it on my own way , Everyone do it according to his business needs and its convenience. But rule should be same.We use FAÇADE because of facade can call BAL or might be outside of our domain like web service etc.
So, UI layer shouldn’t be affected and free from this knowledge that where it gets data and what is the complexity or calling cost.

BAL (Business Access Layer)

Business Manager contains all the business knowledge of Application, Transactions ensures, maintain abstraction between UI and DAL. Architecture should have BaseManager which responsibility is control transaction, most frequently called methods actually this is contract between Façade and BAL so, FACADE doesn’t know about the implementation of Managers. There is a question manager can’t have same methods then we have to make interface for each manager just for separating it from implementation because you can have two managers for same purpose for any need/requirment, it provides you a flexibility to change your implementation according to your need and your application other part will work smothly.
In every BAL class should be singleton just for ensuring a single object and avoiding unnecessary object on every call.

Another good Idea about it is I read something about spring framework this is excellent it takes all the responsibility of making object we just pass the object name and it creates it for us. Great thing of this framework is you can also define dependency and it will create object for you with all of its dependencies.
Great work!

Data Access Layer

Data Access Layer also the same rule we define interface for every DAO. Every DAO object should be singleton because otherwise might be there is a huge amount of unnecessary object creation.
For avoiding this extra object creation implement singleton in every DAO

This is BaseDao responsibility to control the internal transaction and all search criteria, Creation, Deletion and Updating method to avoid redundancy of same implementation. It can be possible to have object caching because it will avoid your round trip of server each time and improve the performance of your application. Most important thing to use this framework is work with objects rather xmlDataset. For Object Relational Mapping you can use

• Nhibernate
• ORM Tool
• Opf3
• Entity Framework

For avoid creation of Dao object every time in BAL you can use As I discussed earlier some Framework following Inversion of control prevent us to couple other layer and take responsiblity of object creation. I am discussing here Spring Framework we have also other Framework available you can use according to your requirement and ease of use.
So, this framework responsibility to create, session and keep all its dependencies and return on calling correctly.

cutomize workflow

I have updated my previous workflow blog with detail example see
http://nazishalirizvi.blogspot.com/2008/09/customize-workflow.html