Problem :

We used to have asp.net website projects, which does not come with project files like .csproj. We also have fckEditor folder in our project. So now every time when I build my project it unnecessarily also build fckEditor folder also which is really annoying to me ( I hate when something takes too long to build :) ).

If you are working on Asp.Net Web Application then the solution is very simple, you just have to “Exclude it” from the project. BUT we are working on WebSite project not web application project.

Solution :

In fact it is quiet simple. Just hide the folder, I mean, Make the folder ( the one that you don't want to be included in compiling process) hidden and it will not be there in the build list.  So simple. :)

Recently I came across a great splash screen for Winforms developed by Tom Clement on CodeProject

I loved this splash screen. Tom has intially created this splash screen using .Net 1.0. Butthis great piece of code had some threading issues with .Net 2.0.

I have seen a lot of comments of users that they are facing few minor problems ( flickering, cross thread operation, use of registry ) and also other users have submitted respective solutions also.
I have just incorporated all those changes in .Net 3.5 version of this great splash screen. I have not written any code here, I have just read the comments and implemented suggestions they have displayed there.

Again Great work by Tom and other contributors who has helped this great splash screen by contributing their valuable suggestions ans solutions in comments.

Please find the attached zip file which contains source code of this splash screen for winforms modified to work with .Net 3.5

SplashScreen.zip (193.83 kb)

A quick ASP.Net tip

1) If you want to use any custom namespace or class in your global.asax you can use following syntax to use corresponding namespace.

<%@ Import Namespace="TristonFramework.Web" %>

or

<%@ Import Namespace="System.Web" %>

2) When you put a breakpoint in Global.asax and if it not firing than consider following tips

   a. Make sure you are using Debug environment ie <compilation debug="true">

    Warning : make sure you have switched compilation element to false before using the web.config in production. Otherwise it has a huge performance panelty. You can read about it here.

  b. Try to edit the Global.asax by just hitting few enters in blank space. Sometimes when Global.asax is not changed after last build, asp.net does not consider it for debugging. i dont know why ? But this trick works almost always.

Thanks and Regards,

Mahin Gupta