How to Make Your Direct Mail Envelopes Stand Out
Direct mail is an important means of communication for several reasons. Direct mail is for decades and continues to be the number one ways, an important message at the same time to present one or more clients. There are several ways that stand out a direct-mail-handling the client can make.
An envelope that strikes you get almost always special attention and will be dealt with promptly and quickly. First, most of the people as well as companies send in simple white envelopes. The simple white envelope with a printed name and address is standard with many mailings. Simply white printed envelopes are very common and are probably not much attention to those who receive the letter or information. However custom envelopes are not the usual and draws the receiver in this way are they more prone to immediately open and view content.
Direct mail envelopes are definitely more attention attract if they are brightly painted and have a special or unusual font. Therefore, this type is the envelope is more attention and get more than probably the priority of the recipient. If you get a larger than normal size e-Mail correspondence that is red or green color the recipient more than likely immediately open and respond to the contents of the envelope, if necessary.
What is viewstate in ASP.NET?
The postback question is the heart of any interview on ASP NET. When a postback happens (i.e. when a form is submitted to a server), the variable values that are set in the code-behind page are erased from the memory of the client system. This concept would be different from what happens in Windows-based applications, where the variable variables persist in memory until they are freed from the memory either by the garbage collector, or by specific codes like dispose or finalize.
In web applications, variable values simply get erased. But it is very simple to persist these values. They may be persisted using the Viewstate object. Before the postback is invoked, the variable's value is saved in a viewstate object. In the recieving page, the viewstate's value may be retrieved back. See example code below...
//Save the value in ViewState object before the PostBack
ViewState("SomeVar") = txtFirstName.text;
//Retrieve the value from ViewState object after the PostBack
String strFirstName = ViewState("SomeVar").ToString();
What is Windows Presentation Foundation, WPF?
What is Windows Presentation Foundation, WPF?
WPF allows creating rich application with respect to look and feel. The rich classes of WPF along with a design engine allow you to make innovative interfaces and client applications with 3D images, animation that is not available using HTML
What are the different documents supported in WPF?
The different documents supported by WPF are mainly fixed documents and flow documents. Fixed documents are used for what you see is what you get (WYSIWYG) applications. In such applications observance to the original design is important. E.g. Desktop applications Flow documents concentrate more on optimize viewing and readability., rather than using a “fixed” layout, flow documents adjust their content based on values of runtime variables. Adjusting content will also include adjusting size, resolution etc. E.g. a Web page.
What are benefits and Limitation of using Hidden fields in asp.net?
Following are the benefits of using Hidden fields:-
. They are simple to implement.
. As data is cached on client side, they work with Web Farms.
. All browsers support hidden field.
. No server resources are required.
Following are limitations of Hidden field:-
. They can be tampered creating a security hole.
. Page performance decreases if you store large data, as the data are stored in pages itself.
. Hidden fields do not support rich structures as HTML hidden fields are only single valued. Then you have to work around with delimiters etc to handle complex structures.
Below is how you will actually implement hidden field in a project
What is the difference between Server.Transfer and Response.Redirect? Why would I choose one over the other?
Some of we developers may confused about these 2 method,
Server.Transfer() : client is shown as it is on the requesting page only, but the all the content is of the requested page. Data can be persist accros the pages using Context.Item collection, which is one of the best way to transfer data from one page to another keeping the page state alive.
Response.Dedirect() :client know the physical loation (page name and query string as well). Context.Items loses the persisitance when nevigate to destination page.
In earlier versions of IIS, if we wanted to send a user to a new Web page, the only option we had was Response.Redirect. While this method does accomplish our goal, it has several important drawbacks. The biggest problem is that this method causes each page to be treated as a separate transaction. Besides making it difficult to maintain your transactional integrity, Response.Redirect introduces some additional headaches. First, it prevents good encapsulation of code. Second, you lose access to all of the properties in the Request object. Sure, there are workarounds, but they’re difficult. Finally, Response.Redirect necessitates a round trip to the client, which, on high-volume sites, causes scalability problems. As you might suspect, Server.Transfer fixes all of these problems. It does this by performing the transfer on the server without requiring a roundtrip to the client.
Design Pattern – proxy pattern
Proxy fundamentally is a class functioning as in interface which points towards the actual class which has data. This actual data can be a huge image or an object data which very large and can not be duplicated. So you can create multiple proxies and point towards the huge memory consuming object and perform operations. This avoids duplication of the object and thus saving memory. Proxies are references which points towards the actual object.
Figure ‘Proxy and actual object’ shows how we have created an interface which is implemented by the actual class. So the interface ‘IImageProxy’ forms the proxy and the class with implementation i.e. ‘clsActualImage’ class forms the actual object. You can see in the client code how the interface points towards the actual object.
Figure: - Proxy and actual object
The advantages of using proxy are security and avoiding duplicating objects which are of huge sizes. Rather than shipping the code we can ship the proxy, thus avoiding the need of installing the actual code at the client side. With only the proxy at the client end we ensure more security. Second point is when we have huge objects it can be very memory consuming to move to those large objects in a network or some other domain. So rather than moving those large objects we just move the proxy which leads to better performance.
10 .NET questions
How do you view the methods and members of a DLL? - What is shadowing?
- How do you load an assembly at runtime?
- If I am writing in a language like VB or C++, what are the procedures to be followed to support .NET?
- Compare Client server application with n-Tier application
- Differences between DLL and EXE?
- Can an assembly have EXE?
- Can a try block have more than one catch block?
- Can a DLL be changed to an EXE?
- Compare & contrast rich client (smart clients or Windows-based) & browser-based Web application
- What are the collections you’ve used?
- Can a try block have nested try blocks?
jsp interview questions, What is a output comment
A comment that is sent to the client in the viewable page source.The JSP engine handles an output comment as uninterpreted HTML text, returning the comment in the HTML output sent to the client. You can see the comment by viewing the page source from your Web browser.
JSP Syntax
<!-- comment [ <%= expression %> ] -->
Example 1
<!-- This is a commnet sent to client on
<%= (new java.util.Date()).toLocaleString() %>
-->
Displays in the page source:
<!-- This is a commnet sent to client on January 24, 2004 -->