TFSDeleteProject /server:ServerName ProjectName
Warning: Deleting a team project cannot be undone. Are you sure you want to delete the team project (Y/N)? Y
Deleting from Build ...
Deleting from Work Item Tracking ...
Deleting from Version Control ...
Deleting Report Server files ...
Deleting SharePoint site ...
Deleting from Team Foundation Core ...
Monday, November 27
- Discussion on Enterprise Exception Handling and Logging
December 11, 2006 : 18.30 - 20.00
This is a session where you (yes, you!) can discuss exception handling and logging in enterprise applications. Bring your tips and tricks, problems and exception handling frustrations with you, and we’ll all learn about best practices together! No slides or preparation required! Don’t want to discuss? No problem, you’re not required to say anything, but we hope you will. To help with a smooth discussion, it will be lead by a panel of 3 to 4 people. If you’re interested to sit on this panel, you’re invited (First-come, First-served basis).
- Visug Geek Dinner
December 21, 2006 : 19.00 - ...
Would you like to meet fellow developers, and have some discussions over dinner you would normally have at the family table? Then come to our geek dinner, where we can discuss everything (yes, even your latest gadget!) while becoming a bigger person. You don’t have to be a geek to attend a geek dinner, but don’t expect us to discuss the latest clothing fashion!
Saturday, November 25
System.Configuration.ConfigurationSettings.AppSettings is obsolete: This method is obsolete, it has been replaced by ConfigurationManager.AppSettings.Ever had similar warnings at compile time? Ok, no problem you think : just replace ConfigurationSettings with ConfigurationManager and you're done. Not! The ConfigurationSettings class exists in the System.dll assembly while the new ConfigurationManager (.NET 2.0) class exists in the System.Configuration.dll assembly. So, you won't be able to find the ConfigurationManager class without adding a reference to the System.Configuration.dll in your project.
Sunday, November 19
Thursday, November 16
Monday, November 6
Saturday, November 4
For the applications I profiled so far, I was always interested in the exact duration of external calls (towards a database, towards another application, ...) from the profiled applications. It turns out that the default setting of DevPartner Studio 8.1 does not take into account the duration of an external call.
In the screenshot above (generated results with DevParnter Studio 8.1) you can see that the sleepFor3seconds method is executed 10 times (Count column), but it takes 0 seconds (Time column). That's not the information I'm looking for - the sleepFor3seconds method takes actually 30 seconds in total! Ok, the Sleep method is not the most appropriate example here, but imagine that it's replaced by a call to a database ... The default behavior of DevPartner 8.1 is that it excludes time spent in threads of other running applications. Luckily it's easy (but hard to find!) to include this external time as well. Go to your project in Visual Studio and hit F4 to display the Project Properties. There you can toggle the Exclude Others setting and that will give the desired results (see screenshot below).
So, be sure what to profile! Sometimes it can be interesting to profile only your own .NET code, but in applications that are dependent of other applications it might be very appropriate to measure also the duration of the external calls.
Wednesday, November 1
- Drag and drop a GridView on your webpage
- Set property AllowPaging on GridView to true
- Implement OnPageIndexChanging event in your code
- Store datasource in a session object
- Use session object for databinding in OnPageIndexChanging event
If you don't use the IsPostPack check, your data will be loaded each time from the database and so you won't need to store the datasource in a session object. But I prefer to store the data in memory to avoid extra database-calls. Another solution may be to store this data in a ViewState object instead of a session object : same results!