December 2006 - Posts

Totally Stolen from:
  1. Empty Recycle Bin (Yes, I know. Not rocket surgery so far. Keep with me, I'm getting warmed up.)
  2. If you bought a PC with XP preinstalled, consider running the PC Decrapifier. It clears out the useless bundled software the manufacturer included to cut costs through renewal kickbacks.
  3. Uninstall any programs you don't need. My criteria: If I can't remember what it is or haven't used it in 6 months, I don't need it. I use SAFARP (Small and Fast Add Remove Programs) , but Windows Add / Remove Programs works here. [UPDATE] A comment reminded of something here - XP Hotfix Files. I've used (and recommend) Doug Knox's " XP Remove Hotfix Backup" program.
  4. Run CCleaner to clean up temporary files and clear out orphaned registry keys. Registry cleanup used to be simple until Office started stashing unused keys to indicate features which would be installed on first use, after which registry cleaners often did more harm than good. However, CCleaner is regularly updated and has always worked for me. If you're scared to monkey with the registry, CCleaner will still help find unused temporary (permatemp?) files which can be removed.
  5. Start looking for big files to be removed. I use FolderSize and WinDirStat for this. Actually, I use FolderSize more for day to day stuff, but for clearing out the underbrush with a machete style work, you can't beat WinDirStat. The treemap really helps you zoom in on the large files or folders; when you click on them they're automatically selected for you in the folder view above. By the way, the screenshot shows it working in Vista.
Posted by wwright | 1 comment(s)

If you are receiving this error, when trying to persist your data with a call to SubmitChanges() on your datacontext, you will find that not only can you not trap it, it blows up your running instance of your webserver… dandy!

It took a lot research to find out what was happening, but eventually Kashif on the ASP.NET forums had the answer: add enlist=false to your connection string. Apparently DLINQ is/is not listening for some kind async event and goes kablooey when it fires. None-the-less, here is an example config string so you can see what I mean. (btw… how on Earth did I ever fix a problem I didn’t make before the internet?)

<add name="DataConnection" connectionString="Data Source=MyServer;Initial Catalog=MyDb;Persist Security Info=True;User ID=wwright;Password=notachance;enlist=false"  providerName="System.Data.SqlClient" />

Posted by wwright | with no comments
More Posts