Tags: codeproject, Kinect, Kinect for Windows, Kinect for Windows SDK, Kinect Infrared Stream, Kinect IR Emitter, kinect SDK, Kinect Tutorial, Kinect windows SDK
In this post I am going to talk about how to capture the Infrared stream from the Kinect sensor and control the IR emitter using Kinect for Window SDK. This feature is available with the Kinect for Windows SDK v1.6. The major components for a Kinect device consists of a depth sensor, color camera, IR Emitter, and a set of microphones with everything secured inside box. The box is attached to a small motor working as the base that enables the device to be tilted.
JScript Debugger– “Unable to attach the process. Another debugger might be attached to the process” – while application is running from Visual Studio. [ Solution ] January 20, 2012Posted by Abhijit Jana in .NET 4.0, ASP.NET 4.0, ASP.NET 4.5, Tips and Tricks, Visual Studio, Visual Studio 2010, Visual Studio 2011.
Tags: ASP.Net, codeproject, Debugging, Visual Studio
Tags: ASP.NET 4.5, codeproject, Developer Preview
Visual Studio 2011 developer preview introduced many great features. These includes IDE features such as HTML Editor Enhancements, Debugging features, parallel computing improvements, SharePoint development features etc. You can read the Announcing Visual Studio 11 Developer Preview post from Jason Zander’s WebLog to know more about the newly launched Visual Studio. In this post I am going talk few of nice features of Visual Studio 2011 developer preview related with ASP.NET.
Tags: asp.net 4.0, codeproject, IIS, Profiler Tool, Visual Studio 2010
Most of all are well aware about command line profiling for ASP.NET Application using VSPerfASPNETCmd command line tool . This can easily profile your ASP.NET Web applications which is hosted on IIS. We just need to run VSPerfASPNETCmd command with required parameter. Once profiling done, we can inspect the generated performance report (.vsp) file within Visual Studio. But, do you know we can do the complete profiling within Visual Studio itself. How ? Here you go.
Tags: .NET, ASP.Net, asp.net 4.0, C#, codeproject, EnableSessionState, HTTPContext, HttpModule, httpPipeline, Session, Session Mode, SessionStatebehavior, state Management, Web.config
While working with ASP.NET web application you must be familiar with one of most important state management technique “Session”. If you want to do a quick refresh or want to know some thing more, please go ahead and read one of my article “Exploring Session in ASP.NET” published at Code Project. In this post I am going to share some important tips that might be useful.
Tags: ASP.Net, codeproject, jQuery, jQuery Context Sensitive Help
In this blog post I am going to explain how we can create a simple Context Sensitive Help for ASP.NET Controls using jQuery. This has been done based on the of a controls in a ASP.NET Web Form. On control selection / focus jQuery Loads a HTML Content from a remote file, then it’s apply the filter based on the control id and inject the filtered content into a predefined placeholder with in the DOM Hierarchy.
Tags: codeproject, Tips & Tricks, Visual Studio 2010, Visual Studio Productivity Power Tool
1 comment so far
In the recent update of Visual Studio 2010 productivity power tool there are few new interesting features introduced. You can download the Productivity tool from http://bit.ly/9nybU6 . There are certain new features like Quick Find which allows you find and advance find dialog option with in code editor with nice highlighting features, nice enhancement of add reference window. kunal chowdhury has some nice blog post where he talked about above two new productivity tool features. You can find the post over http://bit.ly/hDa0si and http://bit.ly/grhGAI . In this post I am going to talk about another nice and most interesting features of Power Productivity Tool which “Enhanced Scroll Mode”.
Run ASP.NET Web Application from Command Prompt February 28, 2011Posted by Abhijit Jana in ASP.NET, Tips and Tricks, Visual Studio.
Tags: ASP.Net, cmd, codeproject
Visual Studio has its own integrated ASP.NET Runtime engine, which helps to run any ASP.NET web application with in Visual Studio. While running application from Visual Studio, you must have seen a popup notification in System Tray (As shown in below image) , which is notification of ASP.NET Development Server.
This ASP.NET Development Server is nothing but a executable file (WebDev.WebServer) which used by Visual Studio to execute you web application when it’s running in the context of Visual Studio. You can find the executable file at <\Program Files (x86)\Common Files\microsoft shared\DevServer\10.0> . This folder contain two different executable
WebDev.WebServer20 is targeted to CLR 2.0, which means all the ASP.NET Application which are targeted till FW .NET 3.5 will be taking care by WebDev.WebServer20.EXE and WebDev.WebServer40.EXE for ASP.NET 4.0 based application.
Now, let’s see how we can use these executable to run an ASP.NET 4.0 Application with out using Visual Studio.
How to make ViewState secure in ASP.NET ? January 26, 2011Posted by Abhijit Jana in ASP.NET, Tips and Tricks.
Tags: ASP.Net, codeproject, How To
The ASP.NET ViewState is a client side state management. ViewState is stored in hidden field with ID named __VIEWSTATE. Typically, stored ViewState information looks as below:
Now let us look at the value. It looks likes an encrypted string. This is nothing but Base64 Encoded string and it is not an encrypted string. So it can be easily decoded.
The main reasons for making it Base64 encoding are as follows:
1. Base64 makes a string suitable for HTTP transfer
2. It makes it a little harder to read .
But people often get confused that this is an encrypted string.
Details explanation on Compression Enabled Session for SQL Server and State Sever Session Mode in ASP.NET 4.0 January 19, 2011Posted by Abhijit Jana in ASP.NET 4.0, General.
Tags: asp.net 4.0, codeproject, CompressionEnabledSEssion, Sate Server, SQL SErver
While we are talking about state management we consider Session is one of most useful server side state management mechanism for a web application. In ASP.NET mainly we are having two type of state management 1. In Process and 2. Out Process . “In process” is the by default session storage mode for ASP.NET Web application and this is taken care by worker process in IIS. When it comes under Out Process we can use either of state server or SQL Server to persist session data. In case of In Process, session data stored in In memory of worker process. But when we are talking about “OutProc” session mode, we need to ensure that session data should be “Serialized” first . So, when we are moving session data from Web Server to Out Process Server ( State Server or SQL Server ) it can be a performance overhead based on the size of data that we are storing in Session.
ASP.NET 4.0 comes with a new option for compressing the Session data with Out Process Session mode. To enabling this functionality we need to add “compressionEnabled=”true” attribute with the SessionMode in web.config .
Programmatically Changing Session State Behavior in ASP.NET 4.0 January 15, 2011Posted by Abhijit Jana in ASP.NET 4.0, General, Visual Studio 2010.
Tags: asp.net 4.0, codeproject, HttpModule
Session is one of most important state management in ASP.NET. We can enable or disabled session state either in web.config or using @Page directive’s EnableSessionState attributes. But there was no provision to change the session state at runtime till date in ASP.NET. But using ASP.NET 4.0, we can change the session state programmatically . The .NET 4.0 framework adds a new method SetSessionStateBehavior to the HttpContext class for ASP.NET. This method required SessionStatebehavior value to set the current session mode. To call SetSessionStateBehavior simply create a new HttpModule by Implementing IHttModule and hook the BeginRequest event. Most important you can only use the SetSessionStateBehavior until the AcquireRequestState event is fired, because AcquireRequestState Occurs when ASP.NET acquires the current state that is associated with the current request
- Default: This is default setting which means everything works as before
- Disabled: Turned of Session Sate for Current Request.
- ReadOnly: Read only access to Session State;
- Required: Enabled session state for both Read and Write Access;
When we can use HttpContext.Current.Items to stores data in ASP.NET? January 14, 2011Posted by Abhijit Jana in ASP.NET, ASP.NET 4.0, Tips and Tricks, Visual Studio.
Tags: ASP.Net, codeproject, HTTPContext, Session
To answer this question In a single statement, you can use HttpContext.Current.Items for very short term storage. By Short term storage means, this data is valid for a single HTTP Request. There are many confusion around regarding storing data in HttpContext.Current.Items and storing data in Session variable. In this blog post I am going to describe what are the different scenarios where we can use HttpContext.Current.Items and what is the exact difference with session variable.
Items collections of HttpContext is and IDictionary key-value collections and that are shared across a single HTTPRequest. Yes, HttpContext.Current.Items valid for a single HTTPRequest. Once after processing, server information is sent back to the browser, the variables that were set in the Items collection will lost. Where as for Session Variable, information valid for multiple request as this is user specific. The session variable only expires either on Session Time Out or explicitly clear the values.