Using ASP.NET 4.0 Chart Control With New Tooling Support for SQL Server CE 4.0 in VS 2010 SP1 and Entity Model

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.

Continue reading

Run “IIS Express” and “Cassini” simultaneously in Visual Studio 2010 SP1

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.

Continue reading

IntelliTrace Log ( .iTrace ) files and Visual Studio 2010 SP 1– Some Hidden Stuff

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.

Continue reading