Since I am using Qwerty keyboards, it is not that easy to type the accented characters in french or even the euro symbol.
I can still use the Windows Character Map, or remember the ASCII code, but I can now also open up a website such http://www.copypastecharacter.com/, which simply does what it says he does (Copy/Paste characters)
Thursday, November 26, 2009
Monday, November 02, 2009
Resharper 5.0 EAP
Resharper 5.0 is on its way...Despite the VS 2010 support, there are some promising new features
- External PDB support
- Project Refactoring
- Better ASP.Net support
- And much more as the JetBrains' Guys demonstrated us over the past years...
Wednesday, October 21, 2009
Tools I like and use
It's now a casual thing to publish the tools you used, so here is my list (for a .Net developer):
- Visual Studio 2008/2010 Pro
- Visual Studio Power Commands Add-In
- Web Deployment Project 2008/2010
- JetBrains Resharper 5.x
- Sybase PowerDesigner
- Enterprise Library Blocks (Data, PolicyInjection)
- MyGeneration (Code Generation)
- MS Build (+ Commuity Tasks)
- NUnit
- Wix
- JetBrains TeamCity
- Redgate Reflector
- Redgate SQL Compare
- TortoiseSVN
- VisualSVN
- SandCastle + Help File Builder
- Firefox (with Firebug)
- Chrome
- Notepad++
- Softerra LDAP Browser
- Paint .Net
- TrueCrypt
- FileZilla
- SyncToy 2.0
If you'd like more tools, check out others' list
Monday, September 28, 2009
MS SQL Server Profiling - Missing Indexes
If you are using MS SQL Server, there is a good chance that you have (or will have) to monitor and improve some of your queries.
Since its 2005 edition, SQL Server provides a feature to find the missing indexes, giving you some information about potential indexes that it thinks would improve performances. This information can be really useful to proactively improve the queries that are getting slower when the number of records grow.
However, like almost everything, this is not all back or white...you should consider the proposed information, but not create dozens of indexes on every table if you don't want your server to spend all its time, processing and especially I/O to maintain indexes.
On the same topic, you will find a couple of nice SQL statements below:
Since its 2005 edition, SQL Server provides a feature to find the missing indexes, giving you some information about potential indexes that it thinks would improve performances. This information can be really useful to proactively improve the queries that are getting slower when the number of records grow.
However, like almost everything, this is not all back or white...you should consider the proposed information, but not create dozens of indexes on every table if you don't want your server to spend all its time, processing and especially I/O to maintain indexes.
On the same topic, you will find a couple of nice SQL statements below:
Wednesday, July 01, 2009
Subscribe to:
Posts (Atom)