Visual Studio 2010 introduces also some new debugging features. One of them is debug history. Debug history enables you to track all the points on track of control flow and it also monitors activities that you cannot see otherwise. It makes debugging of hard to find problems much easier, I think. Of course, there are many other new and cool debugging features available.

Couple of years ago I brought two books for my company. Today I can say that I made a small investment that still works pretty well. These books are titled as The Data Model Reosurce Book and author of these books is Len Silverston.

Visual Studio 2010 has very powerful web application packaging and deployment system. When deploying your web application you create the deployment package and then publish it to web server. After configuring it is one-click action to get current version of application up to target server. Let’s see how it works.

Recently I wrote about Visual Studio 2010 and multiple web.config files support. Let’s see now how to play with web.config transformation so we can use one configuration on development environment and the other for production environment.

Here is the list of all downloads available for Visual Studio 2010 and .NET Framework 4.0. Also learning and hosting resources are included.

DispForm.aspx that displays detail view of list item and EditForm.aspx that displays edit view of list item are not customizable by default. You can move to these pages but there is no Edit option in Site Actions menu. But it still possible to customize these pages, add new web parts there and so on. All you need is your web browser.

Today I found something weird. I tried to add some new views to my ASP.NET MVC solution but there were no ASP.NET MVC items in new items dialog. All the other ASP.NET MVC projects had no problem like this. Solution is simple.

Visual Studio 2010 has support for multiple web.config files. It is one feature of new web application packaging and deployment system. We can create now separate web.config files for each configuration we have for application.

I’m trying out Azure Training Kit examples to study cloud stuff that should hit the streets (or sky) later this year. I faced some trouble when trying to connect with .Net Service Bus using settings mentioned in examples (netTcpRelayBinding and CardSpace). I tried hard but CardSpace authentication failed every time. My final solution was simple: I moved to username and password authentication scheme.

Client-side ID-s of ASP.NET controls have been problem for a long time. They are hard to predict and guess. Fool-proof method that uses JavaScript block that defines client-side ID-s as variable values is not very elegant. Today’s web applications use client-size scripting heavily and now ASP.NET 4.0 provides us with elegant features to handle client-size ID-s of controls to make client-side scripting easier for us. Let’s see quick example.