Stored Procedure Driven Data Grid

http://www.codeproject.com/KB/aspnet/sp_driven_datagrid.aspx
http://www.west-wind.com/weblog/default.aspx


this.gvMain.RowDataBound += new GridViewRowEventHandler(gvMain_RowDataBound);

APP_CODE ???????

Security with the Bin Folder

Putting compiled assemblies into the Bin folder can represent a security risk. If you wrote the code yourself and compiled it, then you know what the code does. However, you should treat compiled code in the Bin folder as you would treat any executable code. Be wary of compiled code until you have tested it and are confident that you understand what it does.

Note these security aspects of putting compiled code into the Bin folder:

*

Assemblies in Bin folder are scoped to the current application. Therefore, they cannot access resources or invoke code outside the current Web application.
*

At run time, the access levels of an assembly are established by the trust level specified on the local computer. For more information, see ASP.NET Trust Levels and Policy Files.
*

When you run a project in Visual Studio, code in the Bin folder runs in a different context than at run time. The Visual Studio Development Server runs under your logged-in identity. If you logged in as an administrator, the code will run with administrator permissions. When you deploy your site, however, the code typically does not run with administrator permissions. Therefore you should test your project with a IIS server before deploying it, to make sure that security errors do not occur in production.

Is User controls (ascx files) are allowed in the App_Code folder?

User controls (ascx files) are not allowed in the App_Code folder. This includes single-file user controls and user controls that use the code-behind model. Putting a user control in the App_Code directory causes the user control's code to be compiled out of its required sequence and therefore is not allowed. (In any event, user controls do not need to be in the App_Code folder; they are already available to pages anywhere in the application.)

Some Imp Link

1.http://www.codedigest.com/Articles/jQuery/224_Building_Cascading_DropDownList_in_ASPNet_Using_jQuery_and_JSON.aspx
2.http://www.developertutorials.com/tutorials/javascript/client-side-data-binding-using-jquery-796/
3 http://www.java2s.com/Tutorial/Oracle/0440__PL-SQL-Statements/CASEstatements.htm
4.http://www.java2s.com/Code/JavaScript/Javascript-Properties/CatalogJavascript-Properties.htm
5.http://www.delphifaq.com/faq/javascript/f1038.shtml
6.http://www.velocityreviews.com/forums/t84123-button-click-executes-postback-page-not-valid.html
5.http://social.msdn.microsoft.com/Forums/en-US/winformsdesigner/thread/c1f66568-1ece-483c-969c-6dc66ea77c49
6 http://www.aspsnippets.com/Articles/Validating-ASP.Net-ListBox-Control-client-side-using-Custom-Validator.aspx
7.http://www.codeproject.com/KB/cs/AgileWare_Convert_Int32.aspx
8.http://www.java2s.com/Tutorial/CSharp/0140__Class/VirtualMethodsandOverriding.htm
9.http://blog.sqlauthority.com/2008/04/02/sql-server-find-nth-highest-salary-of-employee-query-to-retrieve-the-nth-maximum-value/
10.http://www.beansoftware.com/ASP.NET-Tutorials/Using-Crystal-Reports.aspx
11.http://www.programmersheaven.com/user/spickersgill/blog/956-Delegates-Explained-in-Plain-English/
12

How Web services works internally?

But now imagine that your boss come to your office and requires new 3-tier architecture so that your Views and Controllers are on a frontend web server, your Model is on an application server and your database is on a database server. How would you achieve such architecture? How would you call model methods when it is running on different machine? There is a lot of technologies which allow you to call object from different process and even different machine. In the world of .NET we used to use .NET remoting or ASP.NET Web Services (ASMX) for calling remote objects. Now new applications are usually implemented by Windows Communication Foundation (WCF). ASMX and WCF are API for creating Web services.

Web services are development approach to call remote objects, moreover there is a lot of standardized protocols which allow interoperability. Interoperability means that your model can be written in Java and exposed as Java Web service but you will be able to consume web service in your VB.NET code. Now you probably asks what does consuming mean and how does it really work?

Consuming web service = using web service. Common approach to use a web service is based on a proxy pattern. The web service communication differs two players - a server (machine / process) exposing the service and a client (machine / process) consuming the service. The client contains proxy. From the developer point of view, public interface (available methods) of the proxy looks exactly same like public interface on the remote object. So the developer calls methods on the proxy and it internally communicates with the remote object - the service. In the most common communication pattern the proxy wraps method call into request and sends it over transport protocol to the service. Service extracts the content of the request and use it to fill parameters of exposed method, executes method and returns result as a response to the proxy. Proxy takes response, and returns response content as method call result. So using proxy is absolutly transparent and it looks like the remote object lives in the same process (except much longer execution times of the remote call). This is how web services work internally.

Creation of web service and its proxy from scratch is quite hard task because it requires deep knowledge of many protocols and other stuff so we are back in provided API - ASMX and WCF. These API allows you to define web service in extreamly simple way and proxy is generated automaticaly based on service description. So if you are developer that has to consume service in his application you will just use Add web reference or Add service reference in Visual Studio and it creates proxy together with all required classes (request parameter types and response types) for you.

I definitely recommend you to learn how to create service and how to consume it. Based on your experience with ASP.NET I would quickly go through ASMX web services and later on I will go to WCF wich is much more complex. I don't know what to recommend for learning ASP.NET Web Services. You should check MSDN and look for web casts if there is any available. For learning WCF I definitely recommend: http://www.amazon.com/Learning-Hands-Michele-Leroux-Bustamante/dp/0596101627/ref=sr_1_1?ie=UTF8&s=books&qid=1277756654&sr=8-1 and set of 15 web casts which corresponds to the content of this book: http://www.dasblonde.net/2007/06/24/WCFWebcastSeries.aspx

Best regards,
Premjit