YourDotNetSolution

IE 6 adds anchor tags to request value

2010-01-25T14:38:00.000-08:00

If you have a url parameters specified in your url like so:

somepage.aspx?recordId=1

And then add a anchor to it like so:

somepage.aspx?recordId=1#middleofpage

IE 6 will read recordId as 1#middleofpage instead of just 1. The way to fix this is to either add a & symbol in from of the pound like so:

somepage.aspx?recordid=1&#middleofpage

Or, do some regex match to remove the values from the # symbol on so that you end up with only the value you want.

If your lucky, this is your only problem. However, I also have had the problem in IE 6 and 7 where a response.redirect will remove the anchor part completely. So a url like so:

sompage.aspx?recordid=1#middleofpage

Will be somepage.aspx?recordid=1 when it redirects in IE 6/7, even though the code I used was response.redirect("somepage.aspx?recordid=1#middleofpage"). Of course this works fine in all other browsers including IE 8. This happens randomly and I have not figured out a solution. My work around was to send the request to another page and do the redirect from there because adding the # symbol to my url worked fine there, because it's a different page of course:)

SQL Loop

2008-12-26T11:55:00.000-08:00

declare @query varchar(100),@dbname sysnamedeclare @dblist table (dbname sysname)insert into @dblist(dbname) select name from sys.databaseswhere name not in ('master', 'model', 'msdb', 'tempdb')while (select count(*) from @dblist) > 0beginselect top 1 @dbname = dbname from @dblistselect @query = 'dbcc checkdb(' + quotename(@dbname) + ')'exec(@query)delete from @dblist where dbname = @dbnameend
go

Search all fields in a table

2008-12-02T05:24:00.000-08:00

CREATE PROCEDURE [dbo].[FindValue] @TableName NVARCHAR(128), /* Must be a valid table or view name, must not be quoted or contain a schema*/ @Value NVARCHAR(4000), /*May contain wildcards*/ @schema NVARCHAR(128) = 'dbo' /*May be left out*/ AS /* Sample Execution Exec FindValue @TableName = 'spt_monitor', @Value = '8', @schema = 'dbo' */ /* If given a string it will finds all rows where any char, varchar, or their Unicode equivalent which contain that string in the selected table or view. Note that this only works on objects which have entries in information_schema.columns, which excludes certain system objects. If given a numeric value it will check those text types for a match as well as numeric types. If given a possible date, it will also check date type. The string that is being searched for may contain wildcard characters such as %. This will NOT search text, ntext, xml, or user defined fields. This may return a row more than once if the search string is found in more than one column in that row. */ /**************************** Declare Variables ***********************/ DECLARE @columns TABLE (ColumnName NVARCHAR(128)) DECLARE @sql NVARCHAR(MAX) /************************** Populate Table Variable *****************/ /*Takes the names of string type columns for the selected table */ INSERT INTO @columns (ColumnName) SELECT Column_name FROM INFORMATION_SCHEMA.COLUMNS WHERE Table_schema = @schema AND Table_name = @TableName AND data_type IN ('char', 'nchar', 'varchar', 'nvarchar') /* If it is numeric, also check the numeric fields */ IF ISNUMERIC(@value) = 1 INSERT INTO @columns (ColumnName) SELECT Column_name FROM INFORMATION_SCHEMA.COLUMNS WHERE Table_schema = @schema AND Table_name = @TableName AND data_type IN ('int', 'numeric', 'bigint', 'money', 'smallint', 'smallmoney', 'tinyint', 'float', 'decimal', 'real') IF ISDATE(@value) = 1 INSERT INTO @columns (ColumnName) SELECT Column_name FROM INFORMATION_SCHEMA.COLUMNS WHERE Table_schema = @schema AND Table_name = @TableName AND data_type IN ('datetime', 'smalldatetime') /********************* Prepare dynamic SQL Statement to Execute **********/ SELECT @sql = CASE WHEN @sql IS NULL THEN 'Select ''' + ColumnName + ''' as ContainingColumn, * From ' + QUOTENAME(@Schema) + '.' + QUOTENAME(@TableName) + ' where ' + ColumnName + ' like ''' + @Value + ''' ' WHEN @sql IS NOT NULL THEN @sql + 'UNION ALL Select ''' + ColumnName + ''' as ContainingColumn, * From ' + QUOTENAME(@Schema) + '.' + QUOTENAME(@TableName) + ' where ' + ColumnName + ' like ''' + @Value + ''' ' END FROM @columns /******************* Execute Statement and display results ***********/ --print @sql /* This may be uncommented for testing purposes */ EXEC (@sql)

Report server report viewer 404 - File or directory not found

2008-09-17T15:00:00.000-07:00

With SQL Server 2008 and IIS7, you may run into this error like I did. The fix for me was to do the following:

Under IIS area, double-click on Handler Mappings icon. At the Action pane on your right, click on Add Managed Handler. At the Add Managed Handler dialog, enter the following: Request path: Reserved.ReportViewerWebControl.axd Type: Microsoft.Reporting.WebForms.HttpHandler Name: Reserved-ReportViewerWebControl-axd Click OK.

You may also need to add this to your web.config, although I think this is only for older versions of IIS:

<add name="Reserved-ReportViewerWebControl-axd"
path="Reserved.ReportViewerWebControl.axd" verb="*"
type="Microsoft.Reporting.WebForms.HttpHandler" resourceType="Unspecified"/> in
the <handlers> section.

How to pass windows authentication when serving a report with Report Viewer from Reporting Services

2008-07-18T06:16:00.000-07:00

First create the following class:

[Serializable]
public sealed class ReportServerNetworkCredentials : IReportServerCredentials
{
#region IReportServerCredentials Members

///

/// Provides forms authentication to be used to connect to the report server.
///

/// A Report Server authentication cookie.
/// The name of the user.
/// The password of the user.
/// The authority to use when authenticating the user, such as a Microsoft Windows domain.
///
public bool GetFormsCredentials(out System.Net.Cookie authCookie, out string userName,
out string password, out string authority)
{
authCookie = null;
userName = null;
password = null;
authority = null;

return false;
}

///

/// Specifies the user to impersonate when connecting to a report server.
///

///
/// A WindowsIdentity object representing the user to impersonate.
public WindowsIdentity ImpersonationUser
{
get
{
return null;
}
}

///

/// Returns network credentials to be used for authentication with the report server.
///

///
/// A NetworkCredentials object.
public System.Net.ICredentials NetworkCredentials
{
get
{
string userName = "username";
string domainName = "domain or computer";
string password = "password";

return new System.Net.NetworkCredential(userName, password, domainName);
}
}

#endregion
}

Then in the code behind of the page with the report viewer, do the following on page load:

protected void Page_Load(object sender, EventArgs e)
{
myReportViewer.ServerReport.ReportServerCredentials = new ReportServerNetworkCredentials();

}

Some notes about this. When working locally, I could get the report view to display without prompting me for a password (the authentication worked), but the data wouldn'd display. I'm not sure if this is a Vista issue or what, but when I publised it to the server, everything worked fine. Well, everything worked fine after I download the Microsoft Report Viewer Redistributable 2008 from mirosoft and installed it. You can download it here: http://www.microsoft.com/downloads/details.aspx?FamilyID=CC96C246-61E5-4D9E-BB5F-416D75A1B9EF&displaylang=en. This is necessary because the .net Report View control is part of VS 2008, so not included on the server.

How to enable Asp.NET security tables for a database.

2008-07-18T06:12:00.000-07:00

You can run Aspnet_regsql.exe without any command-line arguments to run a wizard that will walk you through specifying connection information for your SQL Server database and installing or removing the database elements for supported features. You can also run Aspnet_regsql.exe as a command-line tool to specify database elements for individual features to add or remove. To specify SQL cache dependency settings or set up session state, you must use the command-line tool.

To run the wizard, run Aspnet_regsql.exe without any command-line arguments, as shown in the following example.

C:\%windir%\Microsoft.NET\Framework\[versionNumber]\aspnet_regsql.exe

How to query a list in sharepoint

2008-06-12T12:19:00.000-07:00

SELECT dbo.UserData.tp_ID,
dbo.UserData.tp_ListId,
dbo.UserData.tp_Author,
dbo.UserData.nvarchar1,
dbo.UserData.nvarchar2,
dbo.UserData.nvarchar3,
dbo.UserData.nvarchar4,
dbo.UserData.nvarchar5,
dbo.UserData.nvarchar6,
dbo.UserData.nvarchar7,
dbo.UserData.nvarchar8,
dbo.UserData.nvarchar9 ,
dbo.UserData.nvarchar10,
dbo.UserData.nvarchar11,
dbo.UserData.nvarchar12,
dbo.UserData.* –dont forget to modify this to snatch only the columns you need
FROM dbo.Lists
INNER JOIN
dbo.UserData ON dbo.Lists.tp_ID = dbo.UserData.tp_ListId
WHERE
(dbo.UserData.tp_ListId = ‘{B44327F5-95E9-4504-A3BF-1E6751C452D6}’)

–optional WHERE clause, this pulls data for ONE list

How to disable or enable all foreign key constraints in Oracle

2008-05-21T13:04:00.000-07:00

--this will disable all foreign key constraints
begin
for i in (select constraint_name, table_name from user_constraints where constraint_type ='R'
and status = 'ENABLED') LOOP
execute immediate 'alter table '||i.table_name||' disable constraint '||i.constraint_name||'';
end loop;
end;

--this will enable them again
begin
for i in (select constraint_name, table_name from user_constraints where constraint_type ='R'
and status = 'DISABLED') LOOP
execute immediate 'alter table '||i.table_name||' enable constraint '||i.constraint_name||'';
end loop;
end;

How to Export and Import MySQL database

2008-04-29T13:33:00.000-07:00

First, to export the database use the following command after navigating in command prompt to your mysql bin directory:

mysqldump -u username -ppassword database_name > FILE.sql

Then use this command to import the data:

mysql -u username -ppassword database_name < FILE.sql

If you don't like command prompt, you can use Heidi SQL that allows you to do it via an easy to use interface.

How to retrieve a list of column names for a specific table in MS SQL Server.

2008-04-22T07:04:00.000-07:00

One way:

sp_columns 'table name'

Another way:

SELECT * FROM INFORMATION_SCHEMA.COLUMNS where TABLE_NAME = 'MyTable'

Asp.NET Web Development Process

2008-03-24T06:57:00.000-07:00

Asp.NET Web Development Process

This document helps define a development process for the entire project life cycle.

Requirements Gathering

A “requirement” is simply a statement of what the business needs to accomplish. At a high level, the business case or justification for the project should be defined as a requirement(s). Then by analysis of this high level requirement(s), additional requirements will flow at an increasing level of detail.

The requirements gathering process results in a living document that will continue to change and grow throughout the project life cycle. Requirements will continue to be refined in the analysis phase.

Here are some guidelines for requirements gathering:
1. The requirement must be from the business perspective. Every requirement should be clear from the client’s perspective and be relevant to their business needs. This is the time to focus on the business side of things. Keep the technical “how” out of the discussion until all the business requirements are clearly defined. This will keep the project focused on what the business needs.
2. Come prepared to the first requirements gathering meeting with the start of a requirements document. You should have enough in the requirements document, even if it’s 100% assumptions, to help facilitate the gathering process by engaging the client. Even making the wrong assumptions about things are helpful as it will help facilitate feedback and get the client thinking about their needs.
3. While technical implementation details do not belong in this document, your perspective on the requirements will help you ask the “right” questions. You should use your experience to facilitate the client thinking about the “right” things, and to help uncover business requirements the client would not normally think about. For example; validation and data rules, data security, web site security, privacy, integration with other systems, reporting, exporting, etc are all business requirements.
4. Follow leads based on the clients’ responses and continue to push until you get concrete answers. The wording should be definite with terms like "must", "will", or "shall". Avoid terms that leave options open like "could" or "may". If concrete answers cannot be determined for a given requirement, flag them and then use the Analysis phase to dig deeper until you get to the bottom of it.
5. Get customer approvals of all requirements. You will want to fill in blanks on behalf of the business, but if you do, make sure you always get customer approval for your assumptions.
6. The requirement should be testable. Ask yourself how you would generally go about testing a requirement. Since the system isn't built, you have to make assumptions about user interface and the like. At a very high level, get the test plan outlined with a short statement on how each requirement should be tested. If you find it difficult to come up with a test or a description of how a test should work, evaluate the requirement to see if it should be better written, is too costly to implement, or isn't practical.
7. Estimating – Use the following formulas for calculating ranges for estimating based on your requirements.
  1. Order of Magnitude (Done during Initiating) - 25% to +75%
  2. Budget Estimate (Done during Planning) -10% to +25%
  3. Definitive Estimate (Done during Planning) - 5% to +10%
Analysis

Analysis is the process of refining requirements and defining the processes for the solution. Analysis is still business centric (meaning it’s from the business perspective and makes sense to the client), but the objective is more technical. At the end of the Analysis Phase, you should have enough details about each requirement to “Design” the solution.
1. Analysis normally takes the form of Use Cases, but can also include:
  1. Demo’s
  2. Wire-frames
  3. Prototypes
2. A Use Case is a narrative form of a process that is needed to meet each requirement. See Appendix A for a template.
  1. Identify actors. An actor is a user of the system or other system that interacts with this one.
  2. Build Use Cases for each concrete requirement.
  3. Associate Use Cases with an Actor and make sure the Use Case is from the Actor’s perspective.
  4. Define how data will be collected and used.
    1. Will they need to report on this data?
    2. Will 3^rd party systems need to use it?
    3. Is there a need to export this data? To what formats?
    4. What validation rules should be required?
  5. Define where data will come from that is required by the Use Case.
    1. Will someone be entering the data?
    2. Is the data static, or something that needs to change regularly?
    3. Is the data coming from a 3^rd party system?
    4. Is the data dependent on a previous process being completed in this solution?
    5. Use Cases should be complete and approved by the client before entering the “Design” phase.
Design

Design is the process of taking solidified Use Cases (and related Requirements), and translating them into a Solution Design. This Solution Design should clearly communicate to a developer how the solution should be written. A Solution Design should contain:
1. Static Structure – This UML diagram will define all objects in the solution. In lieu of a diagram, the Business Layer can be used to build these object directly, as long as they are documented as to which use case and requirements they are designed to meet. Use Case nouns are potential objects (business and data access objects), and verbs potential operations.
2. Sequence Diagrams – These UML diagrams should map to a specific Use Case and show how the objects identified in the Static Structure for this Use Case will be used to accomplish the intended outcome.
3. Prototypes and wire-frames – This should define how the UI should look and function.
Construction

Construction is the process of taking the culmination of knowledge from the Analysis and Design phases to produce code for the solution. While construction doesn’t require that all of the Analysis and Design be completed for the entire solution before any code is written, it does require that:
1. All major components of the solution are defined at a high level.
2. Dependencies and communication requirements between these components are identified.
3. Requirements and Design artifacts are completed and approved (if necessary) for the component being developed.

Construction standards are strictly followed during the construction phase of the project. While these standards are not the only way to do things, it is necessary to adopt one way for consistency and interoperability during the construction and integration of a solution. Here is a list of these standards:

Camel Casing

Camel casing occurs when all words of an identifier are capitalized, except for the first word. The identifiers firstName, productId, and email are all examples of using camel casing.
1. Use camel casing for private type fields, parameters, and local variables.
Pascal Casing

Pascal casing occurs when the first letter of every word in an identifier is capitalized. ProductName, CompanyName, and Email are examples of PascalCasing.
1. Use Pascal casing everywhere except for when you use camel casing. For example, property names, operations, and tables.
Field, Local Variable, and Parameter Naming

Fields are variables declared at the type level. Local variables are declared within methods, property accessors, and indexer accessors. Parameters are part of the declaration of methods, indexers, and delegates and enable code to pass arguments.
1. Prefix field names with "_". The identifiers _firstName, _companyId, and _email are proper field names.
2. Don't prefix Local variables and parameters. The identifiers firstName, companyId, and primaryEmailAddress are valid local variables.
UI Elements

UI Elements should be explicitly named if it is referenced anywhere on the page or in the code-behind.
1. UI Elements should be prefixed to show what type of UI element it is: “lbl” for Label, “txt” for TextBox, etc.
2. They should have “friendly” names that are applicable to how that control is being used.
Delegates and Events
1. Event names can use the VS assigned convention, but be sure the parent control has been named appropriately before the event is created.
2. Name Delegates with a “Handler” Suffix.
Software Development Methodology

During the construction phase, a Software Development Methodology is used to improve overall quality of the solution, as well as enhance flexibility and maintenance over the lifecycle of the application. This methodology follows best practices of n-tier software design to separate out UI, Business and Data Access layers into separate manageable pieces of the application.
1. High Cohesion

OO design is highly cohesive when the objects are singular in their purpose and their purpose is well thought out and maintained.

This also means that at a smaller level, your methods should follow the same general rule. Methods should be as simple and concise as possible. It is better to have several smaller methods to carry out a specific operation, then to have one large method that is harder to read and therefore debug.

Loosely Coupled

OO design is loosely coupled when the application, and it’s parts, are independent in their nature. Meaning, the application, one of it’s components, or a single object can be modified without have a ripple effect in the rest of the system, or to other systems

The way this is accomplished is by designing for high cohesions at the system, component, object, and method level, and carefully handling the communication at each one of these levels to reduce the dependency at each.
Interfaces

Interfaces should be used to provide all up-stream access between layers. Interfaces should also be considered when an object is shared among multiple Managers (UI processes) as an additional layer of abstraction.
User Interface Layer

User Interface Layer is the GUI of the application. For ASP.NET applications, this includes the ASPX and ASPX code-behind.
1. Use .NET UI components – In all instances possible, .NET components should be utilized for the GUI.
2. Use Object Data Sources – This provides design view readability into the BLL and DAL process without loosing encapsulation.
3. Use the code-behind – Avoid writing any embedded code with the UI. Instead, utilize the code-behind.
4. Use Master Pages, Skins, and Themes – This will provide encapsulation of design from the actual ASPX pages. Doing this will provide consistency for the look and feel, as well as ease of managing changes to the design in the future.
5. Use Cascading Style Sheets – CSS should be the primary layout means for overall UI control and design. Avoid using tables, inline styles and outdated formatting options (I.E. font tags).
Business Layer

The business layer contains object that encapsulate the domain of business logic for the application.

This domain has two objectives:

1. Abstract the UI from data access and business logic.
2. Provide communication between the UI and BLL/DAL.

To accomplish the domain’s objectives, we’ve adopted the following standard objects:
1. Managers – Manager objects are used in the code-behind of the aspx page as well as in the DAL (see Data-Access Layer below). They provide single-point-access for all BLL (explicit) and DAL (implicit) functions the application needs to accomplish from the UIL.
Data-Access Layer

The data-access layer provides mechanisms for retrieving and populating data into BLL objects.
1. Gateways – Gateways are the primary data-access objects. They work in conjunction with a reference to a “Manager” to create business objects and populate them will data.
2. For BLL access use Interfaces – Because business objects are upstream from the DAL, all interaction with this layer should be handles through interfaces. Additionally, interaction with the BLL should be isolated to using “Managers”.
3. Use parameters when creating your queries by using the SqlCommand object.
4. Populate BLL objects – In general, business objects should be used to populate with data.
  
  Here are some exceptions to this rule:
  1. You are doing a data-centric operation (requires no business logic). For example, binding search results to a data grid.
  2. You want to provide a generic data transport. For example, when using web services datasets can provide a very agnostic data transport mechanism. Datasets can also easily translate to XML.
5. Read – This would involve any “Select” type operation.
  1. Use Views – This will provide a layer of abstraction for the underlying table structure.
  2. Utilize the “Managers” to create needed BLL objects and perform other business related functions.
  3. Create methods specifically for populating BLL objects from data readers.
  4. Only send in what is necessary from the BLL to retrieve the data. This typically means a primary key.
  5. Return populated BLL objects to the “Manager”.
6. Create – This would include any “Insert” type operation.
  1. Send in the BLL object containing the data for the insert operation. Remember, this must be referenced as an interface.
  2. Use transactions when inserting into multiple tables at once.
  3. Return the updated BLL object to the “Manager”.
7. Delete – In general, deletes take two forms:
  
  A Soft delete – This flags a record as deleted, but doesn’t actually delete the record.
  
  A Hard delete – This actually deletes a record from the database.
  1. Both “Hard” and “Soft” deletes should be written into the DAL, typically only utilizing the “Soft” delete from the UIL.
  2. Use transactions when deleting from more then one table.
  3. Only send in what is necessary from the BLL to retrieve the data. This typically means a primary key.
8. Update – This would be any “Update” type operation.
  1. Send in the BLL object containing the data to use for the update operation. Remember, this should be referenced as an interface.
  2. Use transactions when updating more then one table.
  3. Return the updated object to the “Manager”.

Test

Testing is the process of ensuring quality of the solution. The solutions quality is measured by how well it handles defined requirements, and how well it performs in that capacity.

Testing preparation starts at the Analysis phase by analyzing requirements to determine how to test for each. Then, as construction for each requirement takes place, testing is done to ensure that the constructed artifact does in fact meet the requirements it was designed to. Testing is continued throughout deployment to ensure quality at the solution level.

Testing procedures:
1. Unit Testing – This is the process of testing highly specialized parts of the system to make sure they handle their specific requirements correctly before they are integrated into larger components.
2. Component Testing – Component Testing will ensure that as highly specialized artifacts are brought together to build larger components of the overall system, they will continue to perform their specialized requirements and work together to accomplish a larger set of required functionality.
3. Integration Testing – Integration Testing is the process of testing component as they are integrated together to compose a functional piece of the solution. Testing is done to ensure the component meets requirements as defined for the component and that the integrated set of components meets overall business requirements for the solution as a whole.
4. Regression Testing – Regression Testing is the process of testing peripheral functionality (functionality outside of what was explicitly changed or added) to ensure changes did not have negative impact to any part of the system.
5. Usability Testing – Usability Testing will ensures that working parts of the solution have acceptable usability based on business requirements.
6. Acceptance Testing – As a final step of the testing process, clients/end users will have an opportunity to test working parts of the solution to make sure it meets their expectations as was defined during the Requirements and Analysis phases of the project.
Deploy

Deployment is the process of moving tested functional parts of the solution resulting from the Construction phase into a different environment. This environment can be integration with overall solution in a development environment, moving the solution to a test or production environment, or integrating the solution with a 3^rd party system. Before this can happen the following must be true:
1. The artifact has been tested to make sure it meets the requirements as defined by the business.
2. The artifact has been tested to ensure that is performs these operations well; without error and with proper usability.
3. The artifact has been tested to ensure interoperability with the rest of the solution and any dependent systems (Regression Testing).

Appendix A – Use Cases Guidance/Template

The following table describes the elements you should add to your Use Case diagrams:

Section Title	Description
UC Name	ID of Use Case – i.e. 1.2.3. Can use Tag in Visio.
Actor	Person or System performing Use Case tasks. Represented as part of Use Case diagram.
Requirement	ID from requirements documentation. – i.e. 1.2.3. Provides tracability. Can use Tag in Visio.
Pre-condition	Pertinent facts that must be true about the system prior to beginning tasks.
Tasks	Flow of work that actor engages in to accomplish Use Case. Represents the "normal" flow. Alterations of the flow should go in Task Exceptions. For any significant alterations, or any task sequences that differ significantly from the normal flow or are hard to describe in a sequence diagram, create a new Use Case and rename present Use Case to be more specific. If you encounter the same task sequence across two or more Use Cases, break the subset of tasks into their own Use Case and reference the new Use Case with an Extends or Uses association.
Task Exceptions	Paths that alter the normal task flow should be documented as Task Exceptions. If the exception is significant, consider creating a new Use Case and renaming the present Use Case to something more specific.
Post-condition	Pertinent facts that must be true about the system after completion.
Notes	Create a note for anything that doesn't fit in other categories. i.e. assumptions, business rules, and constraints.

Use the following item as a template. Documentation is provided separately, in the table above, so you can easily copy and paste this template:

UC Name:

Actor:

Requirement:

Pre-condition:

Tasks:

Task Exceptions:

Post-condition:

Notes:

2008-03-24T05:18:00.000-07:00

jQuery - The Basics

This is a basic tutorial, designed to help you get started using jQuery. If you don't have a test page setup yet, start by creating a new HTML page with the following contents:

  <html>
  <head>
    <script type="text/javascript" src="path/to/jquery.js"></script>
    <script type="text/javascript">
      // Your code goes here
    </script>
  </head>
  <body>
    <a href="http://jquery.com/">jQuery</a>
  </body>
  </html>

Edit the src attribute in the script tag to point to your copy of jquery.js. For example, if jquery.js is in the same directory as your HTML file, you can use:

 <script type="text/javascript" src="jquery.js"></script>

You can download your own copy of jQuery from the Downloading jQuery page.

[edit]

Launching Code on Document Ready

The first thing that most Javascript programmers end up doing is adding some code to their program, similar to this:

 window.onload = function(){ alert("a") }

Inside of which is the code that you want to run right when the page is loaded. Problematically, however, the Javascript code isn't run until all images are finished downloading (this includes banner ads). The reason for using window.onload in the first place is due to the fact that the HTML 'document' isn't finished loading yet, when you first try to run your code.

To circumvent both problems, jQuery has a simple statement that you can use, known as the ready event:

 $(document).ready(function(){
   // Your code here
 });

This code checks the document and waits until it's ready to be manipulated - which is just what we want. So take the above snippet and stick it into the script area on your test page. The remaining jQuery examples will need to be placed inside this callback function, so they are executed when the document is ready to be worked on.

[edit]

Making Something Happen on Click

The first thing we're going to try is having something happen whenever a link is clicked. In the ready function (from the example above), add the following:

 $("a").click(function(){
   alert("Thanks for visiting!");
 });

Save your HTML file and reload the test page in your browser. Clicking the link on the page should make a browser's alert pop-up, before leaving to go to the main jQuery page.

For click and most other events, you can prevent the default behaviour - here, following the link to jquery.com - by returning false from the event handler:

 $("a").click(function(){
   alert("Thanks for visiting!");
   return false;
 });

[edit]

Adding a Class

Another thing that is a common task is the addition (or removal) of classes from elements, for example:

 $("a").addClass("test");

if you were to add some style information into the header of your script, like this:

 <style type="text/css">a.test { font-weight: bold; }
 </style>

and then added the above addClass call - all your A elements would now be bold. To remove the class, you'd use removeClass

[edit]

Special Effects

In jQuery, a couple handy effects are provided, to really make your web site stand out. To put this to the test, change the click that you added earlier to this:

 $("a").click(function(){
   $(this).hide("slow");
   return false;
 });

Now, if you click any link, it should make itself slowly disappear.

[edit]

Chainability (The Magic of jQuery)

jQuery uses an interesting concept to make its code short and simple. For those familiar with object-oriented programming, this concept should be rather straightforward.

In a nutshell: Every method within jQuery returns the query object itself, allowing you to 'chain' upon it, for example:

 $("a").addClass("test").show().html("foo");

Each of those individual methods (addClass, show, and html) return the jQuery object, allowing you to continue applying methods to the current set of elements.

You can take this even further, by adding or removing elements from the selection, modifying those elements and then reverting to the old selection, for example:

 $("a")
   .filter(".clickme")
     .click(function(){
       alert("You are now leaving the site.");
     })
   .end()
   .filter(".hideme")
     .click(function(){
       $(this).hide();
       return false;
     })
   .end();

Which would work against the following HTML:

 <a href="http://google.com/" class="clickme">I give a message when you leave</a>
 <a href="http://yahoo.com/" class="hideme">Click me to hide!</a>
 <a href="http://microsoft.com/">I'm a normal link</a>

Methods that modify the jQuery selection, and that can be undone with end(), are the following:

add(),
children(),
eq(),
filter(),
find(),
gt(),
lt(),
next(),
not(),
parent(),
parents() and
siblings().

Please check the Traversing API documentation for details of these methods.

[edit]

Callbacks, Functions, and 'this'

A callback is a function that is passed as an argument to another function and is executed after its parent function has completed. The special thing about a callback is that functions that appear after the "parent" can execute before the callback executes.

Another important thing to know is how to properly pass the callback. This is where I have often forgotten the proper syntax.

[edit]

Callback without arguments

For a callback with no arguments you pass it like this:

 $.get('myhtmlpage.html', myCallBack);

Note that the second parameter here is simply the function name (but not as a string and without parentheses). Functions in Javascript are 'First class citizens' and so can be passed around like variable references and executed at a later time.

[edit]

Callback with arguments

"What do you do if you have arguments that you want to pass?", you might ask yourself.

[edit]

Wrong

The Wrong Way (will not work!)

 $.get('myhtmlpage.html', myCallBack(param1, param2));

This will not work because it calls myCallBack(param1, param2) then passes the return value as the second parameter to $.get().

[edit]

Right

The Right Way ( note the use of function(){ preceding myCallBack() )

 $.get('myhtmlpage.html', function(){
   myCallBack(param1, param2);
 });

So, by passing in an anonymous function (the part with...

 function(){ 
   myCallBack(param1, param2);
 }

...which itself calls your function with arguments), you're done.

This method works because it passes the anonymous function as the second parameter to $.get() without executing it first.

[edit]

Reader Helper Class in C#

2007-11-21T05:29:00.001-08:00

This class will help with reading data from any DataReader. It has helper methods to parse out almost any datatype from the database into a C# data type.

using System;

using System.Data.Common;

using System.Collections.Generic;

using System.Text;

using System.Xml;

using System.Data.SqlClient;

public class ReaderHelper

{

/// <summary>

///

/// </summary>

/// <param name="rdr"></param>

/// <param name="column"></param>

/// <param name="defaultGuid"></param>

/// <returns></returns>

public static Guid GetGuid(DbDataReader rdr, string column, Guid defaultGuid)

{

int ordinal = rdr.GetOrdinal(column);

if (rdr.IsDBNull(ordinal))

{

return defaultGuid;

}

else

{

return rdr.GetGuid(ordinal);

}

}

/// <summary>

///

/// </summary>

/// <param name="rdr"></param>

/// <param name="column"></param>

/// <param name="defaultGuid"></param>

/// <returns></returns>

public static Guid GetGuid(DbDataReader rdr, string column)

{

int ordinal = rdr.GetOrdinal(column);

return rdr.GetGuid(ordinal);

}

/// <summary>

///

/// </summary>

/// <param name="rdr"></param>

/// <param name="column"></param>

/// <returns></returns>

public static decimal GetDecimal(DbDataReader rdr, string column)

{

return GetDecimal(rdr, column, 0);

}

/// <summary>

///

/// </summary>

/// <param name="rdr"></param>

/// <param name="column"></param>

/// <param name="defaultValue"></param>

/// <returns></returns>

public static decimal GetDecimal(DbDataReader rdr, string column, decimal defaultValue)

{

int ordinal = rdr.GetOrdinal(column);

if (rdr.IsDBNull(ordinal))

{

return defaultValue;

}

else

{

return rdr.GetDecimal(ordinal);

}

}

/// <summary>

///

/// </summary>

/// <param name="rdr"></param>

/// <param name="column"></param>

/// <returns></returns>

public static double GetDouble(DbDataReader rdr, string column)

{

return GetDouble(rdr, column, 0);

}

/// <summary>

///

/// </summary>

/// <param name="rdr"></param>

/// <param name="column"></param>

/// <param name="defaultValue"></param>

/// <returns></returns>

public static double GetDouble(DbDataReader rdr, string column, double defaultValue)

{

int ordinal = rdr.GetOrdinal(column);

if (rdr.IsDBNull(ordinal))

{

return defaultValue;

}

else

{

return rdr.GetDouble(ordinal);

}

}

/// <summary>

///

/// </summary>

/// <param name="rdr"></param>

/// <param name="column"></param>

/// <returns></returns>

public static DateTime GetDateTime(DbDataReader rdr, string column)

{

return GetDateTime(rdr, column, new DateTime());

}

/// <summary>

///

/// </summary>

/// <param name="rdr"></param>

/// <param name="column"></param>

/// <param name="defaultValue"></param>

/// <returns></returns>

public static DateTime GetDateTime(DbDataReader rdr, string column, DateTime defaultValue)

{

int ordinal = rdr.GetOrdinal(column);

if (rdr.IsDBNull(ordinal))

{

return defaultValue;

}

else

{

return rdr.GetDateTime(ordinal);

}

}

/// <summary>

///

/// </summary>

/// <param name="rdr"></param>

/// <param name="column"></param>

/// <returns></returns>

public static string GetString(DbDataReader rdr, string column)

{

return GetString(rdr, column, null);

}

/// <summary>

///

/// </summary>

/// <param name="rdr"></param>

/// <param name="column"></param>

/// <param name="defaultValue"></param>

/// <returns></returns>

public static string GetString(DbDataReader rdr, string column, string defaultValue)

{

int ordinal = rdr.GetOrdinal(column);

if (rdr.IsDBNull(ordinal))

{

return defaultValue;

}

else

{

return rdr.GetString(ordinal);

}

}

/// <summary>

///

/// </summary>

/// <param name="rdr"></param>

/// <param name="column"></param>

/// <returns></returns>

public static string GetStringNotNull(DbDataReader rdr, string column)

{

int ordinal = rdr.GetOrdinal(column);

if (rdr.IsDBNull(ordinal))

{

return "";

}

else

{

string value = rdr.GetString(ordinal);

if (value == null) value = "";

return value;

}

}

/// <summary>

///

/// </summary>

/// <param name="rdr"></param>

/// <param name="column"></param>

/// <returns></returns>

public static int GetInt(DbDataReader rdr, string column)

{

return GetInt(rdr, column, 0);

}

/// <summary>

///

/// </summary>

/// <param name="rdr"></param>

/// <param name="column"></param>

/// <param name="defaultValue"></param>

/// <returns></returns>

public static int GetInt(DbDataReader rdr, string column, int defaultValue)

{

int ordinal = rdr.GetOrdinal(column);

if (rdr.IsDBNull(ordinal))

{

return defaultValue;

}

else

{

return rdr.GetInt32(ordinal);

}

}

/// <summary>

///

/// </summary>

/// <param name="rdr"></param>

/// <param name="column"></param>

/// <returns></returns>

public static int GetInt16(DbDataReader rdr, string column)

{

return GetInt16(rdr, column, 0);

}

/// <summary>

///

/// </summary>

/// <param name="rdr"></param>

/// <param name="column"></param>

/// <param name="defaultValue"></param>

/// <returns></returns>

public static int GetInt16(DbDataReader rdr, string column, int defaultValue)

{

int ordinal = rdr.GetOrdinal(column);

if (rdr.IsDBNull(ordinal))

{

return defaultValue;

}

else

{

return rdr.GetInt16(ordinal);

}

}

/// <summary>

///

/// </summary>

/// <param name="rdr"></param>

/// <param name="column"></param>

/// <param name="defaultValue"></param>

/// <returns></returns>

public static double GetMoney(DbDataReader rdr, string column)

{

int ordinal = rdr.GetOrdinal(column);

SqlDataReader sqlReader = (SqlDataReader)rdr;

if (sqlReader.IsDBNull(ordinal))

{

return new double();

}

else

{

return double.Parse(sqlReader.GetSqlMoney(ordinal).ToString());

}

}

/// <summary>

///

/// </summary>

/// <param name="rdr"></param>

/// <param name="column"></param>

/// <returns></returns>

public static byte GetByte(DbDataReader rdr, string column)

{

int ordinal = rdr.GetOrdinal(column);

if (rdr.IsDBNull(ordinal))

{

return new byte();

}

else

{

return rdr.GetByte(ordinal);

}

}

/// <summary>

///

/// </summary>

/// <param name="rdr"></param>

/// <param name="column"></param>

/// <param name="defaultValue"></param>

/// <returns></returns>

public static char GetChar(DbDataReader rdr, string column, char defaultValue)

{

int ordinal = rdr.GetOrdinal(column);

if (rdr.IsDBNull(ordinal))

{

return defaultValue;

}

else

{

char[] c = new char[1];

rdr.GetChars(0, 0, c, 0, 1);

return c[0];

}

}

/// <summary>

///

/// </summary>

/// <param name="rdr"></param>

/// <param name="column"></param>

/// <returns></returns>

public static bool GetBool(DbDataReader rdr, string column)

{

return GetBool(rdr, column, false);

}

/// <summary>

///

/// </summary>

/// <param name="rdr"></param>

/// <param name="column"></param>

/// <param name="defaultValue"></param>

/// <returns></returns>

public static bool GetBool(DbDataReader rdr, string column, bool defaultValue)

{

int ordinal = rdr.GetOrdinal(column);

if (rdr.IsDBNull(ordinal))

{

return defaultValue;

}

else

{

string value = "";

value = rdr.GetValue(ordinal).ToString();

if (value.Equals("yes", StringComparison.OrdinalIgnoreCase)

|| value.Equals("y", StringComparison.OrdinalIgnoreCase)

|| value.Equals("on", StringComparison.OrdinalIgnoreCase)

|| value.Equals("true", StringComparison.OrdinalIgnoreCase)

|| value.Equals("1", StringComparison.OrdinalIgnoreCase))

{

return true;

}

return false;

}

}

}

Sorting and Grouping with the Asp.Net GridView control

2007-11-21T05:26:00.001-08:00

Here is an example of how you can sort and group a GridView.

private bool _sorted = false;

private int _sortColumnIndex = -1;

private string _sortColumnHeader = string.Empty;

private string _SortExpr;

public string SortExpr

{

get { return _SortExpr; }

set { _SortExpr = value; }

}

protected void GridView1_Sorting(object sender, GridViewSortEventArgs e)

{

ResolveGroupingData(e.SortExpression);

}

private void ResolveGroupingData(string sortExpression)

{

foreach (DataControlField field in GridView1.Columns)

{

if (field.SortExpression == sortExpression)

{

_sorted = true;

SortExpr = sortExpression;

_sortColumnIndex = GridView1.Columns.IndexOf(field);

_sortColumnHeader = field.HeaderText;

}

}

}

protected override void Render(HtmlTextWriter writer)

{

if (_sorted)

{

Table table = (Table)GridView1.Controls[0];

Hashtable htLookUp = new Hashtable();

foreach (GridViewRow row in GridView1.Rows)

{

int realIndex = table.Rows.GetRowIndex(row);

string text = row.Cells[_sortColumnIndex].Text;

if (string.IsNullOrEmpty(text))

{

SortExpr = SortExpr.Replace('.', '_');

text = ((Label)row.FindControl("lbl" + SortExpr)).Text;

}

if (!htLookUp.ContainsKey(text))

{

htLookUp.Add(text, null);

GridViewRow newHeaderRow = new GridViewRow(realIndex, realIndex, DataControlRowType.DataRow, DataControlRowState.Normal);

TableCell newCell = new TableCell();

newHeaderRow.Cells.Add(newCell);

newCell.ColumnSpan = GridView1.Columns.Count;

newCell.BackColor = System.Drawing.Color.Gray;

newCell.ForeColor = System.Drawing.Color.White;

newCell.Font.Bold = true;

newCell.Text = string.Format(_sortColumnHeader, " : {0}", text);

table.Controls.AddAt(realIndex, newHeaderRow);

}

}

}

base.Render(writer);

}

2007-11-21T05:26:00.000-08:00

Here is an example of how you can sort and group a GridView.

private bool _sorted = false;

private int _sortColumnIndex = -1;

private string _sortColumnHeader = string.Empty;

private string _SortExpr;

table.Controls.AddAt(realIndex, newHeaderRow);

}

}

}

base.Render(writer);

}

Example of how to compare two objects for sorting.

2007-11-21T05:18:00.000-08:00

The example below demonstrates how you can compare two objects to allow for sorting. This is also a good example of how you can use reflection.

using System.Web;

using System.Web.Security;

using System.Web.UI;

using System.Web.UI.WebControls;

using System.Web.UI.WebControls.WebParts;

using System.Web.UI.HtmlControls;

using System.Collections.Generic;

using System.Reflection;

/// <summary>

/// Summary description for ObjectComparer

/// </summary>

public class ObjectComparer<T> : IComparer<T>

{

#region Properties

private string _direction = "ASC";

public string Direction

{

get { return _direction; }

set { _direction = value; }

}

private string _compareField;

public string CompareField

{

get { return _compareField; }

set { _compareField = value; }

}

#endregion

#region Constructors

public ObjectComparer(string compareField, string direction)

{

_compareField = compareField;

_direction = direction;

}

#endregion

#region IComparer<T> Members

public int Compare(T x, T y)

{

//Split the fields into an array. The field is divided by dots,

//like Employee.Person.FirstName

string[] fieldParts = _compareField.Split('.');

object compareValX = x;

object compareValY = y;

//get the value of each field in the list.

foreach (string field in fieldParts)

{

compareValX = GetPropertyValue(compareValX, field);

compareValY = GetPropertyValue(compareValY, field);

}

//compare the values of the last fields in the list. Assumes the field's

//type implements IComparable.

int compareValue = ((IComparable)compareValX).CompareTo(compareValY);

//negate the result if dircection is descending

if (_direction.ToUpper() == "DESC")

compareValue = -1 * compareValue;

return compareValue;

}

private object GetPropertyValue(object o, string property)

{

//using reflection, load the type and return the value of

//the given property. This will throw an exception if the

//property cannot be found.

PropertyInfo pi = o.GetType().GetProperty(property);

object val = pi.GetValue(o, null);

return val;

}

#endregion

#region IComparer<T> Members

int IComparer<T>.Compare(T x, T y)

{

//throw new Exception("The method or operation is not implemented.");

//Split the fields into an array. The field is divided by dots,

//like Employee.Person.FirstName

string[] fieldParts = _compareField.Split('.');

object compareValX = x;

object compareValY = y;

//get the value of each field in the list.

foreach (string field in fieldParts)

{

compareValX = GetPropertyValue(compareValX, field);

compareValY = GetPropertyValue(compareValY, field);

}

//compare the values of the last fields in the list. Assumes the field's

//type implements IComparable.

int compareValue = ((IComparable)compareValX).CompareTo(compareValY);

//negate the result if dircection is descending

if (_direction.ToUpper() == "DESC")

compareValue = -1 * compareValue;

return compareValue;

}

#endregion

}

How to collect post data and then send it to a remote url as a post using Asp.NET.

2007-11-21T05:02:00.001-08:00

Collect post data and send to remote URL as post. I know there is a postbackurl property that can be used, but this method allows you to modify, add, and remove from what you send to the new URL as a post. I've used this technique when integrating with PayPal and I needed to dynamically create a product that is being purchased (by including their user information), but this has many purposed.

void PostMe1(Object sender,EventArgs e){

RemotePost myremotepost = new RemotePost();

myremotepost.Url = "http://www.jigar.net/demo/HttpRequestDemoServer.aspx";

myremotepost.Add("field1","Tom");

myremotepost.Add("field2","Sawyer");

myremotepost.Post();

}

void PostMe2(Object sender,EventArgs e){

RemotePost myremotepost = new RemotePost();

myremotepost.Url = "http://www.jigar.net/demo/HttpRequestDemoServer.aspx";

myremotepost.Add("field1","Huckleberry");

myremotepost.Add("field2","Finn");

myremotepost.Post();

}

public class RemotePost{

private System.Collections.Specialized.NameValueCollection Inputs = new System.Collections.Specialized.NameValueCollection();

public string Url = "";

public string Method = "post";

public string FormName = "form1";

public void Add(string name,string value){

Inputs.Add(name,value);

}

public void Post(){

System.Web.HttpContext.Current.Response.Clear();

System.Web.HttpContext.Current.Response.Write("<html><head>");

System.Web.HttpContext.Current.Response.Write(string.Format("</head><body onload="\">",FormName));

System.Web.HttpContext.Current.Response.Write(string.Format("<form name="\" method="\" action="\">",FormName,Method,Url));

for(int i=0;i< Inputs.Keys.Count;i++){

System.Web.HttpContext.Current.Response.Write(string.Format("<input name="\" type="\" value="\">",Inputs.Keys[i],Inputs[Inputs.Keys[i]]));

}

System.Web.HttpContext.Current.Response.Write("</form>");

System.Web.HttpContext.Current.Response.Write("</body></html>");

System.Web.HttpContext.Current.Response.End();

}

}

How to show line breaks in an asp.net label.

2007-11-21T04:59:00.000-08:00

When data is collected via a TextBox and line breaks are provided in the input, this is a way to show those breaks in a label. This was surprisingly difficult to figure out for me, so hopefully this will save someone some time.

public string WrappableText(string source)
{
string nwln = Environment.NewLine;
return "

" +
source.Replace(nwln + nwln, "

")
.Replace(nwln, "
") + "

";
}

How to retrieve a page content with Asp.NET

2007-11-21T04:57:00.001-08:00

I use the method below to retrieve a page's content. I often use this technique to send invoices or receipts. You can create any page, then call this function to pull it into a string and send it as the email body.

public string GetUrl(string path)
{

using (StringWriter writer = new StringWriter())
{

Server.Execute(path, writer);

string html = writer.ToString();
path = "http://" + Request.ServerVariables["SERVER_NAME"] + ResolveUrl(path);
path = path.Substring(0, path.LastIndexOf("/") + 1);
//this is here so the css references from the theme are absolute paths
html.Replace("\"../", "\"" + path + "../");

return html;
}

}

Searching with the WSSListProvider for Sharepoint

2007-11-16T13:15:00.000-08:00

The WSSListProvider is a provider build on the Asp.NET provider framework that eases accessibility and simplifies the programming required to access list data in SharePoint. This is the basis for the SharePoint membership, profile, sitemap and role providers based on SharePoint list data. If you interested in any of these providers, please contact me.

This post explain in brief how to search using the WSSListProvider Sharepoint list provider.

It takes a hashtable of string pairs of search terms. Right now it only does exact "Text" based searching. Adding multiple items to the hashtable results in an "and" statement, all search items must be found.

The result is an xml root node containing no, one, or multiple rows of data. In each row, the data is stored in the attributes.

//This will search for "chris" in the "Username" column of the "+Abstract" list.
Hashtable search = new Hashtable();
search.Add("Username", "chris");
XmlNode result = WSSListManager.SearchListItems("+Abstract", search);
//Next, we can check to see how many items are in the list
//by using the Attribute "ItemCount" of the root node.
int count = int.Parse(result.Attributes["ItemCount"].Value);
//Now, based on how many rows there are, we can do various things.
if (count == 1)
{
//If there's only one row, we will select the first (and only) row
XmlNode node = result["z:row"];
//We now have access to the various Attributes of the row
//You can either access them individually...
string title = node.Attributes["Title"].Value;
//Or loop through all the attributes and use a switch statement
string temp;
bool approved;
foreach (XmlAttribute attrib in node.Attributes)
{
switch (attrib.Name)
{
case "Title":
temp = attrib.Value;
break;
case "Approved":
approved = bool.Parse(attrib.Value);
break;
default:
break;
}
}
}
else if (count > 1)
{
//Alternatively, if there is more than one row, we can
//access the data in all the rows by looping through them
foreach (XmlNode node in result)
{
//We need to check to make sure it's the right kind of node
//It injects "Whitespace" nodes at the beginning and ending of the rows returned
//Alternatively, it may be necessary to use (node.NodeType == XmlNodeType.Element)
if (node.NodeType != XmlNodeType.Whitespace)
{
//Using the same loop-through attributes code as above...
string temp;
bool approved;
foreach (XmlAttribute attrib in node.Attributes)
{
switch (attrib.Name)
{
case "Title":
temp = attrib.Value;
break;
case "Approved":
approved = bool.Parse(attrib.Value);
break;
default:
break;
}
}
}
}
}

How to show an asp.net User Control on a Sharepoint page

2007-11-15T14:12:00.000-08:00

Create a directory to hold the user controls on the sharepoint server under C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\CONTROLTEMPLATES
Move the user control into this directory, this can be uncompiled source code.
Using Sharepoint designer, create a page to display the user control.
Add the user control to the page you created with Sharepoint Designer the same way you would add any user control to a asp.net page.

That's it. Then you should be able to load this page in a browser and display the user control.

Stored Procedure to gain exclusive access to a database

2007-10-11T22:51:00.000-07:00

if exists (select * from dbo.sysobjects where id = object_id(N'[dbo].[USP_GETEXCLUSIVE]') and OBJECTPROPERTY(id, N'IsProcedure') = 1)
drop procedure [dbo].[USP_GETEXCLUSIVE]
GO

SET QUOTED_IDENTIFIER ON
GO
SET ANSI_NULLS ON
GO

--create stored procedure
CREATE PROCEDURE USP_GETEXCLUSIVE @dbname varchar(100) AS
SET NOCOUNT ON
SET QUOTED_IDENTIFIER OFF

--declares our variables
DECLARE @KILL_ID int
DECLARE @QUERY VARCHAR(320)

DECLARE GETEXCLUSIVE_CURSOR CURSOR FOR

--get all SPIDs from SYSOBJECTS table which match our database
SELECT A.SPID FROM SYSPROCESSES A JOIN
SYSDATABASES B ON A.DBID=B.DBID WHERE B.NAME=@DBNAME

OPEN GETEXCLUSIVE_CURSOR
FETCH NEXT FROM GETEXCLUSIVE_CURSOR INTO @KILL_ID

WHILE(@@FETCH_STATUS =0)
BEGIN

--form drop trigger query
SET @QUERY = 'KILL '+ CONVERT(VARCHAR,@KILL_ID)

EXEC (@QUERY)
FETCH NEXT FROM GETEXCLUSIVE_CURSOR INTO @KILL_ID
END

CLOSE GETEXCLUSIVE_CURSOR
DEALLOCATE GETEXCLUSIVE_CURSOR

GO
SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
GO

Name Code	Number Code	Glyph	Description
‘		‘	left single quote
’		’	right single quote
&sbquo;		‚	single low-9 quote
“		“	left double quote
”		”	right double quote
&bdquo;		„	double low-9 quote
&dagger;		†	dagger
&Dagger;		‡	double dagger
&permil;		‰	per mill sign
&lsaquo;		‹	single left-pointing angle quote
&rsaquo;		›	single right-pointing angle quote
&spades;		♠	black spade suit
&clubs;		♣	black club suit
&hearts;		♥	black heart suit
&diams;		♦	black diamond suit
	★	★	black star
	☆	☆	white star
&oline;		‾	overline, = spacing overscore
←		←	leftward arrow
↑		↑	upward arrow
→		→	rightward arrow
↓		↓	downward arrow
™		™	trademark sign
Name Code	Number Code	Glyph	Description
	-		unused
			horizontal tab
			line feed
			unused
			space
	!	!	exclamation mark
"	"	"	double quotation mark
	#	#	number sign
	$	$	dollar sign
	%	%	percent sign
&	&	&	ampersand
	'	'	apostrophe
	(	(	left parenthesis
	)	)	right parenthesis
	*	*	asterisk
	+	+	plus sign
	,	,	comma
	-	-	hyphen
	.	.	period
Name Code	Number Code	Glyph	Description
&frasl;	/	/	slash
	0-9		digits 0-9 (see numbers & letters)
	:	:	colon
	;	;	semicolon
<	<	<	less-than sign
	=	=	equals sign
>	>	>	greater-than sign
	?	?	question mark
	@	@	at sign
	A-Z		uppercase letters A-Z (see numbers & letters)
	[	[	left square bracket
	\	\	backslash
	]	]	right square bracket
	^	^	caret
	_	_	horizontal bar (underscore)
	`	`	grave accent
	a-z		lowercase letters a-z (see numbers & letters)
	{	{	left curly brace
	\|	\|	vertical bar
Name Code	Number Code	Glyph	Description
	}	}	right curly brace
	~	~	tilde
	-		unused
–		–	en dash
—		—	em dash
	-		unused
			nonbreaking space
¡	¡	¡	inverted exclamation
¢	¢	¢	cent sign
£	£	£	pound sterling
¤	¤	¤	general currency sign
¥	¥	¥	yen sign
¦ or &brkbar;	¦	¦	broken vertical bar
§	§	§	section sign
¨ or &die;	¨	¨	umlaut
©	©	©	copyright
ª	ª	ª	feminine ordinal
«	«	«	left angle quote
¬	¬	¬	not sign
			soft hyphen
®	®	®	registered trademark
¯ or &hibar;	¯	¯	macron accent
Name Code	Number Code	Glyph	Description
°	°	°	degree sign
±	±	±	plus or minus
²	²	²	superscript two
³	³	³	superscript three
´	´	´	acute accent
µ	µ	µ	micro sign
¶	¶	¶	paragraph sign
·	·	·	middle dot
¸	¸	¸	cedilla
¹	¹	¹	superscript one
º	º	º	masculine ordinal
»	»	»	right angle quote
¼	¼	¼	one-fourth
½	½	½	one-half
¾	¾	¾	three-fourths
¿	¿	¿	inverted question mark
À	À	À	uppercase A, grave accent
Á	Á	Á	uppercase A, acute accent
Â	Â	Â	uppercase A, circumflex accent
Name Code	Number Code	Glyph	Description
Ã	Ã	Ã	uppercase A, tilde
Ä	Ä	Ä	uppercase A, umlaut
Å	Å	Å	uppercase A, ring
Æ	Æ	Æ	uppercase AE
Ç	Ç	Ç	uppercase C, cedilla
È	È	È	uppercase E, grave accent
É	É	É	uppercase E, acute accent
Ê	Ê	Ê	uppercase E, circumflex accent
Ë	Ë	Ë	uppercase E, umlaut
Ì	Ì	Ì	uppercase I, grave accent
Í	Í	Í	uppercase I, acute accent
Î	Î	Î	uppercase I, circumflex accent
Ï	Ï	Ï	uppercase I, umlaut
Ð	Ð	Ð	uppercase Eth, Icelandic
Ñ	Ñ	Ñ	uppercase N, tilde
Ò	Ò	Ò	uppercase O, grave accent
Ó	Ó	Ó	uppercase O, acute accent
Ô	Ô	Ô	uppercase O, circumflex accent
Õ	Õ	Õ	uppercase O, tilde
Name Code	Number Code	Glyph	Description
Ö	Ö	Ö	uppercase O, umlaut
×	×	×	multiplication sign
Ø	Ø	Ø	uppercase O, slash
Ù	Ù	Ù	uppercase U, grave accent
Ú	Ú	Ú	uppercase U, acute accent
Û	Û	Û	uppercase U, circumflex accent
Ü	Ü	Ü	uppercase U, umlaut
Ý	Ý	Ý	uppercase Y, acute accent
Þ	Þ	Þ	uppercase THORN, Icelandic
ß	ß	ß	lowercase sharps, German
à	à	à	lowercase a, grave accent
á	á	á	lowercase a, acute accent
â	â	â	lowercase a, circumflex accent
ã	ã	ã	lowercase a, tilde
ä	ä	ä	lowercase a, umlaut
å	å	å	lowercase a, ring
æ	æ	æ	lowercase ae
ç	ç	ç	lowercase c, cedilla
è	è	è	lowercase e, grave accent
Name Code	Number Code	Glyph	Description
é	é	é	lowercase e, acute accent
ê	ê	ê	lowercase e, circumflex accent
ë	ë	ë	lowercase e, umlaut
ì	ì	ì	lowercase i, grave accent
í	í	í	lowercase i, acute accent
î	î	î	lowercase i, circumflex accent
ï	ï	ï	lowercase i, umlaut
ð	ð	ð	lowercase eth, Icelandic
ñ	ñ	ñ	lowercase n, tilde
ò	ò	ò	lowercase o, grave accent
ó	ó	ó	lowercase o, acute accent
ô	ô	ô	lowercase o, circumflex accent
õ	õ	õ	lowercase o, tilde
ö	ö	ö	lowercase o, umlaut
÷	÷	÷	division sign
ø	ø	ø	lowercase o, slash
ù	ù	ù	lowercase u, grave accent
ú	ú	ú	lowercase u, acute accent
û	û	û	lowercase u, circumflex accent
Name Code	Number Code	Glyph	Description
ü	ü	ü	lowercase u, umlaut
ý	ý	ý	lowercase y, acute accent
þ	þ	þ	lowercase thorn, Icelandic
ÿ	ÿ	ÿ	lowercase y, umlaut
Name Code	Number Code	Glyph	Description
	0	0	0
	1	1	1
	2	2	2
	3	3	3
	4	4	4
	5	5	5
	6	6	6
	7	7	7
	8	8	8
	9	9	9
	A	A	A
	B	B	B
	C	C	C
	D	D	D
	E	E	E
	F	F	F
	G	G	G
	H	H	H
	I	I	I
	J	J	J
	K	K	K
	L	L	L
	M	M	M
	N	N	N
	O	O	O
	P	P	P
	Q	Q	Q
	R	R	R
	S	S	S
	T	T	T
	U	U	U
	V	V	V
	W	W	W
	X	X	X
	Y	Y	Y
	Z	Z	Z
	a	a	a
	b	b	b
	c	c	c
	d	d	d
	e	e	e
	f	f	f
	g	g	g
	h	h	h
	i	i	i
	j	j	j
	k	k	k
	l	l	l
	m	m	m
	n	n	n
	o	o	o
	p	p	p
	q	q	q
	r	r	r
	s	s	s
	t	t	t
	u	u	u
	v	v	v
	w	w	w
	x	x	x
	y	y	y
	z	z	z

YourDotNetSolution

IE 6 adds anchor tags to request value

SQL Loop

Search all fields in a table

Report server report viewer 404 - File or directory not found

How to pass windows authentication when serving a report with Report Viewer from Reporting Services

How to enable Asp.NET security tables for a database.

How to query a list in sharepoint

How to disable or enable all foreign key constraints in Oracle

How to Export and Import MySQL database

How to retrieve a list of column names for a specific table in MS SQL Server.

Asp.NET Web Development Process

Asp.NET Web Development Process

Get customer approvals of all requirements. You will want to fill in blanks on behalf of the business, but if you do, make sure you always get customer approval for your assumptions.

Estimating – Use the following formulas for calculating ranges for estimating based on your requirements.

Order of Magnitude (Done during Initiating) - 25% to +75%

Budget Estimate (Done during Planning) -10% to +25%

Definitive Estimate (Done during Planning) - 5% to +10%

Analysis normally takes the form of Use Cases, but can also include:

Demo’s

Wire-frames

Prototypes

A Use Case is a narrative form of a process that is needed to meet each requirement. See Appendix A for a template.

Identify actors. An actor is a user of the system or other system that interacts with this one.

Build Use Cases for each concrete requirement.

Associate Use Cases with an Actor and make sure the Use Case is from the Actor’s perspective.

Define how data will be collected and used.

Will they need to report on this data?

Will 3rd party systems need to use it?

Is there a need to export this data? To what formats?

What validation rules should be required?

Define where data will come from that is required by the Use Case.

Will someone be entering the data?

Is the data static, or something that needs to change regularly?

Is the data coming from a 3rd party system?

Is the data dependent on a previous process being completed in this solution?

Use Cases should be complete and approved by the client before entering the “Design” phase.

DesignDesign is the process of taking solidified Use Cases (and related Requirements), and translating them into a Solution Design. This Solution Design should clearly communicate to a developer how the solution should be written. A Solution Design should contain:

Sequence Diagrams – These UML diagrams should map to a specific Use Case and show how the objects identified in the Static Structure for this Use Case will be used to accomplish the intended outcome.

Prototypes and wire-frames – This should define how the UI should look and function.

All major components of the solution are defined at a high level.

Dependencies and communication requirements between these components are identified.

Requirements and Design artifacts are completed and approved (if necessary) for the component being developed.

Camel CasingCamel casing occurs when all words of an identifier are capitalized, except for the first word. The identifiers firstName, productId, and email are all examples of using camel casing.

Use camel casing for private type fields, parameters, and local variables.

Pascal CasingPascal casing occurs when the first letter of every word in an identifier is capitalized. ProductName, CompanyName, and Email are examples of PascalCasing.

Use Pascal casing everywhere except for when you use camel casing. For example, property names, operations, and tables.

Field, Local Variable, and Parameter NamingFields are variables declared at the type level. Local variables are declared within methods, property accessors, and indexer accessors. Parameters are part of the declaration of methods, indexers, and delegates and enable code to pass arguments.

Prefix field names with "_". The identifiers _firstName, _companyId, and _email are proper field names.

Don't prefix Local variables and parameters. The identifiers firstName, companyId, and primaryEmailAddress are valid local variables.

UI ElementsUI Elements should be explicitly named if it is referenced anywhere on the page or in the code-behind.

UI Elements should be prefixed to show what type of UI element it is: “lbl” for Label, “txt” for TextBox, etc.

They should have “friendly” names that are applicable to how that control is being used.

Delegates and Events

Event names can use the VS assigned convention, but be sure the parent control has been named appropriately before the event is created.

Name Delegates with a “Handler” Suffix.

High Cohesion

InterfacesInterfaces should be used to provide all up-stream access between layers. Interfaces should also be considered when an object is shared among multiple Managers (UI processes) as an additional layer of abstraction.

User Interface LayerUser Interface Layer is the GUI of the application. For ASP.NET applications, this includes the ASPX and ASPX code-behind.

Use .NET UI components – In all instances possible, .NET components should be utilized for the GUI.

Use Object Data Sources – This provides design view readability into the BLL and DAL process without loosing encapsulation.

Use the code-behind – Avoid writing any embedded code with the UI. Instead, utilize the code-behind.

Use Master Pages, Skins, and Themes – This will provide encapsulation of design from the actual ASPX pages. Doing this will provide consistency for the look and feel, as well as ease of managing changes to the design in the future.

Use Cascading Style Sheets – CSS should be the primary layout means for overall UI control and design. Avoid using tables, inline styles and outdated formatting options (I.E. font tags).

Managers – Manager objects are used in the code-behind of the aspx page as well as in the DAL (see Data-Access Layer below). They provide single-point-access for all BLL (explicit) and DAL (implicit) functions the application needs to accomplish from the UIL.

Data-Access LayerThe data-access layer provides mechanisms for retrieving and populating data into BLL objects.

Gateways – Gateways are the primary data-access objects. They work in conjunction with a reference to a “Manager” to create business objects and populate them will data.

For BLL access use Interfaces – Because business objects are upstream from the DAL, all interaction with this layer should be handles through interfaces. Additionally, interaction with the BLL should be isolated to using “Managers”.

Use parameters when creating your queries by using the SqlCommand object.

Populate BLL objects – In general, business objects should be used to populate with data. Here are some exceptions to this rule:

You are doing a data-centric operation (requires no business logic). For example, binding search results to a data grid.

You want to provide a generic data transport. For example, when using web services datasets can provide a very agnostic data transport mechanism. Datasets can also easily translate to XML.

Read – This would involve any “Select” type operation.

Use Views – This will provide a layer of abstraction for the underlying table structure.

Utilize the “Managers” to create needed BLL objects and perform other business related functions.

Create methods specifically for populating BLL objects from data readers.

Only send in what is necessary from the BLL to retrieve the data. This typically means a primary key.

Return populated BLL objects to the “Manager”.

Create – This would include any “Insert” type operation.

Send in the BLL object containing the data for the insert operation. Remember, this must be referenced as an interface.

Will 3^rd party systems need to use it?

Is the data coming from a 3^rd party system?

Design

Design is the process of taking solidified Use Cases (and related Requirements), and translating them into a Solution Design. This Solution Design should clearly communicate to a developer how the solution should be written. A Solution Design should contain:

Camel Casing

Camel casing occurs when all words of an identifier are capitalized, except for the first word. The identifiers firstName, productId, and email are all examples of using camel casing.

Pascal Casing

Pascal casing occurs when the first letter of every word in an identifier is capitalized. ProductName, CompanyName, and Email are examples of PascalCasing.

Field, Local Variable, and Parameter Naming

Fields are variables declared at the type level. Local variables are declared within methods, property accessors, and indexer accessors. Parameters are part of the declaration of methods, indexers, and delegates and enable code to pass arguments.

UI Elements

UI Elements should be explicitly named if it is referenced anywhere on the page or in the code-behind.

Interfaces

Interfaces should be used to provide all up-stream access between layers. Interfaces should also be considered when an object is shared among multiple Managers (UI processes) as an additional layer of abstraction.

User Interface Layer

User Interface Layer is the GUI of the application. For ASP.NET applications, this includes the ASPX and ASPX code-behind.

Data-Access Layer

The data-access layer provides mechanisms for retrieving and populating data into BLL objects.

Populate BLL objects – In general, business objects should be used to populate with data.

Here are some exceptions to this rule:

Delete – In general, deletes take two forms:

A Soft delete – This flags a record as deleted, but doesn’t actually delete the record.

A Hard delete – This actually deletes a record from the database.