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.
Daily .NET Tips is aiming to sharing useful coding tips and tricks for .NET Developers. This site completely design for sharing Tips and Tricks, useful Code Snippet which anyone use in daily development work and targeted anything related with .NET. This month we have wide range of tips including ASP.NET, C#, MEF, Visual Studio, Profiler etc. In this post I am quickly listing down all the tips which are published over the month September 2011
This is the fifth post in the series of Development With Kinect .NET SDK. In this post I am going to discuss about interacting with multiple Kinect devices with in a single system using Kinect .NET SDK. Before going forward, I will strongly recommend you to read my previous post where I have discussed about Connecting Multiple Kinect Devices with System which will help you setup your system with multiple devices.
This is the Part III of my Kinect .NET SDK Development series post. In past two posts I have discussed about Installation of Kinect Devices along with setting up your development environment and Exploring NUI APIs with Camera. In this post I am going to cover some more fundamental stuff of Kinect Camera. Kinect .NET SDK provides some API to interact with motorized tilt ( Check out the device details section of first post for more information ) to enables the camera up (+27 Degree) or down (-27 degrees) . To adjust the motorized tilt you need to set the NUI Cameras ElevationAngle property to a value between –27 and +27.
The Kinect SDK is a developer toolkit for developing applications. This SDK provides a fantastic interface to interact with Kinect programmatically. The Kinect for Windows SDK beta includes drivers that interact with H/W and provides an interface to interact with device, APIs for interacting with Camera, Sensors, microphone and Motor. The SDK provides capabilities to the developers who build applications with C#, VB or C++ with Visual Studio 2010 which is running on Windows 7. I started developing application with Kinect SDK almost 2 months back, from the day when I received my Kinect Device. I tweeted about my first application over here and I am still learning about the Kinect SDK API’s and how to use them in different ways. Let’s share the learning over here. I will keep posting as step by step to allow you to understand the API’s and get inside Kinect development. I will write a series of post where I will discuss about fundamentals of Kinect SDK API and developing Application using it and yes Step by Step and obviously with Demo Project
The Global Assembly Cache (GAC) is a Cache for globally available Assemblies. Most of the shared assemblies are installed inside GAC to shared across different applications. The Global Assembly Cache tool (Gacutil.exe) allow us to manipulate the contents of the global assembly cache along with install and un-install Assembly. During the development, we generally take help of gacutil from command prompt to install or uninstall assemblies into or from GAC. This is a repetitive process, every time you made some changes in your library you might need to deploy it into the GAC. Visual Studio has a nice feature called Pre-Build and Post-Build events. Using these events we execute some specific commands before or after the build. In this post I am going to show you how we can configure the post build event to deploy an Assembly to GAC.
Visual Studio 2010 introduced a nice new “DataTip pinning” features that enable you to better track of variable and expression while debugging. I am sure by this time you must be knowing what is “Data Tips” and different features of it. In In this Post I am going to share a small tip which talks about tracking some out of scope object using DataTips while debugging.
In this post I’m going to talk about how we can use ASP.NET 4.0 Chart Control with SQL CE as back-end data base using Entity Framework. I will also show how Visual Studio 2010 SP1 provides new tooling supports for SQL Server CE 4.0. ASP.NET 4.0 introduced inbuilt chart controls features and Visual Studio 2010 SP1 Came up with nice tooling support for SQL Server CE. SQL CE is a free, embedded, lightweight database engine that enables easy database storage. This does not required any installation and runs in memory. Let’s see how we can place this together and create a small apps and deploy it using new “Web Deployment Tool” which is available with Visual Studio 2010 SP1.
Understanding the ASP.NET Page Life Cycle is an essential knowledge for developing ASP.NET Web Application. When request come from client to server there are many operations performed in backend before sending response to the client. When client request for some information from a web server, request first reaches to HTTP.SYS, which is the kernel level of IIS. HTTP.SYS then send the request to respective Application Pool. Application Pool then forward the request to worker process to load the ISAPI Extension which will create an HTTPRuntime Object to Process the request via HTTPModule and HTTPHanlder. Once request passed through the HTPP Pipeline, ASP.NET Page Life Cycle Start. You will find several articles that describes the What is ASP.NET Page lifecycle, what are the different events fired during page lifecycle. This post is something different, I will show you how you can see the each and individual Page life cycle events using IntelliTrace
IIS Express is a lightweight, self-contained version of IIS optimized for developers. IIS Express provides the power of IIS7.x while making it easy to develop and test websites. Why we say that it has power of IIS7.x because it runs on code base of IIS 7.5. Visual Studio 2010 SP1 Beta allows you to build and test web applications using IIS Express instead of the built-in ASP.NET Development Web Server (Cassini). If you want to use IIS Express with VS 2010, you have to install IIS Express separately on top of Service Pack 1. To know more about details of use of IIS Express, please read the post http://bit.ly/i8BN1H . We can set IIS Express as default Web Server for Visual Studio or We can also change from Project Properties. Well, In this post I am going to talk about how we run the both IIS and Cassini simultaneously for multiple projects in a single solutions.
IntelliTrace debugging is only available with Visual Studio 2010 Ultimate Edition, which collects debugging information in background and can be used at any point to time to analysis previous debugging data. IntelliTrace collected debugger information into a trace log file (.iTrace ) that can then be opened and debugged using Visual Studio later. Size of .iTrace was always a concerns, as it’s take huge amount of your hard drive space and IntelliTrace is on by default. So whenever you are doing F5 debugging in Visual studio .iTrace is getting saved and it’s consuming your hard drive.
Well, before moving forward, I must thank to Larry Guger , Program Manager for IntelliTrace features . Yesterday I had a discussion with him on IntelliTrace . During discussion I found there are several changes on IntelliTrace log saving which has been shifted with Visual Studio 2010 SP1. I have already blogged about few of them over here http://bit.ly/f8awhz. But few hidden stuff was missing which I got to know from Larry only. In this post I am going to discussed about those changes.